Opened 9 years ago

Closed 9 years ago

#46298 closed defect (worksforme)

Build failed for poppler

Reported by: ac.hixson@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: dbevans (David B. Evans), dliessi (Davide Liessi)
Port: poppler

Description (last modified by ryandesign (Ryan Carsten Schmidt))

Installing frescobaldi. Required :

Error: The following dependencies were not installed: py27-python-poppler-qt4 poppler-qt4-mac poppler

Appeared to be building poppler

LOG

:info:build sed: /opt/local/lib/libiconv.la: No such file or directory
:info:build libtool: link: `/opt/local/lib/libiconv.la' is not a valid libtool archive

I see this has been reported several times in different contexts. Don't know what process was supposed to create the file.

LIke a reply as I'm completely stuck here.

Change History (5)

comment:1 Changed 9 years ago by dbevans (David B. Evans)

has duplicate #46299

comment:2 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Description: modified (diff)

Please attach the main.log file.

.la files get deleted by MacPorts on Mavericks and later. But something on your system is still expecting them to exist. This can happen if you upgrade from Mountain Lion or earlier to Mavericks or later without completing the required migration process.

comment:3 Changed 9 years ago by dbevans (David B. Evans)

Cc: devans@… davide.liessi@… added
Port: poppler added; frescobaldi removed
Version: 2.3.3

CCing maintainers of poppler and frescobaldi.

FWIW, I just confirmed that I can do a fresh build of frescobaldi and its dependents (including poppler) without any problems.

comment:4 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

This isn't something the maintainers of the ports can do anything about. It's an error in the user's installation which the user needs to correct by reinstalling all ports as per the migration instructions.

comment:5 Changed 9 years ago by dbevans (David B. Evans)

Resolution: worksforme
Status: newclosed

Agreed. Since this really isn't a port bug, the reporter of this ticket should proceed as suggested. If there are any further questions about how to do this, the macports-users list would be a good place to ask for help.

Note: See TracTickets for help on using tickets.