On 10/15/19 7:43 PM, Ken Moffat wrote:
On Tue, Oct 15, 2019 at 07:09:30PM -0500, Trent wrote:
I am rebuilding again, and this time on a SSD drive connected to a USB
adapter. Going much faster.
I came up on this.
in Chapter 6.46
http://www.linuxfromscratch.org/lfs/view/stable-systemd/chapter06/kmod.html
Here is what is returned from "make":
make --no-print-directory all-recursive
Making all in .
CCLD libkmod/libkmod.la <http://libkmod.la>
CCLD tools/kmod
/usr/bin/ld: /usr/lib/liblzma.so <http://liblzma.so>: file not recognized:
Is a directory
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:1448: libkmod/libkmod.la <http://libkmod.la>] Error 1
make[2]: *** Waiting for unfinished jobs....
/usr/bin/ld: /usr/lib/liblzma.so <http://liblzma.so>: file not recognized:
Is a directory
Very weird output with those <http://> items in it.
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:1662: tools/kmod] Error 1
make[1]: *** [Makefile:2167: all-recursive] Error 1
make: *** [Makefile:1219: all] Error 2
I see it is related to Xz from the previous section 6.45. I have rerun that
section 3-4 times now. I have also removed /usr/bin/ld: /usr/lib/liblzma.so
<http://liblzma.so> and rebuilt section 6.45 again.
And again - something odd in your mailer ?
But what on earth do you mean when you say you have removed
/usr/bin/ld ?
Not sure of what to make of this, and not seeing anything online about it.
Looking at a completed sysv build:
ken@milliways ~ $file /usr/lib/liblzma.*
/usr/lib/liblzma.la.hidden: libtool library file, ASCII text
/usr/lib/liblzma.so: symbolic link to ../../lib/liblzma.so.5.2.4
So, liblzma should have been moved to /lib and the symlink fixed up.
All at the end of the xz instructions. I suggest you look at your
command history. But after a bad move it's possible that the
readlink might give a weird result. So before rerunning, compare
what that readlink currently returns against my output above, and
perhaps remove the mis-installed xz before repeating xz.
There are several places where we move libraries to /lib and they
are all candidates for weird errors if they go wrong. And you will
probably only see those error messages in an LFS context because
most other distros, at least those using the infernal systemd, do
not separate /lib.
ĸen
Yeah, for some reason the message got malformed, but as I mentioned I
was able to resolve. It is one of those sections in which pasting all
the commands at once gets messed up.
Thanks for responding!
--
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
