Red Hat Bugzilla – Bug 225477
Missing headers in poppler-devel?
Last modified: 2007-11-30 17:11:54 EST
Description of problem:
Trying to build package of referencer, in it's readme it states the following:
NOTE TO FEDORA USERS: Unfortuately the poppler development packages in the defau
lt yum repositories are incomplete -- to build Referencer it is necessary to sep
arately download poppler source packages, and edit the Referencer Makefile to fi
nd this directory. Note that the binary library itself is fine on Fedora, it's
just the headers that are problematic, so once it is built it can be distributed
Using the poppler package as is, build of referencer fails. Leads me to believe
the referencer developer is right in that something is missing in the
poppler-devel package. Just what this is I haven't been able to determine as of
Referencer build fails
Referencer should build
For the devel package of poppler to have the needed headers is to be
build with --enable-xpdf-headers ( Install unsupported xpdf headers. )
(thanks to Stephanos Manos for this info)
Created attachment 147141 [details]
spec file patch
The patch adds a suuport for the missing(?) xpdf headers producing an
additional package (poppler-addheaders-devel) and adds support for Qt4
producing the additional packages. Also fixes a couple of rpmlint errors
I'd like to know whether the xpdf-headers are not enabled becasue they are too
new (AKA unstsable) or are deprecated so they will be removed in a later version
In the latter scenario, I guess it's a Referencer issue...
Created attachment 147315 [details]
IRC Log from #poppler trying to get details about issue
Did a quick chat in #poppler to try to answer the question above. I think this
makes it very clear that I have no idea what I'm doing here and don't
understand anything about this issue what so ever, but maybe some of this is
still useful. The log is attached.
(In reply to comment #4)
> Created an attachment (id=147315) 
> IRC Log from #poppler trying to get details about issue
Thanks for this.
So, AFAICT, the point is those headers are considered "internals", that is,
nothing outside poppler itself should use them (I assume because the public
poppler interface in intended to achieve same or very similar goals)
It seems to me the ball should be bounced now in the Referencer field ( guess
what, I'm a tennis player... ;) ) in order to understand what the author find
lacking in the poppler public interface.
Though, a statement from the poppler maintainer would still be appreciated...
I noticed the referencer developer of this bug, he agreed that this was a
referencer issue and I was told a rewrite of referencer to fix this will happen
at some time.