bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Werner LEMBERG <wl@gnu.org>
To: bruno@clisp.org
Cc: bug-gnulib@gnu.org
Subject: Re: can't compile `stdlib.h` on mxe
Date: Sat, 22 May 2021 17:57:40 +0000 (UTC)	[thread overview]
Message-ID: <20210522.195740.675831717576746236.wl@gnu.org> (raw)
In-Reply-To: <13187658.4rgUex5avo@omega>


>> Note that this is a new error; it didn't happen in July 2019 (the
>> last time I've tried to build ttfautohint with mxe and Qt5).
> 
> Yes. We have added 'restrict' in many places, to match the function
> declarations in POSIX.

OK.

> That's not enough. <config.h> needs to be included before <memory>.
> 
> The Qt documentation [1] recommends a Makefile rule such as
> 
> 	moc $(DEFINES) $(INCPATH) -i $< -o $@
> 
> Try to change this to
> 
> 	moc -fconfig.h $(DEFINES) $(INCPATH) -i $< -o $@

[The proper command line option for moc would be `-b config.h`,
 AFAICS.]

This doesn't work; regardless of the used option, <memory> is always
inserted first.

> or
> 
> 	{ echo '#include <config.h>'; moc $(DEFINES) $(INCPATH) -i $< ; } > $@.tmp
> 	mv $@.tmp $@

This worked, thanks a lot!


    Werner


  reply	other threads:[~2021-05-22 17:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-22 10:03 can't compile `stdlib.h` on mxe Werner LEMBERG
2021-05-22 12:25 ` Bruno Haible
2021-05-22 12:45   ` Werner LEMBERG
2021-05-22 14:32     ` Bruno Haible
2021-05-22 17:57       ` Werner LEMBERG [this message]
2021-05-22 18:39       ` Paul Eggert
2021-05-23  5:30         ` Werner LEMBERG

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210522.195740.675831717576746236.wl@gnu.org \
    --to=wl@gnu.org \
    --cc=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).