#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 am seeing the same problem with 10.5.2 on Intel. I never had this problem with the earlier version of poppler (I had 0.6.4_0 installed). This bug report looks similar, although not identical: [http://trac.macosforge.org/projects/macports/ticket/13595 Ticket #13595] It looks to me like Poppler is trying to build qt4viewer, and is looking in a qt working directory that doesn't exist. That raises two question, that perhaps someone else can answer: 1) What is qt4viewer and why is poppler trying to build it? 2) Why is it trying to find something in a (qt) work directory? It seems to be looking for a working directory and ../../qt4/src. {{{ /bin/sh ../../libtool --tag=CXX --mode=link /usr/bin/g++-4.0 -Wall -Wno-write-strings -O2 -L/opt/local/lib -o poppler_qt4viewer abstractinfodock.o documentobserver.o embeddedfiles.o fonts.o info.o main_viewer.o metadata.o navigationtoolbar.o optcontent.o pageview.o permissions.o toc.o viewer.o ../../poppler/libpoppler.la ../../qt4/src /libpoppler-qt4.la -L/opt/local/lib -lfontconfig -lexpat -framework ApplicationServices -framework Carbon -framework AppKit -L/opt/local/lib -L/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_qt4-mac/work /qt-mac-opensource-src-4.3.4/lib -lQtGui -lpng -lQtXml -lQtTest -lQtCore -lz -lm -lz }}} I see that I don't have this working directory, but I do have qt installed. Shouldn't poppler be trying to find anything that it needs in the appropriate installed directory, not in work directory? As I understand it (correct me if I am wrong) working directories are temporary and get deleted after a successful build? So another port should not be counting on them to exist. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14865#comment:1> MacPorts </projects/macports> Ports system for Mac OS