lux-integ wrote: > Greetings > > I have been folowing clfs and cblfs recipes for the last 18 months. I use > the > AMD64 processor and I build clfs > as pue 64 bit. Nowhere in the clfs recipe(s) is the creation of a /lib64 > or /usr/lib64 or ~/whatever/lib64 I followed the non-multilib build recipe > of cblfs. I compile with just ./configure/make/make install/ and I > link /usr/lib64 to /usr/lib beleiving I have generated 64-bit > executables and libraries. > > This was until last night when I visited the cblfs site regarding > insalling > the nvidia binary-only linux driver > (http://cblfs.cross-lfs.org/index.php/NVIDIA) for nvidia GPU's and noticed > they treat non-multilib as for x86 and have a separate recipe for pure > 64-bit amd64. (I am about to start on another blfs/cblfs 64-bit build an I > would like to know if their non-multilib recipes refer to true 64-bit > builds for amd64-64-bit clfs setups or does one need ALWAYS to pass > arguments such as USE_ARCH=64 CC="gcc $BUILD64" to configure scripts OR > is this dependent on the program to be compiled.
You are asking on the wrong list. CLFS has their own. http://trac.cross-lfs.org/wiki/lists That said, LFS-dev builds a pretty solid 'pure-64' LFS. The only reason you need multilib/32-bit support is for proprietary code that is not available in 64-bit versions -- an increasingly rare situation. http://www.linuxfromscratch.org/lfs/view/development/prologue/architecture.html -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
