When I try to emerge vte I get: /usr/NX/lib/libXcompext.so.1: undefined reference to `_NXSplitParams' /usr/NX/lib/libXcompext.so.1: undefined reference to `_NXEnableCleanAlloc' /usr/NX/lib/libXcompext.so.1: undefined reference to `_NXEnableCleanFlush' /usr/NX/lib/libXcompext.so.1: undefined reference to `_NXLostSequenceFunction' /usr/NX/lib/libXcompext.so.1: undefined reference to `_NXEnableImageFrame' /usr/NX/lib/libXcompext.so.1: undefined reference to `_NXFlushSize' /usr/NX/lib/libXcompext.so.1: undefined reference to `_NXColorParams' /usr/NX/lib/libXcompext.so.1: undefined reference to `_NXEnableImageSplit' /usr/NX/lib/libXcompext.so.1: undefined reference to `_NXEnableCleanImages' /usr/NX/lib/libXcompext.so.1: undefined reference to `_NXEnableImageMask' /usr/NX/lib/libXcompext.so.1: undefined reference to `_NXImageEnvironmentCached' /usr/NX/lib/libXcompext.so.1: undefined reference to `_NXCleanupEnvironmentCached' /usr/NX/lib/libXcompext.so.1: undefined reference to `_NXEnableCleanGet' /usr/NX/lib/libXcompext.so.1: undefined reference to `_NXEnableCleanSend' collect2: ld returned 1 exit status make[2]: *** [reflect-vte] Error 1 make[2]: Leaving directory `/var/tmp/portage/vte-0.11.10/work/vte-0.11.10/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/vte-0.11.10/work/vte-0.11.10' make: *** [all] Error 2 !!! ERROR: x11-libs/vte-0.11.10 failed. !!! Function gnome2_src_compile, Line 39, Exitcode 2 !!! compile failure Reproducible: Always Steps to Reproduce: 1. emerge vte Portage 2.0.50-r1 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.4.20-gentoo-r5) ================================================================= System uname: 2.4.20-gentoo-r5 i686 AMD Athlon(tm) XP 2100+ Gentoo Base System version 1.4.3.13 Autoconf: sys-devel/autoconf-2.58-r1 Automake: sys-devel/automake-1.7.7 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-xp -O3 -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/NX/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3/share/config /usr/share/config /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-march=athlon-xp -O3 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://ftp.easynet.nl/mirror/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X apm arts avi berkdb bonobo cdr crypt cups encode esd foomaticdb gdbm gif gnome gphoto2 gpm gtk gtk2 gtkhtml guile imlib java jpeg libg++ libwww mad mikmod motif mozilla mpeg mysql ncurses nls oggvorbis opengl oss pam pdflib perl png python qt quicktime readline sdl slang spell ssl svga tcltk tcpd tetex truetype x86 xft xml2 xmms xv zlib"
where does /usr/NX stuff come from ?
It comes from net-misc/nxserver-personal
well i don't know why vte wants to include this, but the problem is nxserver then.
Same problem with mozilla...
Managed to reproduce. This looks like a Portage bug. If you look in your /etc/ld.so.conf file, you'll see that the search order of the directories does NOT match the order dictated in /etc/env.d directory. To fix this by hand, move the NX lib directory below the X11R6 directory in /etc/ld.so.conf, run ldconfig again, and then re-emerge. This procedure worked for me. Be warned - until this bug is fixed in Portage, future emerges are likely to screw up the order in this file once more. Re-assigned to dev-portage@gentoo.org. Best regards, Stu
Ok .. worked for me too Thanks
*** Bug 45866 has been marked as a duplicate of this bug. ***
Fixed in CVS.
*** Bug 46384 has been marked as a duplicate of this bug. ***
*** Bug 45546 has been marked as a duplicate of this bug. ***
*** Bug 42201 has been marked as a duplicate of this bug. ***
*** Bug 48664 has been marked as a duplicate of this bug. ***
Portage team, Any chance of looking at this and fixing it? Thanks, Stu
*** Bug 50354 has been marked as a duplicate of this bug. ***
*** Bug 53277 has been marked as a duplicate of this bug. ***
Created attachment 33576 [details, diff] portage-do-not-sort-ld_so_conf.patch Fix against portage-2.0.50-r8
Created attachment 33577 [details, diff] portage-cvs-do-not-sort-ld_so_conf.patch Fix against cvs.
Please guys, here is an patch and real simple as well - two liner without the comments.
>>> a=["c","b","a","z"] >>> for x in a: ... print x ... c b a z
I think you're chasing the wrong problem or something a lot deeper than a python quirk. Mutible or immutible, they don't get sorted in a for-loop. I can add the patch, but I imagine the problem lies elsewhere. Explicitly env-update before you change something. There might be a cache in play here or old env-update runs driving the problem. Please double check. There _used to be_ an explicit sort for ld.so in 2.0.50 through 50-r6 that was removed. It was only in 2.0.50. Mutible: >>> a={} >>> a["A"] = ["a","c","b","d","e","q","r","z","a"] >>> a["B"] = ["a","c","b","r","z","d","e","f"] >>> for x in a["A"]: ... print x ... a c b d e q r z a >>> for x in a["B"]: ... print x ... a c b r z d e f Immutible: >>> a["B"] = ("a","c","b","r","z","d","e","f") >>> for x in a["B"]: ... print x ... a c b r z d e f
Bah, Ok, so I was on crack, and did not notice it was Ok _before_ starting to tinker with it. Close the bug if its fixed Nick :)
Ok. Closed.
*** Bug 52080 has been marked as a duplicate of this bug. ***
*** Bug 64323 has been marked as a duplicate of this bug. ***
*** Bug 76356 has been marked as a duplicate of this bug. ***
