Summary: | env-update does not honor env.d ordering | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Pascal Roussel <pascal> |
Component: | [OLD] GNOME | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | critical | CC: | chris-gentoo, der_phox, dholth, diablobsb, djandruczyk, flatface, gbugs, gnome, humpback, jtshaw, khsongdr, mog.johnny, stuart, toolchain |
Priority: | Highest | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
portage-do-not-sort-ld_so_conf.patch
portage-cvs-do-not-sort-ld_so_conf.patch |
Description
Pascal Roussel
2004-03-08 06:08:13 UTC
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. *** |