Eric Pozharski <why...@pozharski.name
> with <stc0hv$btd$1...@dont-email.me
> John McCue wrote:
>> Mike Small <sma...@panix.com
>>> There's supposed to be a new glibc today or so. I guess it would be
>>> way too late to take that, right? That would count as too major a
>>> change for a freeze? I'm curious how much of a headache it is to
>>> upgrade the c library, since I'm about to attempt it on my linux from
>>> scratch partition.
>> I think uprading glibc is a big PITA, but I never attempted it.
>> Others here will probably know for sure.
> It's sure upgrading libc is scary however it's not PITA. It has
> potential for FUBAR though. Just remember, the potential is just this
> -- potential. Whatever could possibly go wrong can be fixed.
> p.s. Yes, I had screwed up when aaa-libraries had been renamed. Fixed,
> secured procedures, and developed more habits.
> p.p.s. I'm not helping here, am I?
No, it's helpful. This isn't my slackware partition only my linux from
scratch one, so it's useful to know it's a "learning exercise" vs. me
likely having to start over in the book. The book itself recommends
starting over when changing glibc+compiler, but the appendices in glibc
info and faq don't make it sound THAT bad. Maybe I need to figure out
how to distinguish glibc headers vs. non-glibc headers to clean out
headers no longer in the new library, but they seem to be commented
consistently. And there are some things going on in recent glibc shared
object files with merging libraries and changing how symlinks are done
(or not done). That should be interesting.
I guess it's clear slackware 15.0 won't take the new libc. Sounds like
release is imminent.