[MacPorts] #56637: cmake and gobject_introspection portgroups together cause invalid CC archflags
MacPorts
noreply at macports.org
Sat Jun 9 01:20:06 UTC 2018
#56637: cmake and gobject_introspection portgroups together cause invalid CC
archflags
--------------------+--------------------
Reporter: drkp | Owner: (none)
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Keywords: | Port:
--------------------+--------------------
As part of updating poppler (see #54808 and https://github.com/macports
/macports-ports/pull/1975), I've noticed that g-ir-scanner is trying to
invoke clang with invalid archflags because CC is being set in build.args
to an invalid argument:
{{{
:info:build Command failed: cd
"/opt/local/var/macports/build/_opt_local_var_macports_sources_github
.com_macports-ports_graphics_poppler/poppler/work/poppler-0.65.0" &&
/usr/bin/make -j8 -w all CC="/usr/bin/clang {-arch x86_64}" VERBOSE=ON
}}}
I _think_ this is being caused by an interaction between the cmake-1.1 and
gobject_introspection-1.0 portgroups, since gobject_introspection-1.0 adds
the requisite archflags to build.args for g-ir-scanner's use, and the
cmake portgroup is doing some manipulation of the archflags that I don't
really understand.
Note that this isn't a problem for universal builds, except when
muniversal is used, since gobject_introspection-1.0 doesn't set CC for
those.
I've cc'd some of the people involved with the gobject_introspection and
cmake portgroups since I'm not sure which one the problem is with.
--
Ticket URL: <https://trac.macports.org/ticket/56637>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list