Hello, Mikhail! Mikhail Kolesnik schrieb:
as far as i remember, you are only supposed to update the kernel-headers in your /usr/include directories, when upgrading glibc.
And this brings a broader problem: AFAIK, we have no reliable/documented way to safely rebuild toolchain. Looking from the point of distro's long release cycle, we might face a problem trying to upgrade tools like iproute2 or ipsec-tools.
Yes, that seems to be a never ending story. In ix86 it became more simple to bootstrap binutils/glibc/gcc/kernel and friends. It's also not such a big deal to just upgrade glibc in a running system... But on some embedded systems it's just a painful task to go thru the first LFS Chapter plus ton's of bugfixes and patches. I am still not sure if I'll stay with the latest developemnt snapshots of the native/cross-toolchain(s) to get more support/immediate feedback of the developers or go with the latest stable series plus a varying selection of patches. It would be fun to assemble a CCFS (Crossplatform Crux From Scratch) skript. My idea/wish/dream is to get to a point where an automated tool monitors toolchain changes and does a full automatic bootstrap of the toolchain plus some tests (from the Linux Test Project). It should also spit out a ISO Image if the build was successful. I would offer a server for free to do that. Well... sometimes, dreams come true. ;-) Greets, -- Clemens Koller __________________________________ R&D Imaging Devices Anagramm GmbH Rupert-Mayer-Straße 45/1 Linhof Werksgelände D-81379 München Tel.089-741518-50 Fax 089-741518-19 http://www.anagramm-technology.com