> >> Now that you mention it Pierre, I think the following would be better
> >> because it is far easier to read and understand.
> >>
> >>
> >> sed -e 's@/lib../ld@/tools&@g'
> >>
> >> where the '.' matches any character.
> >
> > Not completely sure, but I think we need to be able to match /lib/ld
Am 22.06.2016 um 18:35 schrieb Pierre Labastie:
Did you type the CC=... CXX=... etc lines? They are needed (with
backslash as continuation character) to get the behavior I
described... Maybe LFS_TGT is not set? Or $LFS_TGT-gcc is not found in
the PATH? To be clear, you can unpack gcc outside
Pierre Labastie wrote:
On 21/06/2016 21:12, Bruce Dubbs wrote:
Pierre Labastie wrote:
The place where /tools/ is added before /lib is in 5.10, GCC Pass 2. it is
the long sequence of instructions starting with "for file in". Have you
pasted those instructions from the book, or did you recopy
On 22/06/2016 17:20, Edgar Alwers wrote:
Am 22.06.2016 um 15:08 schrieb Pierre Labastie:
You may try (outside chroot):
echo 'int main(){}' > dummy.c
/tools/bin/i686-lfs-linux-gnu-gcc dummy.c
readelf -l a.out | grep ': /tools'
[Requesting program interpreter: /tools/lib/ld-linux.so.2]
On 21/06/2016 21:12, Bruce Dubbs wrote:
Pierre Labastie wrote:
The place where /tools/ is added before /lib is in 5.10, GCC Pass 2.
it is
the long sequence of instructions starting with "for file in". Have you
pasted those instructions from the book, or did you recopy them by hand?
Make sure
