My sash-3.7 compiles are failing. It starts well enough: root@copasetic # emerge sash Calculating dependencies ...done! >>> emerge (1 of 1) app-shells/sash-3.7 to / >>> md5 src_uri ;-) sash-3.7.tar.gz >>> Unpacking source... >>> Unpacking sash-3.7.tar.gz to /var/tmp/portage/sash-3.7/work * Applying sash-3.6-fix-includes.patch... [ ok ] readline * Applying sash-3.6-readline.patch... [ ok ] >>> Source unpacked. gcc -O3 -march=pentium3 -fomit-frame-pointer -funroll-loops -pipe -fomit-frame-pointer -fforce-addr -fprefetch-loop-arrays -mfpmath=sse -Wall -Wmissing-prototypes -DHAVE_GZIP=1 -DHAVE_LINUX_ATTR=1 -DHAVE_LINUX_MOUNT=1 -DHAVE_BSD_MOUNT=0 -DMOUNT_TYPE='"ext3"' -DHAVE_READLINE -c -o sash.o sash.c sash.c: In function `fileman_completion': sash.c:536: warning: implicit declaration of function `completion_matches' sash.c:536: warning: assignment makes pointer from integer without a cast sash.c: In function `command_generator': sash.c:561: warning: suggest parentheses around assignment used as truth value sash.c: At top level: sash.c:1454: warning: `showPrompt' defined but not used gcc -O3 -march=pentium3 -fomit-frame-pointer -funroll-loops -pipe -fomit-frame-pointer -fforce-addr -fprefetch-loop-arrays -mfpmath=sse -Wall -Wmissing-prototypes -DHAVE_GZIP=1 -DHAVE_LINUX_ATTR=1 -DHAVE_LINUX_MOUNT=1 -DHAVE_BSD_MOUNT=0 -DMOUNT_TYPE='"ext3"' -DHAVE_READLINE -c -o cmds.o cmds.c [snip] But towards the end the troube begins: gcc --disable-shared -static -s -o sash sash.o cmds.o cmd_dd.o cmd_ed.o cmd_grep.o cmd_ls.o cmd_tar.o cmd_gzip.o cmd_find.o cmd_file.o cmd_chattr.o cmd_ar.o utils.o -lz -lreadline -lncurses /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/../../../libc.a(ssp.o)(.bss+0x0): multiple definition of `__guard' /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/libgcc.a(_stack_smash_handler.oS)(.bss+0x0):/var/tmp/portage/gcc-3.3.2-r2/work/gcc-3.3.2/gcc/libgcc2.c:2021: first defined here /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/../../../../i686-pc-linux-gnu/bin/ld: Warning: size of symbol `__guard' changed from 32 in /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/libgcc.a(_stack_smash_handler.oS) to 4 in /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/libgcc.a(_stack_smash_handler.oS) /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/../../../libc.a(ssp.o)(.text+0x90): In function `__stack_smash_handler': : multiple definition of `__stack_smash_handler' /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/libgcc.a(_stack_smash_handler.oS)(.text+0x90):/var/tmp/portage/gcc-3.3.2-r2/work/gcc-3.3.2/gcc/libgcc2.c:2036: first defined here /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/../../../../i686-pc-linux-gnu/bin/ld: Warning: size of symbol `__stack_smash_handler' changed from 728 in /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/libgcc.a(_stack_smash_handler.oS) to 817 in /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/libgcc.a(_stack_smash_handler.oS) cmd_ls.o(.text+0xa33): In function `listFile': : warning: Using 'getgrgid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking cmds.o(.text+0x41f): In function `do_chgrp': : warning: Using 'getgrnam' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/../../../libreadline.a(complete.o)(.text+0xfb1): In function `rl_username_completion_function': : warning: Using 'getpwent' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking cmds.o(.text+0x2df): In function `do_chown': : warning: Using 'getpwnam' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking cmd_ls.o(.text+0x9c1): In function `listFile': : warning: Using 'getpwuid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/../../../libreadline.a(complete.o)(.text+0xfa3): In function `rl_username_completion_function': : warning: Using 'setpwent' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/../../../libreadline.a(complete.o)(.text+0x104f): In function `rl_username_completion_function': : warning: Using 'endpwent' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking collect2: ld returned 1 exit status make: *** [sash] Error 1 !!! ERROR: app-shells/sash-3.7 failed. !!! Function src_compile, Line 37, Exitcode 2 !!! (no error message) My guess is that using the love-sources has some part in it. I have tried sash-3.6 and gcc-config i686-pc-linux-gnu-3.3.3 with similar resutls. Reproducible: Always Steps to Reproduce: 1. emerge 2.6.7-love5 2. emerge glibc 3. emerge sash Actual Results: !!! ERROR: app-shells/sash-3.7 failed. !!! Function src_compile, Line 37, Exitcode 2 !!! (no error message) Expected Results: sash merged Portage 2.0.50-r9 (hardened-x86-2004.0, gcc-3.3.2, glibc-2.3.3.20040420-r1, 2.6.7-love5) ================================================================= System uname: 2.6.7-love5 i686 Pentium III (Coppermine) Gentoo Base System version 1.4.16 distcc 2.13 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.3 [enabled] Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=pentium3 -fomit-frame-pointer -funroll-loops -pipe -fomit-frame-pointer -fforce-addr -fprefetch-loop-arrays -mfpmath=sse" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=pentium3 -fomit-frame-pointer -funroll-loops -pipe -fomit-frame-pointer -fforce-addr -fprefetch-loop-arrays -mfpmath=sse" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox sfperms strict" GENTOO_MIRRORS="http://gentoo.chem.wisc.edu/gentoo/ http://csociety-ftp.ecn.purdue.edu/pub/gentoo/ http://gentoo.mirrors.pair.com/" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X acpi aim alsa apache2 arts berkdb bluetooth crypt cups dvd emacs emacs-w3 flac foomaticdb gdbm gif gimp gimpprint gtkhtml hardened imlib java jikes jpeg junit kde lcd libwww mmx mozsvg mysql nls nptl opengl pam pcmcia perl pic pie ppds python qt quicktime readline sdl spell sse ssl tcpd tetex usb x86 xmms zlib"
(1) stop using love sources, they're a joke (2) update your glibc and/or gcc to fix the multiple guard definitions
Love-sources have their place, but you shouldn't really be reporting bugs on here if you're using them - either make absolutely sure you can reproduce the bugs with a supported kernel, or go and bug the love-sources guys.
love sources have their place; right next to all the other useless kernel patchsets at any rate, this isnt a kernel related bug, this is related to moving of the guard symbols between gcc and glibc ... if you have the latest stable versions of gcc/glibc, you shouldnt hit this bug
I suppose we all have our vices. I switched over to 2.6.8.1-mm3, but the error persists. It seems that love-sources is not involved. I will update glibc next.
2.6.8.1-mm3 is a joke as well. Sigh.. Either way this is no longer a bug.. Your system is just to far out of date.
