Trying to build nautilus (on alpha, but that doesn't matter) with CFLAGS=-g. It breaks on the following line in src/nautilus-server-connect.c setlocale (LC_ALL, ""); The problem is that LC_ALL isn't defined. It comes from <locale.h> which is normally included by <libintl.h>, but inside #ifdef __OPTIMIZE__ I think this should be fixed in Nautilus since it should be getting LC_ALL from <locale.h> instead of depending on the definition from <libintl.h>. Reproducible: Always Steps to Reproduce: 1. CFLAGS=-g emerge nautilus Actual Results: I sighed. Expected Results: Nautilus should have built, and trumpets should have announced its arrival. Portage 2.0.46-r9 (default-alpha-1.4, gcc-3.2.2, glibc-2.3.1-r3) ================================================================= System uname: 2.4.19 alpha EV67 GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://www.ibiblio.org/pub/Linux/distributions/gentoo" CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" PORTDIR="/usr/portage" DISTDIR="/usr/distfiles" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/usr/local/tmp" PORTDIR_OVERLAY="" USE="alpha crypt cups encode gif jpeg libg++ mikmod ncurses nls oss pdflib png qt qtmt quicktime sdl spell truetype xml2 xmms xv zlib gnome-libs gdbm berkdb readline tetex bonobo tcltk java guile ruby X gpm tcpd pam libwww ssl perl python imlib oggvorbis gnome gtk motif opengl mozilla -arts -esd -kde -slang ev6" COMPILER="gcc3" CHOST="alpha-unknown-linux-gnu" CFLAGS="-mcpu=ev67 -g -pipe" CXXFLAGS="-mcpu=ev67 -g -pipe" ACCEPT_KEYWORDS="alpha ~alpha" MAKEOPTS="-j2" AUTOCLEAN="yes" SYNC="rsync://rsync.gentoo.org/gentoo-portage" FEATURES="sandbox noclean noauto ccache"
you reporting this upstream yourself ? i'd like to see a patch for it.
Yeah, I'll report this upstream. I'll patch it in our tree until a new version is available that fixes the problem.
I've pushed this upstream... http://bugzilla.gnome.org/show_bug.cgi?id=105756
This is fixed in our ebuild via the same patch I pushed upstream.