On Sun, 7 Oct 2018 07:28:34 -0500 rhubarbpieguy via blfs-support <[email protected]> wrote:
> Yes, I changed /etc/profile.d/xorg.sh according to Introduction to > Xorg-7. So without that change I see the following: OK, the include search paths look OK to me for both your g++/gcc 8.2.0 and 7.3.0 systems - that is for the example you gave *without* $CPLUS_INCLUDE_PATH and/or $C_INCLUDE_PATH being set. Can you compile Poppler-0.67.0 on your gcc 8.2.0 system *if* $CPLUS_INCLUDE_PATH and/or $C_INCLUDE_PATH are *not* set (don't have any pathappend lines in /etc/profile.d/xorg.sh, unset/clear C_INCLUDE_PATH CPLUS_INCLUDE_PATH, and restart x) and thus your gcc's search paths are as you stated (quoted at the end of this post)? If yes, then I sure don't think you should be setting $CPLUS_INCLUDE_PATH et al. Note that in the Xorg-7 instructions: http://www.linuxfromscratch.org/blfs/view/svn/x/xorg7.html it is stated: "Note: If you've decided to use the standard /usr prefix, you can omit the remainder of this page and continue at util-macros-1.19.2. If you've decided to not use the standard prefix, be sure to add $XORG_PREFIX/bin to your PATH environment variable, and $XORG_PREFIX/lib/pkgconfig and $XORG_PREFIX/share/pkgconfig to your PKG_CONFIG_PATH variable. It is also helpful to specify additional search paths for gcc and an include directory for the aclocal program. Issue the following commands as the root user: " that is ONLY if the standard prefix /usr is *not* being used. But, you had: > echo $CPLUS_INCLUDE_PATH - /usr/include > echo $C_INCLUDE_PATH - /usr/include You should not be setting $CPLUS_INCLUDE_PATH, $C_INCLUDE_PATH is the include paths gcc/g++ is using already "includes the includes of Xorg", which is the case for /usr/include. If you still can't compile poppler-0.67.0 with your gcc 8.2.0 system being sure $CPLUS_INCLUDE_PATH and $C_INCLUDE_PATH are not set, then you will have to begin with poppler-0.62 and advance the version number until the build fails. My guess is the trouble starts with version 0.65. Cheers, Mike For reference, the gcc search paths that look OK to me are as you gave here: > --------------------------------- > `gcc -print-prog-name=cc1plus` -v > > ignoring nonexistent directory > "/usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../x86_64-pc-linux-gnu/include" > #include "..." search starts here: > #include <...> search starts here: > /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../include/c++/8.2.0 > > /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../include/c++/8.2.0/x86_64-pc-linux-gnu > > /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../include/c++/8.2.0/backward > /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/include > /usr/local/include > /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/include-fixed > /usr/include > > ----------------------------- > `gcc -print-prog-name=cc1` -v > > ignoring nonexistent directory > "/usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../x86_64-pc-linux-gnu/include" > #include "..." search starts here: > #include <...> search starts here: > /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/include > /usr/local/include > /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/include-fixed > /usr/include > ------------- So, IMHO, that is what you want to have and what matches most everyone else's systems. -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
