[poppler] configure disable-X ignored

Albert Astals Cid aacid at kde.org
Wed Mar 9 11:04:18 PST 2011


A Dimecres, 9 de març de 2011, Tim Brody va escriure:
> $ git clone git://git.freedesktop.org/git/poppler/poppler
> $ cd poppler
> $ ./autogen.sh --prefix=/usr/local/poppler --disable-cairo-output
> --disable-poppler-glib --disable-gtk-test --disable-poppler-qt4
> --disable-splash-output --disable-poppler-cpp
> $ make
> 
> ...
> Building poppler with support for:
>   font configuration: fontconfig
>   splash output:      no
>   cairo output:       no
>   abiword output:     no
>   qt4 wrapper:        no
>   glib wrapper:       no
>     introspection:    no
>   cpp wrapper:        no
>   use gtk-doc:        no
>   use libjpeg:        yes
>   use libpng:         yes
>   use libtiff:        no
>   use zlib:           no
>   use libcurl:        no
>   use libopenjpeg:    yes
>   use cms:            yes
>   command line utils: yes
> 
> $ make 2>&1
> 
> ...
> gtk-test.cc:14:21: error: gdk/gdk.h: No such file or directory
> In file included from gtk-test.cc:19:
> ../glib/poppler.h:22:25: error: glib-object.h: No such file or directory
> In file included from ../glib/poppler.h:201,
>                  from gtk-test.cc:19:
> 
> (Followed by more errors related to cairo)
> 
> I'd like to "backport" current poppler onto servers and even with distros
> <year old (Fedora Core 13) it's a nightmare. Is it unreasonable to ask
> poppler to maintain compatibility with stable releases of dependent
> libraries e.g. cairo 1.0, glib 2.0 etc? It surely can't help testing to
> restrict your community to those people on the very latest library levels?

Well, you know, the "community that contributes" uses very latest library 
versions, so it is up to you guys not using them to provide patches.

Albert


More information about the poppler mailing list