From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Cc: Werner LEMBERG <wl@gnu.org>
Subject: Re: can't compile `stdlib.h` on mxe
Date: Sat, 22 May 2021 14:25:00 +0200 [thread overview]
Message-ID: <2661657.bLj8NbuU8O@omega> (raw)
In-Reply-To: <20210522.120351.2143127505500278390.wl@gnu.org>
Hi Werner,
> While compiling my `ttfautohint` package with a slightly tailored mxe
> build, I get the following compilation error:
>
> CXX ttfautohintGUI-ddlineedit.moc.o
> In file included from /home/wl/git/mxe/usr/lib/gcc/i686-w64-mingw32.static/5.5.0/include/c++/cwchar:44:0,
> from /home/wl/git/mxe/usr/lib/gcc/i686-w64-mingw32.static/5.5.0/include/c++/bits/postypes.h:40,
> from /home/wl/git/mxe/usr/lib/gcc/i686-w64-mingw32.static/5.5.0/include/c++/iosfwd:40,
> from /home/wl/git/mxe/usr/lib/gcc/i686-w64-mingw32.static/5.5.0/include/c++/memory:72,
> from ddlineedit.moc.cpp:9:
> ../gnulib/src/stdlib.h:1904:1: error: expected ',' or '...' before 'string'
> _GL_FUNCDECL_RPL (strtoull, unsigned long long,
> ^
>
> Attached is the built `stdlib.h` file, together with the used
> `bootstrap.conf`. Please advise.
The error message "expected ',' or '...' before 'string'" points to a problem
with the 'restrict' keyword.
An appropriate definition of 'restrict' should be available in the gnulib-
generated config.h file.
* Can you verify that ddlineedit.moc.cpp starts with a '#include <config.h>'
statement? [1]
* Can you show the block of preprocessor statements in <config.h> that
defines 'restrict'?
* Can you show the command that is being executed (make V=1)? A symbolic
placeholder like 'CXX' is useless for debugging a compilation failure.
* What are the C compiler and C++ compiler versions that you use in this
build?
Bruno
[1] https://www.gnu.org/software/gnulib/manual/html_node/Source-changes.html
next prev parent reply other threads:[~2021-05-22 12:25 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 [this message]
2021-05-22 12:45 ` Werner LEMBERG
2021-05-22 14:32 ` Bruno Haible
2021-05-22 17:57 ` Werner LEMBERG
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=2661657.bLj8NbuU8O@omega \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=wl@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).