[lfs-dev] Multilib patch
kevin.m.buckley at gmail.com
Sat Jan 5 22:16:53 PST 2019
A web search for my GCC-internal zlib config error
configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES
turned up, amongst others, these two, the first of which results from
an LFS build !
The second of those suggests that it may be the lack of a "multilib capable"
toolchain ON THE HOST that is the issue for me?
With that in mind, I'm coming back to my original remarks about rebuidling
the way I last "upgraded" an x86_64 LFS to have multilib capibilty was by
following one of DJ's old books, wherein things were effectively done in
x86_64 host -> x86_64 LFS-tools
x86_64 LFS-tools -> x86_64 LFS
x86_64 LFS -> Multilib LFS-tools components
Multilib LFS-tools -> Multilib LFS components
Indeed, after the Binutills pass1 now, the only file in /tools/bin are
suggesting that any non-x86_64 stuff has to come from the host ?
Then again, you've stated that your sucessful build came from an
FYI, my host (Ubuntu 1404 - yes. old, yes) has
Binutils: (GNU Binutils for Ubuntu) 2.24
gcc (Ubuntu 4.8.4-2ubuntu1~14.04.4) 4.8.4
(Ubuntu EGLIBC 2.19-0ubuntu6.14) 2.19
so is a little diferent to what the Multilib book suggests things
have been tested against, bis:
Binutils-2.25 (Versions greater than 2.31.1 are not recommended as
they have not been tested)
GCC-4.9 including the C++ compiler, g++ (Versions greater than 8.2.0
are not recommended as they have not been tested)
Glibc-2.11 (Versions greater than 2.28 are not recommended as they
have not been tested)
I think I may find the best way forwards to be one in which I build an
non-Multilib LFS 8-3
and then use that to boostrap the Multilib one, as that would give me
a "host" with
Just out of interest then, what are the Binutils, GCC, Glibc versions on
the "non-multilib" host that your Multilib buils suceeds ?
More information about the lfs-dev