[prev in list] [next in list] [prev in thread] [next in thread]
List: macports-tickets
Subject: Re: [MacPorts] #14865: poppler 0.8.0 fails to build under tiger
From: "MacPorts" <trac () macosforge ! org>
Date: 2008-03-31 18:22:48
Message-ID: 059.88a64a480b0c1a62246c64d3523f72b8 () macosforge ! org
[Download RAW message or body]
#14865: poppler 0.8.0 fails to build under tiger 10.4.11 on Intel
-----------------------------------+----------------------------------------
Reporter: jwhowse4@comcast.net | Owner: macports-tickets@lists.macosforge.org
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 1.6.0
Resolution: | Keywords:
-----------------------------------+----------------------------------------
Comment (by dersh@alum.mit.edu):
I found a work around, that is also a clue to the problem. The following
worked for me:
{{{
sudo port deactivate qt4-mac
sudo port clean poppler
sudo port install poppler
sudo port activate qt4-mac
}}}
So, it seems that if qt4-mac is installed that the poppler install tries
to build some additional applications (qt4viewer?) but looks in the wrong
place. On the other hand, if qt4-mac is not installed, then poppler seems
to ignore this, so it builds fine.
I see that the poppler port file does refer to
${worksrcpath}/qt4/Makefile.in
I would think that the correct solution is to have the poppler port
somehow point the poppler configure to correctly find qt4-mac stuff. But
I am really not sure how to do that. Suggestions?
--
Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14865#comment:2>
MacPorts </projects/macports>
Ports system for Mac OS
_______________________________________________
macports-tickets mailing list
macports-tickets@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-tickets
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic