Skip to Content.
Sympa Menu

sm-discuss - [SM-Discuss] GCC 4.3.0 and gnupg

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: Eric Sandall <eric AT sandall.us>
  • To: " SM-Discuss" <sm-discuss AT lists.ibiblio.org>
  • Subject: [SM-Discuss] GCC 4.3.0 and gnupg
  • Date: Thu, 10 Apr 2008 22:39:45 -0700

The issue with gnupg and GCC 4.3.0 is:
gcc -march=i686 -pipe -Os -mno-tls-direct-seg-refs -Wall -Wno-pointer-sign
-s -o
gpgkeys_hkp gpgkeys_hkp-gpgkeys_hkp.o
gpgkeys_hkp-ksutil.o ../util/libcompat.a -lcurl -s -L/usr/lib -L/usr/lib
-L/usr/lib
gcc -march=i686 -pipe -Os -mno-tls-direct-seg-refs -Wall -Wno-pointer-sign
-s -o
gpgkeys_finger gpgkeys_finger-gpgkeys_finger.o
gpgkeys_finger-ksutil.o ../util/libutil.a
gpgkeys_curl.c: In function 'main':
gpgkeys_curl.c:304: error: 'typeof' applied to a bit-field
...
make[2]: *** [gpgkeys_curl-gpgkeys_curl.o] Error 1
make[2]: Leaving directory `/usr/src/gnupg-1.4.9/keyserver'

The kernel guys had this problem with gcc 3.3 -> 3.4 in
http://linux.derkeiler.com/Mailing-Lists/Kernel/2004-07/4738.html:
"In the gcc-3.3 -> gcc-3.4 transition they changed gcc to
explicitly forbid using typeof on bitfields, see gcc
bugzilla #10333. This is not unreasonable, since typeof
and sizeof on bitfields can have strange semantics."

So why is it hitting gnupg now with gcc 4.2 -> 4.3?

-sandalle

--
Eric Sandall | Source Mage GNU/Linux Developer
eric AT sandall.us PGP: 0xA8EFDD61 | http://www.sourcemage.org/
http://eric.sandall.us/ | http://counter.li.org/ #196285

Attachment: signature.asc
Description: This is a digitally signed message part.




Archive powered by MHonArc 2.6.24.

Top of Page