Opened 3 years ago

Closed 3 years ago

#4355 closed defect (fixed)

"/tools/lib64" in systemd instruction

Reported by: Xi Ruoyao Owned by: DJ Lucas
Priority: normal Milestone: 8.4
Component: Book Version: SVN
Severity: normal Keywords:
Cc: DJ Lucas

Description

r11473 added the command:

for file in /tools/lib64/lib{blkid,mount,uuid}*; do
    ln -sf $file /usr/lib/
done

AFAIK /tools/lib64 only contains the symlink ld-linux-x86-64.so.2 and lib{blkid,mount,uuid} are in /tools/lib.

CC dj since he authored r11473.

Change History (6)

comment:1 by DJ Lucas, 3 years ago

Owner: changed from lfs-book to DJ Lucas
Status: newassigned

No, that's not correct. On current builds, we still have /tools/lib64->lib. OTOH, those instructions predate the change to /lib in the toolchain. While still technically valid, despite the multiple layers of symlinks, unless there is an -rpath somewhere in systemd, e2fsprogs, or procps, I doubt that the library symlinks are even necessary. I had simply put them back because they were present prior to systemd's build order getting mixed up. It hadn't even occurred to me to try without them. We are using the pkgconfig files from /tools/lib/pkgconfig/ so they should include -L/tools/lib. I haven't made it very far in my BLFS build, maybe 50 packages in, and I'm working on a new set of PKGBUILDs. I've only made it through enough to get pacman going and most of the optional deps not covered in LFS. I'll start a fresh build tonight and test without. As an aside, it'll even double as a sanity check for my packaging. :-) I should be able to report back tomorrow evening, possibly morning.

comment:2 by DJ Lucas, 3 years ago

Oh, I forgot I moved them to the systemd package. Yes, in that case, it is probably just an artifact of doing multilib builds and the added "64" is not necessary (but harmless). That said, I did put the links back, but cannot recall if I tested without or simply did as a matter of course. Build running now.

comment:3 by Xi Ruoyao, 3 years ago

Oh it seems I didn't obey LFS standard procedure to create /tools/lib64...

But at least we should remove "64" for 32-bit x86.

comment:4 by DJ Lucas, 3 years ago

Resolution: fixed
Status: assignedclosed

Resolved in r11474.

comment:5 by Xi Ruoyao, 3 years ago

Resolution: fixed
Status: closedreopened

However there is still PKG_CONFIG_PATH=/usr/lib/pkgconfig:/tools/lib64/pkgconfig. In 32-bit x86 we don't have /tools/lib64.

in reply to:  5 comment:6 by Bruce Dubbs, 3 years ago

Resolution: fixed
Status: reopenedclosed

Replying to xry111:

However there is still PKG_CONFIG_PATH=/usr/lib/pkgconfig:/tools/lib64/pkgconfig. In 32-bit x86 we don't have /tools/lib64.

And lib64 -> lib so it should never be needed to reference lib64 directly.

Fixed at revision 11476.

Note: See TracTickets for help on using tickets.