On Wed, 3 Oct 2018 23:50:15 -0600 Alex B <[email protected]> wrote:
> "export CPLUS_INCLUDE_PATH=/usr/include/c++/8.2.0:/usr/include" did the > trick. > .. > I still don't see why there is a need to set that variable, when it is > not being set by jhalfs and can't find any reference to it under /etc > either. The packages should have compiled successfully without the need > for it. Alex, I agree with you and Paul here: On Thu, 04 Oct 2018 16:01:16 -0700 Paul Rogers via blfs-support <[email protected]> wrote: > It really does suggest there are further problems in your system. I found something else that we can compare notes to. Do a: unset CPLUS_INCLUDE_PATH `gcc -print-prog-name=cc1plus` -v to show the g++ include paths irrespective of what CPLUS_INCLUDE_PATH was set to. Be sure to use the correct type of quotes in the above command. Both of the quotes are ` which is on the same key as the tilde ~ on most keyboards. And it seems one has to press ctl-C to get back to the command prompt after "End of search list." is displayed. I found this tip at: https://askubuntu.com/questions/573417/where-are-header-files-for-gcc-located So, this information from your gcc setup can then be compared to that of others with recent BLFS systems and then we can see if something is indeed different. Cheers, Mike -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
