[lfs-support] 5.7 glibc sanity check question

Alan Corey alan01346 at gmail.com
Wed Jul 11 13:24:37 PDT 2018



On 07/11/2018 12:59 PM, Bruce Dubbs wrote:
> On 07/11/2018 10:28 AM, Alan Corey wrote:
>> OK, it fails.  And when I do
>> readelf -l a.out
>> and look at the output manually the interpreter line is just
>>
>> [Requesting program interpreter: /lib/ld-linux-aarch64.so.1]
>>
>> No /tools in there.  How does it get there?  I configured glib with
>> the little script
>> #!/bin/bash
>> ../configure --prefix=/tools --host=$LFS_TGT  \
>>   --build=$(../scripts/config.guess) --enable-kernel=3.2 \
>>   --with-headers=/tools/include libc_cv_forced_unwind=yes \
>>   libc_cv_c_cleanup=yes
>>
>> Built it all, it failed the sanity test and I was trying to figure out
>> why.  I thought --prefix only changed where something was installed, I
>> didn't know it got embedded.  Maybe this is like argv[0].  This is
>> referencing ld-linux on the host, not the one in /tools.
>
> Are you building as user lfs?  Is $LFS_TGT defined properly?
>
>   -- Bruce
>
Yes and yes.

up64$ whoami
lfs
up64$ env
LC_ALL=POSIX
OLDPWD=/mnt/lfs/sources/glibc-2.27
LFS=/mnt/lfs
NO_AT_BRIDGE=1
PWD=/mnt/lfs/sources/glibc-2.27/build
HOME=/home/lfs
LFS_TGT=aarch64-lfs-linux-gnu
TERM=rxvt-unicode-256color
SHLVL=1
PATH=/tools/bin:/bin:/usr/bin
PS1=\h\$
_=/usr/bin/env

up64$ readelf -l a.out | grep interpreter
       [Requesting program interpreter: /lib/ld-linux-aarch64.so.1]

-- 
---
Sent from my 64-bit Raspberry Pi



More information about the lfs-support mailing list