Matthew Burgess wrote:
Was the SE-Linux afflicted FC3 distro also because of host infection, or was that down to incorrect instructions? Basically what was happening was that (I think) glibc was being built in chapter 5 against the host's se-linux stuff. When we were chrooted in chapter 6, glibc wanted to enable se-linux support again, but obviously couldn't.
I think again, it's just the nature of our current build method. Not sure that there was either side to blame on that one. The point is that things like that get covered over with the cross-build method. And while we currently require that the host be a Linux system, afaict, the only requirements for a host with the cross-build instructions would be to have a gnu toolset available. (ie., if you started building ppc64 LFS on an OSX machine.) Granted, the ability to build for anything from anything is not the main reason for the change, but it does highlight the desired benefit of severly limiting the impact of the host system on the final build. If we weren't worried about what our end result was we also wouldn't take the time to run the testsuites on our toolchain...
-- JH -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
