I tried to upgrade quagga to the latest version marked stable in x86 (which is the ~amd64 version). Reproducible: Always Steps to Reproduce: 1. emerge quagga Actual Results: The compile fails with: mkdir .libs x86_64-pc-linux-gnu-gcc -march=athlon64 -O2 -pipe -fomit-frame-pointer -o .libs/zebra zserv.o main.o interface.o connected.o zebra_rib.o redistribute.o debug.o rtadv.o zebra_snmp.o zebra_vty.o irdp_main.o irdp_interface.o irdp_packet.o router-id.o ioctl.o ipforward_proc.o if_netlink.o if_proc.o rt_netlink.o rtread_netlink.o -lcap ../lib/.libs/libzebra.so -lm -lcrypt -lreadline -lcurses -Wl,--rpath -Wl,/usr/lib/quagga ../lib/.libs/libzebra.so: undefined reference to `cap_init' ../lib/.libs/libzebra.so: undefined reference to `cap_get_flag' ../lib/.libs/libzebra.so: undefined reference to `cap_clear' ../lib/.libs/libzebra.so: undefined reference to `cap_set_flag' ../lib/.libs/libzebra.so: undefined reference to `cap_set_proc' ../lib/.libs/libzebra.so: undefined reference to `cap_free' collect2: ld returned 1 exit status make[2]: *** [zebra] Error 1 make[2]: Leaving directory `/var/tmp/portage/quagga-0.98.2/work/quagga-0.98.2/zebra' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/quagga-0.98.2/work/quagga-0.98.2' make: *** [all] Error 2 Expected Results: Installed :) Portage 2.0.51-r15 (default-linux/amd64/2004.3, gcc-3.3.4, glibc-2.3.4.20041102-r0, 2.6.10-hardened-r3 x86_64) ================================================================= System uname: 2.6.10-hardened-r3 x86_64 AMD Athlon(tm) 64 Processor 3000+ Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Feb 20 2005, 11:25:14)] dev-lang/python: 2.3.4-r1 sys-apps/sandbox: [Not Present] sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.9.5, 1.5, 1.4_p6, 1.6.3, 1.8.5-r3, 1.7.9-r1 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.16 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CFLAGS="-march=athlon64 -O2 -pipe -fomit-frame-pointer" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/bind /var/qmail/alias /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon64 -O2 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://gentoo.blueyonder.co.uk http://www.mirrorservice.org/sites/www.ibiblio.org" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/dump/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="amd64 acl aim alsa apache2 aper avi berkdb bzlib cdparanoia crypt dga directfb dv dvd dvdr dvdread encode faac faad ffmpeg fla flash gd-external gdbm gif gmp gtk gtk2 hardened ieee1394 ipv6 jabber jack java jpeg kde live lzo mad maildir matroska memlimit mozilla mozsvg mp3 mpeg mpeg4mplayer msn network nls nodrm ntlm oggvorbis opengl oscar pcre perl php pic pie png postgres quotas readline real rrdtool rtc samba sdl session sftplogging ssl svg tga theora tiff truetype truetype-fonts underscores v4l v4l2 voodoo3 xanim xfs xml2 xmms xv xvid xvmc yahoo yv12 zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
I just tried to update libcap to the latest - from 1.10-r4 to 1.10-r5, and it has compiled successfully. Could you put a requirement in the ebuild for libcap-1.10-r5 for AMD? Many thanks.
Sorry, overwrote your change of assignee
libcap-1.10-r5 is the single version available in portage since Feb the 9th 2005.
Yes, my point is that if quagga-0.98.2 fails to compile unless libcap-1.10-r5 is installed, then it should be listed in the ebuild as a requirement, so that trying to install quagga upgrades libcap.
yes, sure. lets force those damn lazy peeps to update their sistem at least once in 6 months, even though they are too lazy to issue a emerge -uDN world. we all love to have such useless bugs filling up bugzilla (which may hold water some time ago). bye now.
I don't want to update "world" every now and then. I think you're missing the point. Maybe you guys all update your boxes every day, but these are servers at work, so I only upgrade packages for security reasons. I simply think that if package x needs y-0.0.2 to work correctly, it should be a dependancy listed.
Just change the line in the ebuild from: sys-libs/libcap to >=sys-libs/libcap-1.10-r5 and all will be good.
done