On Sun, 2004-02-01 at 11:24, Aaron Walker wrote:
On Sun, 2004-02-01 at 07:59, Alec Berryman wrote:
> On Sun, Feb 01, 2004 at 11:54:52AM +0000, Matt Wilson wrote:
> > as well). So I was wondering if there's anyway I can use 2.6.* headers
> > for compilation instead? I'm using 2.6.1 without any problems and am
> > considering giving NPTL a try and once again noticed that glibc needs
> > linux-headers-2.4.* ... </rant>
> 
> Last I heard a number of packages, maybe including glibc, wouldn't compile
> cleanly with the 2.6 headers.  You certainly can fiddle around with the
> ebuilds and start using the 2.6 headers, though.

I've done two NPTL installs so far, and haven't had any problems
whatsoever with glibc.  If you use X or svgalib, however, you will have
problems getting those to compile correctly.  Both of mine have been
server installs, so I haven't needed those packages.

In case anyone is feeling experimental (if not then you probably
shouldnt be messing with NPTL in the first place.. not yet anyways), I
installed w/NPTL by doing the following:

1) Boot LiveCD
2) Do normal install stuff until you get to the part where you need to
edit make.conf
3) Put nptl in the USE flags
4) Edit /usr/portage/sys-kernel/linux-headers/linux-headers-2.6.ebuild
and add you architecture to the KEYWORDS varibale after "-*", for
example KEYWORDS="-* x86"
5) Run /usr/portage/scripts/bootstrap-2.6.sh to start stage 1.
6) Add "~x86" to ACCEPT_KEYWORDS in make.conf.  This is needed for NPTL.
7) continue install while crossing fingers.

HTH,
Aaron




--
[EMAIL PROTECTED] mailing list

I have not run across any problems, other than X and svgalib and mentioned above.  For a work around I used X version 4.3.99.902 and it compiled fine and seems rock stable.  As for svgalib, I used the -B flag on one of my stable machines and just installed the binary package that way.   

Reply via email to