"Without any CPLUS_INCLUDE_PATH etc. variables set, can you build
poppler 0.62 on the gcc 8.2.0 system?"
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
I misread your above question as I saw 8.2 and thought you meant BLFS
8.2. I reported running Poppler 0.62 on my BLFS 8.3/gcc 8.2.0 system
previously. I'm using EpdfView with Poppler 0.62 currently.
However, (what the heck), I thought I'd attempt compiling Poppler 0.67
(BLFS 8.3 version) on my BLFS 8.2 build. To my surprise, It compiled
successfully. So, I can compile Poppler 0.67 on BLFS 8.2/gcc 7.3 but
not on BLFS 8.3/gcc 8.2. I've apparently done something wrong with BLFS
8.3 but am a loss as why it affects only Poppler.
I also ran your commands on my BLFS 8.2/gcc 7.3 build.
---------------------------------
`gcc -print-prog-name=cc1plus` -v
ignoring nonexistent directory
"/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../include/c++/7.3.0
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../include/c++/7.3.0/x86_64-pc-linux-gnu
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../include/c++/7.3.0/backward
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/include
/usr/local/include
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/include-fixed
/usr/include
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/7.3.0/../../../../x86_64-pc-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/include
/usr/local/include
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/include-fixed
/usr/include
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
----------------------------------------------------------------------------------------------------------
Ken raised the cmake question earlier. I used the cmake commands from
the documentation and OpenJPEG (which compiled successfully) uses
cmake. I know little of cmake but want to make certain there's not
something in his post I didn't understand.
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
