Archaic wrote:
Watching a 6.1.1-1 CD build and saw this:
c++ -o nsHttpPipeline.o -c -DOSTYPE=\"Linux2.6.12\" -DOSARCH=\"Linux\"
-I/lfs-livecd/packages/firefox/mozilla/netwerk/protocol/h
Obviously, firefox is reading the running kernel, not the livecd kernel
(which isn't even built at this stage). I haven't investigated anything
so I don't even know if it matters.
Looks like it goes nowhere except informational dialogs. C and C++
preprocessor just can't make any significant compile-time decisions
based on strings.
Might it behoove the team to suggest that any particular version of the
CD be built from a host running the same version of LFS for the sake of
purity of the blfs segment of it?
No, that's absolutely impractical if one builds two LiveCD versions with
two different kernels one of which is 2.6.11.x (requires old udev
version incompatible with newer kernels).
Again, I have no idea if there are to be any side effects, but the
answer to that may lie in how far from an LFS versioned host you have
gotten (or possibly worse, from a non-LFS host) when beginning the CD
build.
Can't this "purity" be achieved by adjusting the uname wrapper in order
to lie about the kernel version?
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/livecd
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
