I am getting a compile error in camel/camel-service.c ; the function in question looks like this : struct addrinfo * camel_getaddrinfo(const char *name, const char *service, const struct addrinfo *hints, CamelException *ex) { (....) #ifndef ENABLE_IPv6 (....) hints->ai_family = AF_INET; #endif The compiler sees hints (a const parameter) being assigned to, and barfs. This error occurs for me with both with hardened gcc-3.4.2-r1 and unhardened gcc-3.3.4 Reproducible: Always Steps to Reproduce: 1. USE="crypt -debug doc -ipv6 -kerberos ldap mozilla nntp pda spell ssl" emerge =evolution-2.0.1 Actual Results: gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I./.. -I../intl -I../e-util -DCAMEL_LIBEXECDIR=\"/usr/libexec/evolution/2.0/camel\" -DCAMEL_PROVIDERDIR=\"/usr/lib/evolution/2.0/camel-providers\" -DG_LOG_DOMAIN=\"camel\" -pthread -DXTHREADS -D_REENTRANT -DXUSE_MTSAFE_API -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gal-2.2 -I/usr/include/gtk-2.0 -I/usr/include/libgnomecanvas-2.0 -I/usr/include/libxml2 -I/usr/include/libglade-2.0 -I/usr/include/libgnomeprint-2.2 -I/usr/lib/gtk-2.0/include -I/usr/X11R6/include -I/usr/include/atk-1.0 -I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/include/freetype2/config -I/usr/include/libart-2.0 -I/usr/lib/mozilla/include/nspr -I/usr/lib/mozilla/include/nss -march=athlon-xp -O2 -pipe -frename-registers -fomit-frame-pointer -Wall -Wmissing-prototypes -Wno-sign-compare -c camel-service.c -MT camel-service.lo -MD -MP -MF .deps/camel-service.TPlo -fPIC -DPIC -o .libs/camel-service.o camel-service.c: In function `camel_getaddrinfo': camel-service.c:897: warning: assignment from incompatible pointer type camel-service.c:900: error: assignment of read-only member `ai_family' make[3]: *** [camel-service.lo] Error 1 Expected Results: successful emerge System uname: 2.6.8-gentoo i686 AMD Athlon(tm) XP 2500+ CFLAGS="-march=athlon-xp -O2 -pipe -frename-registers -fomit-frame-pointer " gcc-3.4.2-r1 glibc-2.3.3.20040420-r1
try without -frename-registers -fomit-frame-pointer
My apologies, turns out this was fixed in #66024. This is what I get for not syncing more than once a day... *** This bug has been marked as a duplicate of 66024 ***