[MacPorts] #27525: exiv2: unable to infer tagged configuration
MacPorts
noreply at macports.org
Thu Apr 7 21:54:29 PDT 2011
#27525: exiv2: unable to infer tagged configuration
-----------------------------------------+----------------------------------
Reporter: lyle2.0+macports@… | Owner: tcurdt@…
Type: defect | Status: closed
Priority: Normal | Milestone:
Component: ports | Version: 1.9.2
Resolution: fixed | Keywords:
Port: exiv2 |
-----------------------------------------+----------------------------------
Changes (by ryandesign@…):
* status: new => closed
* resolution: => fixed
Comment:
"unable to infer tagged configuration" is a message printed by libtool
when the compiler used to compile libtool differs from the compiler used
to compile the port being compiled now, using libtool. In this case, the
difference is that the compiler used to compile libtool was "ccache
/usr/bin/g++-4.2" (because the user has "configureccache yes" in their
macports.conf, or at least did at the time they built the libtool port),
and the compiler now being used to build exiv2 is "/usr/bin/g++-4.2"
(because the exiv2 portfile has the line "configure.ccache no" thereby
disabling ccache support). This was caused by a combination of r45058
(which made the exiv2 port use the libtool port, because exiv2 0.18's
configure script was generated by autoconf 2.61 and the libtool it
generated was too old to build universal binaries properly) and r73142
(which disabled the use of ccache with exiv2).
I fixed the problem in r77658 by undoing r45058, since exiv2 0.21's
configure script was generated with autoconf 2.67, which is new enough to
support universal builds on its own. Additionally, in r77659 I undid
r73142 because it builds fine for me with ccache.
--
Ticket URL: <https://trac.macports.org/ticket/27525#comment:6>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list