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
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
