On 08/10/2019 06:12 PM, Douglas R. Reno via blfs-dev wrote:
On 8/10/19 2:55 PM, Jean-Marc Pigeon via blfs-dev wrote:Hello, Help welcome. Unable to build poppler-0.79, problem stand within openjpeg-2.3.1 Able to build poppler-0.79, with openjpeg-2.3.0. poppler-0.79.0/poppler/JPEG2000Stream.cc:20:10: fatal error: openjpeg.h: No such file or directory 20 | #include <openjpeg.h> compilation terminated. iIn both build openjpeg.h is indeed present within /usr/include/openjpeg-2.3 Problem.... I have the same files list within 2.3.0 and 2.3.1, even more problematic beside the version number both pkgconfig/libopenjp2.pc are identical.... Here is the poppler build context. Building Poppler with support for: font configuration: fontconfig splash output: yes cairo output: yes qt5 wrapper: yes glib wrapper: yes introspection: no gtk-doc: no cpp wrapper: yes use libjpeg: yes use libpng: yes use libtiff: yes use zlib compress: yes use zlib uncompress: no use nss3: yes use curl: yes use libopenjpeg2: yes use lcms2: yes command line utils: yes fuzz target: no Thanks for help...Hi Jean, Are you sure your OpenJPEG install completed successfully? I just built poppler-0.79.0 on my i686 system: renodr [ /sources ]$ search-package openjpeg Sat 10 Aug 2019 01:39:08 PM CDT openjpeg-2.3.1 renodr [ /sources ]$ search-package poppler Sat 10 Aug 2019 01:47:04 PM CDT poppler-0.79.0 Here's the poppler build context: Building Poppler with support for: font configuration: fontconfig splash output: yes cairo output: yes qt5 wrapper: no glib wrapper: yes introspection: yes gtk-doc: no cpp wrapper: yes use libjpeg: yes use libpng: yes use libtiff: yes use zlib compress: yes use zlib uncompress: no use nss3: yes use curl: yes use libopenjpeg2: yes use lcms2: yes command line utils: yes fuzz target: no test data dir: /sources/poppler-0.79.0/poppler-0.79.0/build/testfiles -- Configuring done -- Generating done Everything seems to be working, and the program I needed it for runs well.
Many Thanks for your Help.
Yes, I am positive about it.
Here are my last findings....
1) openjpeg (2.3.1) program install "include files" within
/usr/include/openjpeg-2.3
a) if I symlink openjpeg-2.3 directory contents to /usr/include
then poppler-0.79.0 compile ok.
b) if I rename pkgconfig/libopenjp2.pc to x_libopenjp2.pc
compilation is still successful (so pkgconfig is not used).
2) If I remove 2.3.1 and put back openjpeg-2.3.0
program install "include files" within
/usr/include/openjpeg-2.3 (as expected/usual)
a) poppler-0.79.0 is successful again.
b) If I move /usr/include/openjpeg-2.3 to
/usr/include/x_openjpeg-2.3,
poppler compilation is failing (good!).
Conclusions:
1) pkgconfig is not used by poppler (to find the CFLAGS).
2) In some way, openjpeg say/announce where are its include
and this is set to be wrong within 2.3.1
Making sense? do you agree?
Problem, I am not able to prove/find the 2.3.1 defect...
my conclusion seems to me illogical.
I must overlook something.
--
seen "Linux from scratch" and looking for ISO files
www.osukiss.org
smime.p7s
Description: S/MIME Cryptographic Signature
-- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
