Hello,
don't attempt to use a 32-bit config.
Where can I find a 64-bit config that I can use as a
starting point?
make CROSS_COMPILING=x86_64-pc-linux-gnu-
ARCH=x86_64 menuconfig
Note the '-' at the end of the CROSS_COMPILING,
this should match the
prefix given to your cross-compile
Linux From Scratch - Version
7.0-cross-lfs-20050902-x86
Host Distribution - Slackware 10.1 with kernel-2.6.13
Section - 5.8. Glibc-2.3.5
Executing make for Glibc-2.3.5 fails with the
following error:
nptl/sysdeps/x86_64/tls.h:23:47: error: asm/prctl.h:
No such file or directory
make[1]: ***
On Wed, 7 Sep 2005, Basel Al-Mustafa wrote:
--- Ken Moffat [EMAIL PROTECTED] wrote:
You are trying to build a 64-bit system, aren't you
?
Yes that is true but I think I made a mistake. I
followed the instructions under Version
7.0-cross-lfs-20050902-x86_64-Multilib when I should
have
You *were* correct in what you did - pick the
system you want to build
*for* (64/32 in your case).
Ken
Do I need to rebuild packages in the previous chapters
after cross compiling the kernel?
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ:
--- Ken Moffat [EMAIL PROTECTED] wrote:
No. You should have built cross-tools which run
on your x86 host and
compile for x86_64, then you used those to
cross-compile tools which
will run as x86_64. When you have used the
cross-tools to build a
64-bit kernel, and booted that (with
Hello,
I followed the instructions exactly for ther gcc 4 branch of LinuxFromScratch.
I am reaching the chapter 6, to 6.14 , and do the following:
Prepare GCC for compilation:
./gcc-4.0.1/configure --prefix=/usr \
--libexecdir=/usr/lib --enable-shared \
--enable-threads=posix
I get this error when I run find:
find Hard link count is wrong for /proc
filesystem driver may have bug
Anyone know anything about that?
Thanks
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information
baho-utot wrote:
I get this error when I run find:
find Hard link count is wrong for /proc
filesystem driver may have bug
Anyone know anything about that?
Thanks
Unless you're actually looking for something in /proc, you can use
'-xdev' and find won't look in the virtual file systems.