bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gcc 4.3.0 and stddef.h


From: Eric Blake
Subject: Re: gcc 4.3.0 and stddef.h
Date: Thu, 15 May 2008 18:53:21 -0600
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.14) Gecko/20080421 Thunderbird/2.0.0.14 Mnenhy/0.7.5.666

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

[adding bug-gnulib]

According to Karl Berry on 5/15/2008 10:18 AM:
| Hi Eric (and Sergey),
|
| m4 1.11.1 (and tar 1.20, as I previously reported) doesn't compile with
| gcc 4.3.0, which I installed from the original sources.
|
| Here's the m4 error:
|
| gcc -std=gnu99  -I.     -g -O2 -MT gl_avltree_oset.o -MD -MP -MF
.deps/gl_avltree_oset.Tpo -c -o gl_avltree_oset.o gl_avltree_oset.c
| In file included from gl_oset.h:22,
|                  from gl_avltree_oset.h:21,
|                  from gl_avltree_oset.c:21:
| /usr/local/gnu/lib/gcc/i686-pc-linux-gnu/4.3.0/include/stddef.h:214:
error: duplicate 'unsigned'
| /usr/local/gnu/lib/gcc/i686-pc-linux-gnu/4.3.0/include/stddef.h:214:
error: two or more data types in declaration specifiers
| In file included from /usr/include/stdlib.h:438,
|                  from ./stdlib.h:30,

Definitely an instance of gnulib's stdlib.h wrapping the system stdlib.h.

|                  from gl_avltree_oset.c:23:
| /usr/include/sys/types.h:110: error: two or more data types in
declaration specifiers
| make[3]: *** [gl_avltree_oset.o] Error 1
| make[3]: Leaving directory `/usr/local/gnu/src/m4-1.4.11/lib'
|
| Line 214 is just this:
| typedef __SIZE_TYPE__ size_t;

Can we see the preprocessed file?  I'm guessing (because I don't have a
working gcc 4.3.0 myself) that some previous header, perhaps even
<config.h>, is #defining size_t, and that the pre-definition, coupled with
~ the expansion of __SIZE_TYPE__, is leading to the duplicate 'unsigned'
designators.

|
| I'll attach the whole stddef.h in case it helps.  If not, life goes on :).
| There's no problem with other gcc versions; unfortunately I haven't yet
| had a chance to trace down whether the problem is in gcc (likely) or the
| infrastructure.

Another thing to check: could you have a stale config.cache from a prior
compiler interfering with configure's determination of gcc 4.3.0's abilities?

- --
Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkgs2wEACgkQ84KuGfSFAYB9oACdEDKqfSm5/TQi80Ow4YLROoxs
Vg4An32bTreLbSMu5aZq9eJRnQ+GyiVm
=JX0X
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]