While doing an emerge -e system for 2004.3 I get the following notices at the end of the emerge of the package: * Notice: /bin/ping is setXid, dynamically linked and using lazy bindings. This combination is generally discouraged. Try: LDFLAGS='-Wl,-z,now' emerge iputils * Notice: /bin/ping6 is setXid, dynamically linked and using lazy bindings. This combination is generally discouraged. Try: LDFLAGS='-Wl,-z,now' emerge iputils Other packages seem to be concerned too: glibc-2.3.4.20041102(Bug #76210), and pam-0.77-r1 (Notice: /sbin/pwdb_chkpwd is setXid, dynamically linked and using lazy bindings. This combination is generally discouraged. Try: LDFLAGS='-Wl,-z,now' emerge pam * Notice: /sbin/pam_timestamp_check is setXid, dynamically linked and using lazy bindings. This combination is generally discouraged. Try: LDFLAGS='-Wl,-z,now' emerge pam * Notice: /sbin/unix_chkpwd is setXid, dynamically linked and using lazy bindings. This combination is generally discouraged. Try: LDFLAGS='-Wl,-z,now' emerge pam ) Reproducible: Always Steps to Reproduce: 1. emerge -e system 2. 3. Portage 2.0.51-r3 (default-linux/x86/2004.3, gcc-3.4.3, glibc-2.3.4.20041102-r0, 2.6.9-gentoo-r13 i686) ================================================================= System uname: 2.6.9-gentoo-r13 i686 AMD Athlon(tm) XP 1700+ Gentoo Base System version 1.4.16 Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.92.0.2-r2 Headers: sys-kernel/linux26-headers-2.6.8.1-r2 Libtools: sys-devel/libtool-1.5.2-r7 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=athlon-xp -s -fomit-frame-pointer -pipe -funroll-loops -fprefetch-loop-arrays -fforce-addr -fmove-all-movables -mfpmath=sse,387 -mmmx -msse -m3dnow -momit-leaf-frame-pointer -frename-registers -fweb -ftracer" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/fax /usr/lib/mozilla/defaults/pref /usr/local/etc /usr/share/config /usr/share/cursors/xorg-x11/default/ /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 /var/spool/fax/etc" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=athlon-xp -s -fomit-frame-pointer -pipe -funroll-loops -fprefetch-loop-arrays -fforce-addr -fmove-all-movables -mfpmath=sse,387 -mmmx -msse -m3dnow -momit-leaf-frame-pointer -frename-registers -fweb -ftracer -fvisibility-inlines-hidden" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" GENTOO_MIRRORS="http://mirrors.sec.informatik.tu-darmstadt.de/gentoo/ http://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ ftp://ftp.uni-erlangen.de/pub/mirrors/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.de.gentoo.org/gentoo-portage" USE="x86 3dnow acl acpi alsa apm avi berkdb bitmap-fonts bzlib crypt cups curl dga encode esd exif flac foomaticdb ftp gd gdbm gif gtk gtk2 hal ide ipv6 ithreads jpeg libwww lzo mad maildir mhash mikmod mmx motif mpeg ncurses nptl oggvorbis openal opengl oss pam pcre pdflib perl pic png posix pthreads qt quicktime readline sdl shared sharedmem speex sse ssl svga tiff truetype xinerama xml2 xmms xpm xprint xv xvid zlib"
Same for me. This setXid warning pops up in several other packages, too, and has been discussed in various forum threads - without results. Some people seem to put the required LDFLAGS in their make.conf, but that doesn't seem to be the solution for what seems to be a per-package problem. As you don't get this message until *after* you emerged the package, it's a real nuisance...
Created attachment 50537 [details, diff] iputils-021109-r3.ebuild.diff This should do the trick for iputils
finally added to portage, but only for the setuid binaries
The problem seems to be back in iputils-20060512. It seems that the patch in this bug report didn't make it into the new ebuild. I've applied it manually and that makes the problem go away again. The same flags are also missing from the 2007002 ebuild.
no, different issue newer portage doesnt check setXid flags
