On 15/01/2016 20:07, Timothy Rice wrote:
> Dear all,
>
> I'm having trouble compiling `dummy.c` in Ch 5.7 of both Stable and
> Development LFS. As you know, it is unwise to continue without being able
> to compile this file.
>
> The problem is that when linking, $LFS_TGT-gcc is having trouble finding
> `crti.o` and `crt1.o` in /tools/lib. However, `ls /tools/lib` plainly
> reveals that these files at least exist. I'm fairly sure I've compiled
> binutils and gcc with the correct paths.
[...]
> * test.out: Output of `$LFS_TGT-gcc -v dummy.c -o a.out`.
I am worried about the "collect2" options. It has:
"-dynamic-linker /lib64/ld-linux-x86-64.so.2"
I think the correct command should have:
"-dynamic-linker /tools/lib64/ld-linux-x86-64.so.2"
also, I have that the full path to crt1.o and ctri.o is given, which is not
true for you.
It looks like you screwed up something in the fixup_commands function in gcc:
I am not sure what the "find... -exec bash -c 'relink_file "$0"' {} \;"
does... Have you tested it?
[...]
>
> Also, I'm building LFS in an LVM. The volume group is lfs and there are
> logical volumes for root and tools. The mount hierarchy is:
>
> * /dev/mapper/lfs-root -> /home/lfs/mnt
> * /dev/mapper/lfs-tools -> /home/lfs/mnt/tools
You'll need an initramfs for booting the LFS system.
Pierre
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
http://en.wikipedia.org/wiki/Posting_style
