On Sun, Sep 17, at 10:23 Vladimir A. Pavlov wrote: > > > > Now I have a package that cannot be compiled with glibc-2.3.6 since it > > > requires glibc-2.4. > > > > Is this real, or a made up example ? Any _source_ that needs a > > specific version of glibc is at least unusual. > > It's my guess about _binary_ compatibility. As I said before, > rebuilding a whole system is rather expensive in terms of the time > required.
I think is the the other way around. Upgrading glibc requires much more time than a clean install. To coexist two different compiler versions in the same system is plain easy,but glibc? Almost every single package is linked against the library and use its functions. I think and I am not an expert that using a virtual machine like xen or by just using two partitions with different glibc versions is much more convenient for your purposes. I was told,back when I was using gentoo,that in every major glibc upgrade I should have to rebuild the whole system again,and not once but twice (correct me if I am wrong). As ken pointed out the real solution to your problem is by scripting the whole build. You can dump out the commands direct from the XML sources by using something like. xsltproc --xinclude --nonet --output /tmp/lfs/ stylesheets/dump-commands.xsl index.xml Then you can run some sed's and change some options,and there you have the scripts. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
