#55675 closed defect (fixed)
qpdf @7.0.0: build fails if qpdf @6.0.0 is active
Reported by: | pmetzger (Perry E. Metzger) | Owned by: | ryandesign (Ryan Carsten Schmidt) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | ||
Port: | qpdf |
Description
qpdf is currently failing to build. main.log for the build attached.
Attachments (1)
Change History (5)
Changed 7 years ago by pmetzger (Perry E. Metzger)
Attachment: | qpdf-main.log added |
---|
comment:1 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)
Summary: | qpdf fails to build → qpdf @7.0.0: build fails if qpdf @6.0.0 is active |
---|
comment:2 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)
Looks like it's already been reported, and the correct fix has already been identified:
comment:3 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)
Owner: | set to ryandesign |
---|---|
Resolution: | → fixed |
Status: | new → closed |
comment:4 Changed 7 years ago by Aaron Madlon-Kay <aaron@…>
Note: See
TracTickets for help on using
tickets.
Your log shows this problem:
I can reproduce this problem, if qpdf @6.0.0 is installed and active when I try to build qpdf @7.0.0.
The build system puts the flags in the wrong order:
-lqpdf -L/opt/local/lib -Llibqpdf/build
. This means that the older libqpdf.dylib already installed in /opt/local/lib will be used in preference to the new one built in libqpdf/build, and the old one doesn't have all the symbols the new version does.This problem should be reported to the developers of qpdf so that they can fix it. Until they do, we should add...
...to the port to at least give the user a more helpful error message.
After you filed this ticket, our buildbot produced a binary archive of this port on High Sierra. So if you clean and try again, you should receive that. You can also work around the problem by using trace mode (
sudo port -t upgrade qpdf
) or by deactivating the old version of qpdf before trying to build the new one.