Every time I play with Linux again, I'm more impressed. It's going to be a while before I relapse to Windows...

So, first I tried compiling WINE, and now I'm running the tgz package binary, and when I run it, it says...

wine: glibc >= 2.3 without NPTL or TLS is not a supported combination.
It will most likely crash. Please upgrade to a glibc with NPTL support.

Because WINE asked so nicely, I decided I would just do that. In fact, I'd decided, I would recompile all sorts of things, because scrolling code lights my fire(s). After I got GCC, gmp, binutils, gperf, mpfr, texinfo, and all sorts of other things that had smaller numbers before I made the numbers bigger, I started on glibc-2.5.

I R the FM, but not too much, I have to support my position as a proper newbie... and I do the thing, and then the other thing, and then that one thing, and some other things, and halfway (every point in a long compile is halfway, it's a bit more optimistic) through make, it goes...

AHHHHHHHHHHH! YOU'RE GONNA DIE!

And then I switch out of GAIM, and I see...

pthread_mutex_timedlock.c: In function 'pthread_mutex_timedlock':
pthread_mutex_timedlock.c:276: error: '__NR_clock_gettime' undeclared (first use in this function)
pthread_mutex_timedlock.c:276: error: (Each undeclared identifier is reported only once
pthread_mutex_timedlock.c:276: error: for each function it appears in.)
make[2]: *** [/compile/glibc-2.5/target/nptl/pthread_mutex_timedlock.o] Error 1
make[2]: Leaving directory `/compile/glibc-2.5/nptl'
make[1]: *** [nptl/subdir_lib] Error 2
make[1]: Leaving directory `/compile/glibc-2.5'
make: *** [all] Error 2

And then I started to have a hissy fit, and I cried for a while.. the manual didn't say what to do if I started crying, or if I started to become a threat to myself and others, or if I woke up, hungover in the most cliche gutter in town (it's at 26th and Locust), so I opened Kaboodle and bubbled in unbridled glee at the fact that I could actually use sound, a usb mouse, an NTFS mount, and a wireless card on Linux together. I was doing my bubbling to Stargate SG1, in case it's important to know to solve my problem.

You need to be using a 2.6 kernel and kernel headers or glibc-2.5 won't compile. Did you use the 2.4 kernel when you installed Slackware 11?

BTW, the toolchain is usually built kernel headers, glibc, binutils, then gcc in that order. With gmp and mpfr between binutils and gcc if you want FORTRAN support in gcc. Weird things can happen if your toolchain is busted. Have fun.

Oh... I didn't know 2.6 was an option with Slack 11, and I'd actually been looking for that 'toolchain' thing (now that I know it is 'toolchain'... thing), but I was looking for whether it was GCC or GlibC first.

Is there a fast way to switch to 2.6 with Slackware 11, or would it be better to reinstall the OS? I already have a FAT32 partition I've been moving things between, so a format would be kind of painless.

I also have an Athlon64, a K8N4-E, a Radeon X700, 2 ide drives and one sata drive plugged into the NVidia controller. I've tried to build 2.6 kernels on here a few times, and I keep screwing them up. I don't know if I'm configuring it right, or if there's things I have to do 'post upgrade' to make things work right.

Actually, I guess there's some things that are so commonly known with Linux that people don't bother pointing some things out in other documents, like to 'switch' to GCC4.1, I had to change my symlinks. I already figured this, but all the documents I saw didn't clarify this at all, and I spent a while looking for the command "ls -n [symlink]" when I needed to know where the gcc symlink was already pointing.