On Wed, 10 Oct 2018 16:47:49 -0500 rhubarbpieguy via blfs-support <[email protected]> wrote:
> I applied the patch to poppler-0.63.0 and poppler-0.67.0. > Both compiled successfully. The changeset between 0.63 and 0.64 is tens of thousands of lines long. Tis much like finding a needle in haystack on the first try. Yay! However, we still don't know exactly what is going wrong and why others haven't encountered this problem. However, given that the offending change was made/suggested by a clang script, I think it is likely that it is a bug (in poppler 0.63-on). First of all, GTK3 must be installed for gtk-test.cc to be built. So, the problem won't occur on systems without GTK3. Now, on your gcc 8.2.0 system (the newer one where the build fails), do a fresh unpack of poppler 0.63. Do not apply any patches to it. Verify that your gcc/g++ path variables are indeed not set to anything: echo $CPLUS_INCLUDE_PATH echo $C_INCLUDE_PATH They are both unset/blank, right? Now, attempt to build poppler 0.63, but invoke the verbose option with make to see the actual gcc/g++ command that fails: mkdir build cd build cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/usr -DTESTDATADIR=$PWD/testfiles -DENABLE_XPDF_HEADERS=ON .. make VERBOSE=1 Could you paste the gcc/g++ commands just before and after the build failure occurred so we can see what command line options gcc/g++ was invoked with when attempting to build gtk-test.cc? Cheers, Mike -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
