On 11/4/19 9:23 PM, Jared Stevens via blfs-support wrote:
Good evening everyone,
I thought it'd be best to make a reply to this existing thread instead
of making a new one since the current issue is identical to the one I
originally had at the beginning of this thread.
After following the advice of Pierre and attempting to rebuild the GCC
compiler to fix the Qemu compile error was still unsuccessful, I
attempted a brand new LFS build.
This build used a completely remade 'tools' directory for LFS on an
entirely different host PC, and as of now has NOT had the GCC compiler
reinstalled in BLFS to include the additional features. It is the
standard C/C++ GCC compiler built in LFS following the steps exactly.
Despite these measures, however, attempts to install Qemu-4.1.0 still
fail with the exact same error at the exact same location in the build:
In file included from /usr/include/features.h:474,
from /usr/include/bits/libc-header-start.h:33,
from /usr/include/stdint.h:26,
from
/usr/src/blfs/vm/qemu-4.1.0/pc-bios/optionrom/linuxboot_dma.c:65:
/usr/include/gnu/stubs.h:7:11: *fatal error:* gnu/stubs-32.h: No such
file or directory
7 | # include*<gnu/stubs-32.h>*
| *^~~~~~~~~~~~~~~~*
compilation terminated.
make[1]: *** [/usr/src/blfs/vm/qemu-4.1.0/rules.mak:69:
linuxboot_dma.o] Error 1
make: *** [Makefile:519: pc-bios/optionrom/all] Error 2
Furthermore, the output of the sanity check similar to chapter 6 of
LFS continues to include '/usr/include' first despite being a
completely unrelated and fresh LFS build:
$ echo 'int main(){}' | gcc -v -xc -|& grep include
ignoring nonexistent directory
"/usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/../../../../x86_64-pc-linux-gnu/include"
ignoring duplicate directory "/usr/include"
#include "..." search starts here:
#include <...> search starts here:
* /usr/include*
* /usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/include
/usr/local/include
/usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/include-fixed*
I am at a complete loss here. I know my PC is capable of
virtualization, and I know that a build mistake on my part in BLFS did
not occur because I haven't touched the compiler since LFS.
I can also confirm that the GCC compiler passed each and every sanity
check introduced throughout the book as well.
Is there any way to force the build of Qemu to search '
/usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/include' before '/usr/include'
or something?
Thanks,
Jared
Since nobody else has responded yet, I thought I would take a stab at
helping you.
To me, I don't see it as a virtualization problem,.
From what you posted:
usr/include/gnu/stubs.h:7:11: *fatal error:* gnu/stubs-32.h: No such
file or directory
7 | # include*<gnu/stubs-32.h>*
| *^~~~~~~~~~~~~~~~*
*
*
*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?
*
*If you do not figure it, maybe someone here with more knowledge can
point it out for you.
*
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
