As title says, it builds fine on ppc-macos. Reproducible: Always Steps to Reproduce: 1. 2. 3.
(dependencies are for convenience to myself here) [ebuild N ] x11-libs/motif-config-0.9 0 kB [1] [ebuild N ] x11-libs/openmotif-2.2.3-r7 0 kB [1] [ebuild N ] media-libs/t1lib-5.0.2 -X (-doc) 0 kB [1] [ebuild N ] app-text/xpdf-3.00-r10 +motif -nodrm +truetype 522 kB [1] tested USE flags to work on the PDF version of "Vi Improved by Steve Oualline" When using "motif nodrm" I get no xpdf, configure: configure: WARNING: Couldn't find X / Motif -- you will be able to compile pdftops, pdftotext, pdfinfo, pdffonts, pdftoppm, and pdfimages, but not xpdf while "motif nodrm truetype" or "motif truetype" or "truetype" works fine. Seems like the truetype USE flag does the trick, but it requires to set it, before compilation yields into something one would expect. "-motif" has the same effect of not creating the xpdf executable.
Ah, I should have specified "builds fine using the default USE flags for ppc-macos." (I.e. -motif -nodrm - truetype.)
well, it builds fine in any case, but it fails to find motif (meaning actually building xpdf) in my mentioned situation, indicating somehow something goes wrong there in comparison with x86
I found this one in the configure file for xpdf: if test "x$smr_have_freetype2_library" != xyes; then no_x="yes" fi This would certainly mean that we HAVE to have freetype2 in order to get the xpdf binary. Weird, really.
well, it makes sense for what the configure does, but it doesn't make sense on x86 this doesn't hold. I'll have to look into this... :/
Created attachment 89057 [details] The test pdf.
what does this test.pdf file mean?
The original version builds fine, setting CXXFLAGS/LDFLAGS properly, but the one we have in the tree is a modified one that uses poppler, and poppler requires fontconfig-2 to build; now fontconfig has the ppc-macos keyword, but I've just noticed there is a collision on /etc/fonts/fonts.{conf,dtd}. If I'm not missing something we should package.mask fontconfig and close this as CANTFIX.
I will try fontconfig tonight* to see if it collides for me too. * disclaimer: need not necessarily be today :)
xpdf needs poppler, which wants >=automake-1.9, which is p.masked on OSX. No go.
That one is a useless dep and can go away; the problem with poppler is the one described in comment #8.
get the dep fixed and reopen this bug.
... done; but there is no point in reopening this bug.
This is interesting, I get no collisions for fontconfig. Poppler hasn't got its own bug for this? Interesting. Ohw wait... portage 2.1.1 is broken with regard to collision protect. FUCK!