Re: [gentoo-user] broken gcc-config and suspicious linux-headers 2.4.21

2004-02-13 Thread Wazow
Just for information of all those following this thread, there is an interesting related thread at forums: see http://forums.gentoo.org/viewtopic.php?t=132041 Andrzej Wazow wrote: Hi, I have recently upgraded to gentoo-sources 2.6.1. Now portage wants to emerge old 2.4 headers for some

Re: [gentoo-user] broken gcc-config and suspicious linux-headers 2.4.21

2004-02-12 Thread Gard Spreemann
On Wednesday 11 February 2004 21:29, Wazow wrote: Hi, I have recently upgraded to gentoo-sources 2.6.1. Now portage wants to emerge old 2.4 headers for some reason. What is causing it to do that? How can I avoid it? (I do not feel that application compiled with those is very safe to run).

Re: [gentoo-user] broken gcc-config and suspicious linux-headers 2.4.21

2004-02-12 Thread Marius Mauch
On 02/12/04 Gard Spreemann wrote: On Wednesday 11 February 2004 21:29, Wazow wrote: Hi, I have recently upgraded to gentoo-sources 2.6.1. Now portage wants to emerge old 2.4 headers for some reason. What is causing it to do that? How can I avoid it? (I do not feel that application

Re: [gentoo-user] broken gcc-config and suspicious linux-headers 2.4.21

2004-02-12 Thread Wazow
Hi Marius, Finally I got the answer I wanted! Marius Mauch wrote: I have recently upgraded to gentoo-sources 2.6.1. Now portage wants to emerge old 2.4 headers for some reason. What is causing it to do that? How can I avoid it? (I do not feel that application compiled with those is very safe to

Re: [gentoo-user] broken gcc-config and suspicious linux-headers 2.4.21

2004-02-12 Thread Marius Mauch
On 02/12/04 Wazow wrote: So now my situation is: My initial gentoo installation was compiled with 2.4 kernel (and so was my still used glibc). Then I upgraded to gentoo-dev-sources 2.6.1 and wondered why /usr/src/linux was not pointing to new kernel sources. I thougth that it was a

Re: [gentoo-user] broken gcc-config and suspicious linux-headers 2.4.21

2004-02-12 Thread Wazow
Thanks. I give it a try, right now starting with emerge -uDv kernel-headers. Gee, this package is huge. How come portage reports that headers are 30MB? Andrzej Marius Mauch wrote: On 02/12/04 Wazow wrote: So now my situation is: My initial gentoo installation was compiled with 2.4 kernel

Re: [gentoo-user] broken gcc-config and suspicious linux-headers 2.4.21

2004-02-12 Thread Marius Mauch
On 02/12/04 Wazow wrote: Thanks. I give it a try, right now starting with emerge -uDv kernel-headers. Gee, this package is huge. How come portage reports that headers are 30MB? Because they are extracted from a normal kernel tarball. Marius -- Public Key at

Re: [gentoo-user] broken gcc-config and suspicious linux-headers 2.4.21

2004-02-12 Thread Wazow
Now I have emerged kernel-headers-2.4.21. Indeed /usr/include/linux was downgraded from 2.6.1 to 2.4.21, also portage officially did not downgrade anything. This was a quite overwrite... In the end I see two interesting messages: * Kernel headers are usually only used when recompiling glibc,

[gentoo-user] broken gcc-config and suspicious linux-headers 2.4.21

2004-02-11 Thread Wazow
Hi, I have recently upgraded to gentoo-sources 2.6.1. Now portage wants to emerge old 2.4 headers for some reason. What is causing it to do that? How can I avoid it? (I do not feel that application compiled with those is very safe to run). Finally see the gcc-config line. Why does it show

Re: [gentoo-user] broken gcc-config and suspicious linux-headers 2.4.21

2004-02-11 Thread Kent Smith
Same here. I'm not sure what to do about it either, sorry! (Help?) On Wed, 2004-02-11 at 12:29, Wazow wrote: Hi, I have recently upgraded to gentoo-sources 2.6.1. Now portage wants to emerge old 2.4 headers for some reason. What is causing it to do that? How can I avoid it? (I do not