Summary: | glib >=2.3.4 seems to break glx? | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | David Li <matrixhax0r> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
David Li
2004-07-12 14:29:18 UTC
Ok, I changed my CFLAGS to something nicer ("-O2 -pipe"), reemerge, and it still doesn't work. hm I think its because 2.4.x kernels lack nptl support ... I have the newest glibc installed and it also installed the linux2.6-headers (2.6.6-r1) No problem for me because I use 2.6.7-gentoo-r9 $ genlop -i glibc * sys-libs/glibc Total builds: 7 Global build time: 7 hours, 12 minutes and 48 seconds. Average merge time: 1 hour, 1 minute and 49 seconds. Info about currently installed ebuild: * sys-libs/glibc-2.3.4.20040619 Install date: Mon Jul 12 23:57:55 2004 USE="nls nptl -pic -build -erandom -hardened -makecheck -multilib -debug" $ glxinfo name of display: :0.0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.2 ... i'm sort of inclined to close this invalid because of your CFLAGS. Messing with your system is really your own problem to deal with, I just sense you are looking for problems reading your report. The nptl story in comment #2 is probably right on track, but even then you have moved between 2.4 & 2.6 kernels in the past afaik or it still shouldn't happen. Anyway, the bottomline is that this is not a problem that would normally show on average user systems and I don't think there's much to fix here : downgrade your glibc or move to a 2.6 kernel. If you can reproduce on a clean system with sane cflags open a new report. hmm I think the problem is that glibc still wants to install the 26-headers on an 2.4 system and than builds against it. I use a 2.6.x kernel for more then 9 months now so it isn't a problem Indeed my glibc is not compiled with ntpl. I am wondering why ntpl is a USE flag to do it when it's not even in the use flag list (/usr/portage/profiles/use.desc)? Shouldn't there be some kind of mask preventing people from emerging the new one if ntpl is not in the USE flags? |