lfs for x86_64 with slamd64 host
 

Hi, all.

I'm running slamd64 (i.e. slackware x86_64) and I'd like to build LFS for this system (an EM64T). I just have a few questions:

1. Do I need to use CLFS or would LFS be fine? (Seeing as I'm not actually cross-compiling, because the target architecture is the same as the host?)

2. Does / will it compile just for generic x86_64 or will it eb able to make use of my EM64T's specific features like sse3 and things like that (not quite sure what the difference is between the EM64T and the athlon 64 chips)?

I would like to have it in 64bit because my chip has that capacity but it's also perfectly content to run 32bit OS's (It ran Mandrake 10, slackware 10.2 and even windoze fine before I realised that I actually had a 64bit chip and swiched to slamd64). Is it worth the extra effort that seems to be involved?

Edit: One more quick question: Will I have to do anything extra to use my chip's hyperthreading or should I just turn it off?

Thanks
silkenphoenixx

I'm sure the folks in this forum that are smarter than I will correct this, but...

If you want to provide multilib support (i.e., 32-bit and 64-bit), you will need to use the CLFS multilib book. You'd need to know what needs to be added to the LFS commands to ensure 64-bit support is enabled to use the LFS book. I'd recommend just following the CLFS book.

"Turning on" specific uP features like sse3 is done when you configure the kernel. Configuring the kernel is not really any different in (C)LFS than in other distros. As far as any packages taking advantage of certain uP features, those would be toggled with configure script options. There are typically other options that could be set/unset than the CLFS book sets/unsets.

The CLFS books are kinda like a recipe. You can leave out one of the ingredients (CLFS configure option) and the cookie (system) will likely taste like sh*t (not work). However, you can alway add some raisins and nuts (enable other package features) that aren't necessarily called out in the recipe (CLFS book). Then the cookie (system) will be scrumpdilicious (customized).

Ok, that's helpful. I'm fairly new in the Linux world (Started using Linux Sept 2005, finally got rid of windows march of this year) and configuring the kernel is something that I've never attempted (unless installing nvidia drivers counts! :-) ) I suppose I'd learn how on kernelnewbies.org?

Thanks much
silkephoenixx

btw, I tried using just LFS, but it failed when compiling gcc on the first pass, so I guess I'll stick to clfs. Another question that I have is, if I get it right, I'd like to cross-compile on my desktop for a really old acer laptop that I came across (366mhz celeron 64mb ram). How would I go about transferring the install to the laptop's drive? The idea that I had would be to compile it onto a usb hard disk, boot off a live cd, format and copy the stuff onto the hard disk, then chroot to do final configuration (like installation of lilo and stuff). Would this work?

I've never cross-compiled on one machine for another so I wouldn't want to say yes or no. I see a potential problem with changing the host system halfway through the process. You'd have to be careful about that. Probably if you completed the "If You're Going to Boot" chapter (chapter 7 in the multilib book) you wouldn't even need to chroot on the laptop. Maybe you could boot the laptop from a LiveCD and install LFS over a network connection.

I guess I would use the LFS LiveCD and do everything on the laptop if I could boot it from CD. Otherwise, take a look at the FAQ, mailing list archives, and LFS hints. I'm sure it's been done before, just not by me.

I would have done that but there are 2 problems:

1. Memory. I was a little worried of running out of it especially during the "make bootstrap" of gcc, but I suppose if I give it a bit of swap it won't be too much of a problem.

2. Time. It'll take AGES! But, patience is a virtue I suppose, and I have a livecd.

The problem with your network suggestion is that the laptop has no nic, and I don't have the cash to spring for either a new laptop or a pcmcia one so I have (had?) to find some other method.

regards
silkenphoenixx