--- Arnie Stender <[EMAIL PROTECTED]> wrote: > I am still trying to get a running gnome desktop on > my pure 64 CLFS > running on an AMD64 AtholnX2. I'm getting close to > the end of the GNOME > Core packages and trying to compile libxklavier-2.0 > which is required by > gnome-applets. The make dies after getting a huge > string of errors which > for the sake of not having to go through them all I > will trim down: > > gcc -DHAVE_CONFIG_H -I. -I. -I.. -Wall -Werror > -DDATA_DIR=\"/usr/share/libxklavier\" -I. > -I/usr/include > -I/usr/include/libxml2 -I/usr/X11R6/include -I.. > -DXKB_HEADERS_PRESENT=1 > -DENABLE_XKB_SUPPORT=1 -DENABLE_XMM_SUPPORT=1 -g -O2 > -MT > xklavier_config.lo -MD -MP -MF > .deps/xklavier_config.Tpo -c > xklavier_config.c -fPIC -DPIC -o > .libs/xklavier_config.o > cc1: warnings being treated as errors > xklavier_config.c: In function > '_XklNodeGetXmlLangAttr': > xklavier_config.c:32: warning: pointer targets in > passing argument 1 of > 'strlen' differ in signedness > xklavier_config.c:32: warning: pointer targets in > passing argument 2 of > '__builtin_strcmp' differ in signedness > xklavier_config.c:32: warning: pointer targets in > passing argument 2 of > '__builtin_strcmp' differ in signedness > xklavier_config.c:32: warning: pointer targets in > passing argument 1 of > 'strlen' differ in signedness > xklavier_config.c:32: warning: pointer targets in > passing argument 2 of > '__builtin_strcmp' differ in signedness > snip snip > make[2]: *** [xklavier_config.lo] Error 1 > make[2]: Leaving directory > `/usr/src/secondary/libxklavier-2.0/libxklavier' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory > `/usr/src/secondary/libxklavier-2.0' > make: *** [all] Error 2 > > Does any body have suggestions for fixing this? What > I cut was a > continuation of message like the above from > xklavier_config.c.
It seems that the problem comes from this: "> cc1: warnings being treated as errors" It's due to the gcc flag: -Werror, which force all warnings (and the warnings seem harmless) to be considered as errors. See the following message: http://linuxfromscratch.org/pipermail/blfs-dev/2006-February/013468.html which give you a solution with a single command. Not everyone seems to have this problem, according the answer to this post. Regards G. Moko __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
