On Fri, 30 Sep 2005, Jim Gifford wrote:
We are currently trying to stablize the Cross-LFS book.
Any thoughts on a package freeze for existing packages, particularly
glibc ? (That is, freeze versions unless it becomes clear that a
different version will solve problems). I'm preparing to start some
fresh builds (x86, x86_64-64, x86_64 on the same machine), hopefully
tomorrow, but if we upgrade glibc each week my test results will be
worthless by the time I have them ;)
Outstanding Issues
PPC
Yaboot
The only issue I've noticed is the errors in the list of files to
install into /boot (/me admits to still not getting around to correcting
this). Anything else ?
Pure64 Builds
Bootloaders, what to do, suggestions welcomed, Biggest concerns
Silo and Grub lack of ability to be compiled as 64 Bit. -- Programmers
welcome!!
For x86_64-64 lilo compiles and works now, or at least it did last time
I checked.
Book
Update the earilier chapters of the book to reflect cross-compiling
Add all missing configuration lines
Any thoughts on what to do about space/time measurements ? I'm not a
big fan of SBUs, but (at least on non-cross) they have some element of
repeatability if people don't get too finicky with how precisely they
measure them. I think Manuel had a suggestion about what to use as an
approximate SBU when building the final system if this was a true
cross-build. Maybe we could have SBUs for the first part, and NBUs
(native build units) for the temp tools and final system.
I'm fairly sure that the space used in the first part of the build will
depend on both the host and the target (e.g. ppc32 instructions are all
32 bits, and building glibc back in the days of LFS-5.0 took a lot more
space on ppc than on x86).
Ken
--
das eine Mal als Tragödie, das andere Mal als Farce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
