#24820 closed defect (invalid)
exiv2: fails to build on 10.6.3: "unable to infer tagged configuration"
Reported by: | dmmonarres@… | Owned by: | tcurdt@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.8.2 |
Keywords: | Cc: | ryandesign (Ryan Carsten Schmidt) | |
Port: | exiv2 |
Description
Exiv2 seems to fail to run "make" at this step:
DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_exiv2/work/exiv2-0.18.2" && /usr/bin/make -j2 all' if test "x1" = "x1"; then cd xmpsdk/src && /usr/bin/make xmpsdk; fi; libtool: compile: unable to infer tagged configuration libtool: compile: specify a tag with `--tag' make[1]: *** [XMPMeta.o] Error 1 make[1]: *** Waiting for unfinished jobs.... libtool: compile: unable to infer tagged configuration libtool: compile: specify a tag with `--tag' make[1]: *** [XMPMeta-GetSet.o] Error 1 make: *** [xmpsdk] Error 2
I have attached the full debug log after cleaning port.
Attachments (2)
Change History (8)
Changed 15 years ago by dmmonarres@…
comment:1 Changed 15 years ago by mf2k (Frank Schima)
Owner: | changed from macports-tickets@… to tcurdt@… |
---|
comment:2 Changed 15 years ago by dmmonarres@…
After removing the post-configure step the port builds.
Changed 15 years ago by dmmonarres@…
Attachment: | exiv2-postconfigure_removed.log added |
---|
Log of build after post-configure removal.
comment:3 follow-up: 4 Changed 15 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | ryandesign@… added |
---|
I can't reproduce this problem; port builds fine for me on Snow Leopard. I also updated the port to 0.19. Do you still see this problem with exiv2 after selfupdating? If so, please try rebuilding your libtool port ("sudo port -n upgrade --force libtool
"), clean exiv2 ("sudo port clean exiv2
") and try again.
comment:4 Changed 15 years ago by dmmonarres@…
Replying to ryandesign@…:
I can't reproduce this problem; port builds fine for me on Snow Leopard. I also updated the port to 0.19. Do you still see this problem with exiv2 after selfupdating? If so, please try rebuilding your libtool port ("
sudo port -n upgrade --force libtool
"), clean exiv2 ("sudo port clean exiv2
") and try again.
After forcing a rebuild of libtool, exiv2 builds and installs correctly. Thanks.
comment:5 Changed 15 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → invalid |
---|---|
Status: | new → closed |
Great, glad you got it working.
comment:6 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
Turns out it wasn't invalid, it just only occurred in a select set of circumstances, explored further and fixed in #27525.
Debug Log