Jeremy Huntwork wrote: > This is nearly done, so I will go ahead and post results on this when I > have them. As Greg has explained, this will at least show that the > system can bootstrap itself and produce the same thing. That should have > at least some merit.
Here is the results via Farce: http://linuxfromscratch.org/~jhuntwork/farce-results There are 4 lines that, to me, stand out: unexpected FAIL: /usr/bin/libtool is different unexpected FAIL: /usr/bin/vim differs after stripping and processing unexpected FAIL: /usr/include/c++/4.0.2/i686-pc-linux-gnu/bits/stdc++.h.gch/O0g.gch is different unexpected FAIL: /usr/include/c++/4.0.2/i686-pc-linux-gnu/bits/stdc++.h.gch/O2g.gch is different The libtool is easy to explain, the differences in that amount to a different hostname used for each build. It contains a line like this: # Libtool was configured on host lfslivecd My hostname changed on the two builds - one was done on the livecd and the second, I rebooted into the new system and built on that. The vim one puzzles me a bit. :/ Also, I'm hoping that the stdc++.h.gch differences are due to the randomness that Ken and Greg talked about. > Seeing that he also explained the ICA method with a bit more detail, > I'll do another build afterwards following his method and share the > results of those. Well, now to try Greg's method and see what we get. -- JH -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
