Hi all, I'm trying to build a development environment that's completely independant of the underlying OS so that when I do an upgrade of my OS, it can't have any effect on my development environment with new quirks in gcc or glibc.
What I basically want is for example a /opt filesystem which would have the following: - /opt/glibc/<version-x> - /opt/glibc/<version-y> - /opt/binutils/<version-z> - /opt/binutils/<version-a> - /opt/gcc/<version-b> - /opt/gcc/<version-c> Where glibc/x, gcc/c and binutils/z are dependant on each other and _only_ each other but completely separate of the OS (same goes for the other versions) This way I could basically "recreate" the different versions of RedHat EL by collecting their glibc / gcc / binutils versions, compile them against each other and by "merely" (understatement, I know) setting my PATH variable, I could have the compiler, libc and linker of my choosing. Is such a setup feasible with the documentation found in LFS? Are there any caveats I should be aware of? Any suggestions? Kind regards, Jeroen Kleijer PS: I'm aware that this seems overkill (why not keep a copy of the old OS lying around?) but when you've got several projects running that have to be supported for x number of years and you've got different projects with different requirements and you've got an IT crew that wants to upgrade for vendor support, then the above might actually become pretty desirable. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
