>
> If I issue the following command (similar to the sanity check in chapter
> 6 of LFS):
>
> echo 'int main(){}' | gcc -v -xc - |& grep include
>
> I get:
> ignoring nonexistent directory
>
> "/usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/../../../../x86_64-pc-linux-gnu/include"
> #include "..." search starts here:
> #include <...> search starts here:
> /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
> /usr/include
>
> which means /usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/include is searched
> first.
>
Okay so the output I am getting mentions a duplicate directory and does
indeed search '/usr/include' first but does at least continue to search the
other directories:
$ 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
So apparently, my compiler is searching the correct places but in the wrong
order. Does this warrant a full rebuild of GCC though? I feel like there
should be a way to correct the order without having to start over again.
I also wonder how it managed to get in this specific order in the first
place considering I followed the book's instructions exactly. The only
thing I did that varied from the book was including '-j2' in the make
process to speed up the build slightly.
If I do have to rebuild GCC, how can I make sure that the order is made
correct this time around?
Thanks for helping me locate the issue at hand here. Hopefully this can get
resolved without too much fuss. I have yet to get a full LFS/BLFS build
finished and working properly, and this is my fourth attempt at it haha.
-- Jared
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page