#46739: cmake @3.0.2_1+universal: configuring PowerPC on an Intel system fails with "Unknown option: --host=powerpc-apple-darwin10.8.0" ----------------------+------------------- Reporter: larryv@… | Owner: css@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: cmake ----------------------+------------------- The `muniversal-1.0` portgroup adds a “`--host`” option to `configure.args` when the host and build architectures differ. CMake’s configure script doesn’t recognize this option. {{{ :debug:configure Executing command line: cd "/opt/local/var/macports/build/_Users_larryv_Projects_MacPorts_git_trunk_dports_devel_cmake/cmake/work/cmake-3.0.2-ppc" && ./configure --prefix=/opt/local --mandir=/share/man --docdir=/share/doc/cmake --parallel=1 --init=/opt/local/var/macports/build/_Users_larryv_Projects_MacPorts_git_trunk_dports_devel_cmake/cmake/work/cmake-3.0.2/macports.cmake --system-libs --host=powerpc-apple-darwin10.8.0 :info:configure Unknown option: --host=powerpc-apple-darwin10.8.0 }}} This only manifests on Snow Leopard because the `cmake` portfile already sets {{{ supported_archs i386 x86_64 }}} on Intel and {{{ supported_archs ppc ppc64 }}} on PowerPC. The [[attachment:cmake-no-host.patch|attached patch]] stops `muniversal-1.0` from adding the option and allows the build to complete successfully, but I don’t know whether it’s the cleanest solution. Another approach would be to drop PowerPC support entirely; I don’t know how useful it is to build `cmake` itself universally. -- Ticket URL: <https://trac.macports.org/ticket/46739> MacPorts <https://www.macports.org/> Ports system for OS X