ch5 perl linked to /lib

Ken Moffat zarniwhoop73 at
Sat Jan 2 10:29:08 PST 2010

The story so far - a few fubars and syntax errors in my scripts,
which I eventually sorted.  Got into chapter 6 and failed in
the headers check with
/bin/sh: /usr/bin/perl: No such file or directory

Investigation showed that /tools/bin/perl and the symlink were
in place, but /tools/bin/perl was linked to /lib.

At first, I assumed this was another error in my script, and
probably I'd barfed the toolchain adjustments, but everything
else in /tools/bin looks to be correctly linked.

Then, I guessed it was an error in my script, but the patch
is being applied.  Configure correctly determines that it is
on linux, but I'm wondering if something causes it to
ignore the linux hint (which is what we patch).  Unfortunately,
I don't really understand perl's configurey.

ISTR somebody had a miscompiled perl recently, but I
can't find that thread (google is less than useful today)
and I'm out of ideas for diagnosing how to fix this.

Supporting evidence after latest attempt to rebuild perl:
lfs at bluesbreaker ~$ ldd /mnt/lfs/building/perl-5.10.1/perl =>  (0x00007fff27fff000) => /lib/ (0x00007fd0996ed000) => /lib/ (0x00007fd0994e9000) => /lib/ (0x00007fd099267000) => /lib/ (0x00007fd099030000) => /lib/ (0x00007fd098e2d000) => /lib/ (0x00007fd098adb000)
	/lib/ (0x00007fd099905000

lfs at bluesbreaker ~$ grep prefix
if test -L ${prefix}/lib/; then

 I've already tried adding ${prefix} on the line that uses awk to find
the name of libc, as clfs does and as we have done sometimes in
the past, but it didn't alter the result.

Any suggestions, please ?  If it matters, as you can see this is x86_64.

After tragedy, and farce, "OMG poneys!"

More information about the lfs-support mailing list