Got somewhere with this.
I removed the poppler-bindings package, which was the different thing between my installations.
In configure, I get:
checking for POPPLER... yes checking for POPPLER_GLIB... no checking for POPPLER_CAIRO... no
and also:
Enable Poppler-Cairo: yes
Does this mean I have tried to enable it but it doesn't work?
With poppler-bindings installed, it gave me yeses for all three checks, but wouldn't compile.
What am I doing wrong?
Jeff, is this the same for you?
JF
Joshua Facemyer / Impressus Art wrote:
Jon A. Cruz wrote:
On Oct 20, 2007, at 6:49 PM, Joshua Facemyer / Impressus Art wrote:
Okay, will the same pdf functionality be present then? (Also, is this a workaround to get the thing compiling at a loss of functionality, or is it something that should / will be addressed in a future update to make it compile in an environment that it should without difficulty?)
Someone familiar with the specifics would have to look into it, but I think it's a work-around in losing a bit of functionality...
But from what I recall, it's probably due to us using internals of poppler that are not part of the public API. Get and build poppler yourself and you might have the needed .h, but use standard packing and you probably won't.
Part of me only seeing this recently was that only recently had I gotten a new enough poppler in macports.
I use Gentoo, so my poppler should be "my own" build. Same with Jeff. (Had you figured this out yet, Jeff?)
Is it maybe that some switch needs to be passed to poppler when building it?
JF
Update: on my two gentoo boxes, one won't build the latest SVN with poppler 0.6 and one will. They both have Cairo 1.4.10, and both packages are built with the same use flags.
JF