Summary: | app-text-xpdf-3.02 fails to build against !x11-libs/openmotif-2.2 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jeroen Roovers (RETIRED) <jer> |
Component: | Current packages | Assignee: | Printing Team <printing> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
app-text:xpdf-3.02:20071118-163030.log USE=-nodrm
app-text:xpdf-3.02:20071118-163849.log USE=nodrm |
Description
Jeroen Roovers (RETIRED)
2007-11-18 16:47:46 UTC
Created attachment 136300 [details]
app-text:xpdf-3.02:20071118-163030.log USE=-nodrm
Created attachment 136301 [details]
app-text:xpdf-3.02:20071118-163849.log USE=nodrm
elmer ~ # allpackagesemerge |grep poppler =app-text/poppler-0.6.1-r1 =app-text/poppler-bindings-0.6.1 =app-text/poppler-data-0.1 app-text/xpdf-3.01-r8 has the same issue. After using motif-config to switch back to stable x11-libs/openmotif-2.2, the problem magically went away. app-text/xpdf generally doesn't compile against x11-libs/openmotif-2.3 or "lesstif-2.1" (according to motif-config, actually that's x11-libs/lesstif-0.94.4). Removing blocker as xpdf stabilisation doesn't depend on this bug being resolved (as such). So its enough to just depend on that openmotif version? And you are sure it doesnt work with lesstif at all? (In reply to comment #7) > So its enough to just depend on that openmotif version? And you are sure it > doesnt work with lesstif at all? I don't know. Why don't we start at the beginning: you could try reproducing it... lesstif sucks, not an xpdf bug. If you want to help to sanitize motif in gentoo, move to Bug 117057 please. *** This bug has been marked as a duplicate of bug 193505 *** |