michael.kearns at saaconsultants.com
Mon Apr 7 02:32:42 PDT 2008
J. Greenlees wrote:
> Michael Kearns wrote:
>> Having decided to have another go at LFS (been through the process a
>> couple of times before, a few years back), I grabbed the 6.3 (amd64)
>> LiveCD, and followed the latest development book.
> It's usually recommended to use CLFS for building 64 bit right now.
> /Adding capabilty for x86_64 hosts is a major objective of the upcoming
> LFS 7.0 currently under development./
Thanks for that. I had just assumed the 64-bit would be handled under
the basic LFS, as there is a seperate LiveCD. I'll restart and give it a
go following the CLFS book - can I still use the same LiveCD ?
>> I downloaded all of the latest tool sources and patches (would be great
>> to have a txt file on those pages, containing all of the URLs, to use
>> with wget -i ), and followed through the book (which doesn't mention how
>> to unpack the sources, not that it's very difficult, but...)
> This functionality is in the scripted install in jalfs. :)
I'd avoided any automation, as it's been a while since my last rebuild
and so I wanted to ensure I was very much hands on with every aspect. I
did find that I could get the list from a copy-paste using the browser
page-info->links dialog though ;)
>> On the first pass of building the toolchain, binutils worked fine, but
>> on coming to build gcc it complains at the first compilation that it
>> can't find stubs-32.h - I checked, and sure enough it's not there.
>> Not knowing enough about how the 32/64 bit stuff is handled, what could
>> I have done wrong, and is this something that needs changing ?
> /There are quite a few differences in building 32 bit and 64 bit, CLFS
> has this covered more than LFS does at this time.
I'll start reading up.
More information about the lfs-support