Summary: | glib-2.0.4 cannot emerge | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Low Kian seong <low> |
Component: | New packages | Assignee: | Spider (RETIRED) <spider> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | azarah, low |
Priority: | High | ||
Version: | 1.2 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | This is the glib install log |
Description
Low Kian seong
2002-06-26 05:27:50 UTC
Created attachment 1818 [details]
This is the glib install log
okay, thanks for this, its really confusing and I dont know what to make of it... the build tells me everything should have gone nice.. but.. I'm ccing you azarah to see if you get anything from this.... after a chat on IRC you said you rebuilt glibc, so.... I dont know if that has anything to do with ldconfig. It looks more like the produced libglib-2.0.so (or file it is symlink to) gets corrupted for some reason. That or ld have the wrong search paths. I did some updates to libtool.eclass earlier ... try to emerge rsync in halv an hour or so, and try again. And ? Got it working ? no news here. There is a bug with libtool that causes nautilus initial builds to fail, thanks to Spider for this link: http://bugzilla.gnome.org/show_bug.cgi?id=75635 Anyhow, glib-2.0.4-r1 is updated with this fix, please try it out. And ... did -r1 fix it for you ? |