On Sat, Aug 22, 2020 at 3:55 AM Pierre Labastie via blfs-support
<blfs-support@lists.linuxfromscratch.org> wrote:
>
> On Fri, 2020-08-21 at 19:36 -0400, Chris Gorman via blfs-support wrote:
> > On Fri, Aug 21, 2020 at 4:52 PM Pierre Labastie via blfs-support
> > <blfs-support@lists.linuxfromscratch.org> wrote:
> > > On Fri, 2020-08-21 at 16:14 -0400, Chris Gorman via blfs-support
> > > wrote:
> > > > On Fri, Aug 21, 2020 at 3:47 PM Pierre Labastie via blfs-support
> > > > <blfs-support@lists.linuxfromscratch.org> wrote:
> > > > > On Fri, 2020-08-21 at 13:44 -0400, Chris Gorman via blfs-
> > > > > support
> > > > > wrote:
> > > > > > Hello All,
> > > > > >
> > > > > > I am trying to build a sysv BLFS system off of LFS-10.0-rc1
> > > > > > and
> > > > > > am
> > > > > > getting an odd error with header files. The compiler is
> > > > > > failing
> > > > > > complaining about missing headers that are present on the
> > > > > > system. [...]
> > >
> > > Now, to see where the error comes from, you can look at the logs
> > > from
> > > jhalfs (/jhalfs/logs in the booted system). Especially, it'd be
> > > interesting to know what is the output of the sanity check at the
> > > end
> > > of the gcc log.
> > I will look at this log file in detail in a bit. I wanted to get you
> > the output you were interested in, but I'm not too sure what sanity
> > check you're referring to. The last few lines are
> > [...]
> > /usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/../../../../lib/crti.o
> > succeeded
> > /usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/../../../../lib/crtn.o
> > succeeded
> > #include <...> search starts here:
> > /usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/include
> > /usr/local/include
> > /usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/include-fixed
> > /usr/include
>
> Here is the right order, but it is for gcc. Unfortunately, we do not
> test g++ after installing in chapter 8.
>
> > SEARCH_DIR("/usr/x86_64-pc-linux-gnu/lib64")
> > SEARCH_DIR("/usr/local/lib64")
> > SEARCH_DIR("/lib64")
> > SEARCH_DIR("/usr/lib64")
> > SEARCH_DIR("/usr/x86_64-pc-linux-gnu/lib")
> > SEARCH_DIR("/usr/local/lib")
> > SEARCH_DIR("/lib")
> > SEARCH_DIR("/usr/lib");
> > attempt to open /lib/libc.so.6 succeeded
> > found ld-linux-x86-64.so.2 at /lib/ld-linux-x86-64.so.2
> > removed 'dummy.c'
> > removed 'a.out'
> > removed 'dummy.log'
> >
> > I am going to try to ...
> > 1) copy /usr/include to /tmp
> > 2) add /tmp to the directory search path via -idirafter
> > 3) rebuild gcc
> >
This failed for me. It passed the problem I was having with
#include_next not finding the correct file, but it errored out on
something else.
>
> Another possibility could be to have
> "-nostdinc -isystem /usr/include/c++/10.2.0 \
> -isystem /usr/include/c++/10.2.0/x86_64-pc-linux-gnu \
> -isystem /usr/include/c++/10.2.0/backward \
> -isystem /usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/include \
> -isystem /usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/include-fixed \
> -isystem /usr/include"
> in CXXFLAGS, that is all the include dirs in the right order.
This is a good suggestion, but I am concerned about what else is wrong
with the build. (See further down.)
>
> Out of curiosity, is there an order problem with gcc? Could you try
> echo int main'(){}' | gcc -v -xc - |& grep include
>
> I get:
> ignoring nonexistent directory "/usr/lib/gcc/x86_64-pc-linux-
> gnu/10.2.0/../../../../x86_64-pc-linux-gnu/include"
> #include "..." search starts here:
> #include <...> search starts here:
> /usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/include
> /usr/local/include
> /usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/include-fixed
> /usr/include
I get an incorrect ordering.
#include "..." search starts here:
#include <...> search starts here:
/usr/include
/usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/include
/usr/local/include
/usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/include-fixed
>
> Pierre
>
> --
> http://lists.linuxfromscratch.org/listinfo/blfs-support
> FAQ: http://www.linuxfromscratch.org/blfs/faq.html
> Unsubscribe: See the above information page
The more I think about it, the more I think I might just try a rebuild
the system as both gcc and g++ have a broken search path.
Merci pour votre temps Pierre et pour vos suggestions.
Chris
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
