Just looked on gnu site and noticed 2.4 was out, however this time there's
no linuxthreads with it (latest is 2.3.6), so those wishing to upgrade are
forced to stick with 2.3.6 or scrap linuxthreads. (Suppose you could always
install 2.3.6 in /lib and 2.4 in /lib/tls, but that seems more hassle than
its worth).

Guess we'll either be seeing a move to 2.6 permanently, or slackware will
hang behind on latest version of glibc for a while.

Martin

Martin J. Green wrote :

> Guess we'll either be seeing a move to 2.6 permanently, or slackware will
> hang behind on latest version of glibc for a while.

From the Slackware current Changelog:
"a/glibc-solibs-2.3.6-i486-3.tgz: Recompiled against 2.4.32 and 2.6.15.6
kernel headers. Yes, I have seen that shiny-looking glibc-2.4 release on
ftp.gnu.org, but glibc-2.4 completely drops support for linuxthreads,
and therefore will not support vanilla Linux 2.4.x kernels. I don't
think we're quite ready for that yet around here."
--
Thomas O.

This area is designed to become quite warm during normal operation.

"Thomas Overgaard" <thover@post2.tele.dk> wrote in message
news:5pmif3-fp4.ln1@news.inet.tele.dk...

> From the Slackware current Changelog:
> "a/glibc-solibs-2.3.6-i486-3.tgz: Recompiled against 2.4.32 and 2.6.15.6
> kernel headers. Yes, I have seen that shiny-looking glibc-2.4 release on
> ftp.gnu.org, but glibc-2.4 completely drops support for linuxthreads,
> and therefore will not support vanilla Linux 2.4.x kernels. I don't
> think we're quite ready for that yet around here."

Yep, never saw that in ChangeLog, but knew as much anyways.