On Tue, Nov 5, 2019 at 10:34 PM Jared Stevens via blfs-support <
[email protected]> wrote:
> *It is looking for the stubs-32.h header file. That is a 32 bit header
>> file from libc. Libc was installed during LFS.*
>>
>>
>> *Why it is looking for that, I do not know as I don't know anything about
>> Quem. So maybe it is one of two things, required, by Quem, or some of your
>> environment was setup as 32 bit?*
>>
> From what I can recall, I can't see how any part of environment was setup
> as 32-bit since both builds were done on two separate 64-bit host PCs and
> were done verbatim from the LFS 9.0-systemd book.
>
> I have done tons of research online about this error, and from what I can
> gather, everyone who has ever experienced this issue had it resolved by
> installing the glibc-devel.i386 or g++-multilib packages from their
> distro's package manager.
>
> Obviously, that solution won't work with LFS, and I am certainly not
> willing to destroy my build by attempting to anyways. Futhermore, I feel
> like the issue is not with my build but rather with Qemu looking for header
> files that simply aren't there. I have tried setting the configure flag
> '--disable-multilib' in Qemu as suggested by someone in a forum during my
> research, but the package doesn't recognize the flag.
>
> The only way I can see this being a build issue in my opinion is if the
> instructions in the LFS 9.0 book left out configuration for the glibc-i386
> header files under an x86_64 build environment. I would be willing to bet
> that if the build environment were built under i386, there wouldn't be any
> issues.
>
> Like I said before, this is an error message that has occurred to me now
> at the exact same location (and nowhere else) on two separate builds of LFS
> 9.0 using two different host PCs and different built 'tools' directories
> and with no obvious errors with GCC or any other LFS package as all sanity
> checks passed as per the book's instructions.
>
> I had hoped to use Qemu on my LFS build, but I assume I will have to make
> do without it unless someone is able to help me figure out where the
> problem lies here. If nothing else, I'll make sure to try again when the
> next stable LFS version is released just to see if the issue has been
> resolved.
>
> -- Jared
>
--
Have you looked at Emmett's multilib LFS (
https://www.linuxquestions.org/questions/linux-from-scratch-13/%5Bguide%5D-howto-multilib-lfs-4175649832)?
It can be used retrospectively to provide a 32-bit glibc on a 64-bit
system. See especially post number 5 in that thread.
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
