Ken Moffat wrote: > 2009/8/2 Justin P. Mattock<justinmatt...@gmail.com>: > >> Anyways as for creating ext4 and x86_64 system, I started >> yesterday, and everything seems good. >> /lib64 and /usr/lib64 seem simple enough to have the packages >> go there. but hopefully It's not to tough to make it to the xserver etc.. >> >> As for the build should I have used x86_64-unkown-linux-gnu >> or x86_64-pc-linux-gnu >> >> Justin P. Mattock >> -- >> > Since you are building multilib, you really need to check what is in > cblfs - for my first few multilib builds I had all sorts of weird and > unrepeatable problems, partly because I never saw a need to build > multiple sizes of everything. You youngsters with terrabyte disks > and multiple CPUs probably don't have a problem with that ;-) > > In particular, imake (for xmkmf) needs to be available in both sizes. > > Nowadays, I've given up on multilib because for me it doesn't add > enough benefits to compensate for the extended build. YMMV. > > ĸen > Cool thanks, at the moment I'm getting the hang of /lib64 /usr/lib64 seems a bit challenging to build things like perl-5.10.0.
Thanks to you guys having the cblfs available I was able to do that right.(if not perl would of been creating /usr/lib every time). All of this lib64 stuff has me wondering do I really need this? i.g. if I set the compiler flags to x86_64 will the system be x86_64 without the need for lib64's, or do I need the lib64's to work with things like firefox(prebuilt x86_64)? Seems a bit faster to build regularly without having to worry about the whole "better make sure the lib is set to the right location". (anyways never have done this, so might as well). Justin P. Mattock -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
