Bruce Dubbs wrote: > Justin P. Mattock wrote: > >> I think I screwed up here, when building a pure64 >> I used ubuntu x86_64(which is multilib) >> >> after compiling and building everything >> I chrooted into the directory to build the kernel. >> Im noticing I have some commands that work like mv, ls >> dmesg, and probably some others. but when I >> make menuconfig I receive a command not found. >> >> when I do ls -l /usr/bin/make >> I see: >> -rwxr-xr-x 1 root:root /usr/bin/make >> >> but ldd /usr/bin/make gives: >> >> not a dynamic executable >> (seems othere apps/libs are in the same state) >> >> My guess is during building some programs >> get hard wired(maybe by pkgconfig) >> to reading the link to lib which gets >> symlinked to lib64 >> (this is how ubuntu has it setup). >> >> is there a way to adjust this, or should I start over >> on a regular 686 and build a pure64 from there >> so the linkers get directed to /lib without having >> the multilib obstruction? >> > > I just went through this for the first time on a 64-bit system. I started > with > the Ubuntu 64-bit server and everything built fine. There were some problems > in > BLFS with xorg that we're trying to get straightened out but that was > overcome. > > For LFS, I just followed the book (actually with jhalfs). > > bdu...@core2:~$ ldd /usr/bin/make > linux-vdso.so.1 => (0x00007fff95b3f000) > librt.so.1 => /lib/librt.so.1 (0x00007fe720da0000) > libc.so.6 => /lib/libc.so.6 (0x00007fe720a4d000) > libpthread.so.0 => /lib/libpthread.so.0 (0x00007fe720832000) > /lib64/ld-linux-x86-64.so.2 (0x00007fe720fa8000) > > I don't know what you did, but a pure 64-bit system can be done. > > -- Bruce > Thanks for the response, at the moment I just did the multilib x86_64 without any of the 32bit libs just lib64 kinda like what fedora has done. seems to be o.k.
Anyways: I think my mistake was not doing the adjusting the toolchain section.(causing everything to be linked wrong during compile time). Probably would have been o.k. if I was using a pure64 host system instead of the multilib/symlink system (but could be wrong). when doing a ldd I see the same as you see for the version of make on the new system: /lib64/ld-linux-x86-64.so.2 (0x00007f07fae50000) if this is the hard coded(irregardless of where make is at)in make, then this is why I'm not getting a proper reaction out of make, and most of these programs..(could probably be fixed by creating a symlink to a lib64, but for now I'm trying to avoid that. My best bet is to probably go back and readjust the toolchain then recompile and see if the system works as it should. Justin P. Mattock -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
