On 07/10/2018 01:33 PM, Ken Moffat wrote:
On Tue, Jul 10, 2018 at 10:53:37AM -0400, Alan Corey wrote:
Like
aarch64-lfs-linux-gnu-as.1
or did I screw up again?
For (pseudo) cross-compiling (i.e. pass 1), that is ok.
In /mnt/lfs/tools/bin I have a set of executables with names like
aarch64-lfs-linux-gnu-as and in
/mnt/lfs/tools/aarch64-lfs-linux-gnu/bin there's another set with
normal names. Neither are symlinks to the other.
Use ls -i : they should be hardlinks to the same inode.
Yes, they are, I'm not used to seeing hard links
[...]
I just finished /lfs/chapter05/binutils-pass1.html I didn't try very
hard to figure out what
case $(uname -m) in
x86_64) mkdir -v /tools/lib && ln -sv lib /tools/lib64 ;;
esac
Is for because I'm not an x86_64 user. Should I have done something
similar for aarch64? It links something, that's all I know.
It all depends on the expected linker and library directories. For
x86_64 the initial expectation was multilib, so 64-bit libraries and
their linker are in {$PREFIX,}/lib64 - on LFS we do not support
multilib, everything can happily live in /lib with the symlink and
other step(s) shown for x86_64.
But my google-fu doesn't let me find out what the expected
directory/linker is (searching for linker got me to ld scripts and
information from gcc on the two -mabi variants for 32bit, 64bit,
searching for loader got me information on boot images).
So, I think it is VERY likely that you need the lib64 symlinks. But
if you get to glibc in chapter 6 I have no idea what the equivalent
of ld-linux should be.
Ah! Searching for aarch64 ld-linux got hits for
ld-linux-aarch64.so.1 so that is probably the correct name,
Confirmatory details at https://patchwork.openembedded.org/patch/80431/
On a page at linaro I found:
TRIPLET=arm-unknown-linux-gnueabi # or aarch64-unknown-linux-gnu
LINUX_ARCH=arm # use arm64 if building for an aarch64 target
I see both the arm64 and aarch64 in general. But the prefix seems to be used
mostly on the binutils stuff. On the host Pi I see:
lrwxrwxrwx 1 root root 5 Apr 4 06:16 aarch64-linux-gnu-cpp -> cpp-7
-rwxr-xr-x 1 root root 912128 Jun 15 08:29 aarch64-linux-gnu-cpp-6
-rwxr-xr-x 1 root root 981896 Jun 26 03:52 aarch64-linux-gnu-cpp-7
-rwxr-xr-x 1 root root 1035192 Jun 26 04:45 aarch64-linux-gnu-cpp-8
-rwxr-xr-x 1 root root 3384304 Jun 22 02:11 aarch64-linux-gnu-dwp
-rwxr-xr-x 1 root root 31424 Jun 22 02:11 aarch64-linux-gnu-elfedit
lrwxrwxrwx 1 root root 5 Apr 4 06:16 aarch64-linux-gnu-g++ -> g++-7
-rwxr-xr-x 1 root root 981896 Jun 26 03:52 aarch64-linux-gnu-g++-7
lrwxrwxrwx 1 root root 5 Apr 4 06:16 aarch64-linux-gnu-gcc -> gcc-7
-rwxr-xr-x 1 root root 912128 Jun 15 08:29 aarch64-linux-gnu-gcc-6
-rwxr-xr-x 1 root root 981896 Jun 26 03:52 aarch64-linux-gnu-gcc-7
-rwxr-xr-x 1 root root 1035192 Jun 26 04:45 aarch64-linux-gnu-gcc-8
lrwxrwxrwx 1 root root 8 Apr 4 06:16 aarch64-linux-gnu-gcc-ar ->
gcc-ar-7
-rwxr-xr-x 1 root root 23072 Jun 15 08:29 aarch64-linux-gnu-gcc-ar-6
-rwxr-xr-x 1 root root 27104 Jun 26 03:52 aarch64-linux-gnu-gcc-ar-7
-rwxr-xr-x 1 root root 27104 Jun 26 04:45 aarch64-linux-gnu-gcc-ar-8
lrwxrwxrwx 1 root root 8 Apr 4 06:16 aarch64-linux-gnu-gcc-nm ->
gcc-nm-7
-rwxr-xr-x 1 root root 23072 Jun 15 08:29 aarch64-linux-gnu-gcc-nm-6
-rwxr-xr-x 1 root root 27104 Jun 26 03:52 aarch64-linux-gnu-gcc-nm-7
-rwxr-xr-x 1 root root 27104 Jun 26 04:45 aarch64-linux-gnu-gcc-nm-8
The aarch64-linux-gnu-gcc is a symlink pointing to aarch64-linux-gnu-gcc-7
right now.
Leaving the directory as-is for now and moving on
ĸen
--
---
Sent from my 64-bit Raspberry Pi
--
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
