Opened 14 years ago
Closed 14 years ago
#154 closed task (fixed)
/usr/lib64 created by binutils in pure64
Reported by: | ken | Owned by: | ken |
---|---|---|---|
Priority: | blocker | Milestone: | CLFS Standard 1.1.0 |
Component: | BOOK | Version: | CLFS Standard 1.1.0 |
Keywords: | Cc: |
Description
On at least x86_64-64, binutils installs libiberty.a into /usr/lib64.
Now that I've been bitten by this (openjade assumes opensp is in /usr/lib64 if that directory exists, because that is supposedly how it is on ppc64!), I think someone mentioned this on the lists last year.
Change History (4)
comment:1 Changed 14 years ago by
Version: | → CLFS Standard 1.1.0 |
---|
comment:2 Changed 14 years ago by
Owner: | changed from clfs-commits@… to ken |
---|
Hmm, didn't work. In the meantime, I've found /usr/lib64/libstdc++.so* symlinks are needed to allow the glibc-2.7 and ld testsuites to all pass, perhaps there is a connection.
comment:3 Changed 14 years ago by
Looks like I missed the middle '%' when I put that into my script. <sigh/> Seems to be back on the road.
comment:4 Changed 14 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
OK, I can see what is going on. From my build log
At this stage gcc is, of course, in /tools - it hasn't been patched for pure64 so for -print-multi-os-directory (in 64-bit) it returns ../lib64. If I run this against the final gcc it returns ../lib.
The following has had minimal testing (haven't used it in a build, just hacked it and confirmed it will install correctly). The offending line is, fortunately, copied unchanged from libiberty/Makefile.in to libiberty/Makefile so we can just sed it before we cd to binutils-build (the Makefile itself is created when make runs the configure-libiberty target).
Looks as if this will be appropriate to all the pure64 versions of multilib archs (i.e. not alpha).
I'm nowhere close to testing this in a build, so I'll post it here.