[MacPorts] #52161: mp-buildbot: incorrect error message when a port cannot be installed due to arch mismatch

MacPorts noreply at macports.org
Fri Sep 2 13:32:58 CEST 2016


#52161: mp-buildbot: incorrect error message when a port cannot be installed due to
arch mismatch
--------------------------+--------------------------------
 Reporter:  ryandesign@…  |      Owner:  macports-tickets@…
     Type:  defect        |     Status:  new
 Priority:  Normal        |  Milestone:
Component:  contrib       |    Version:  2.3.4
 Keywords:                |       Port:
--------------------------+--------------------------------
 If I try to install wine on PowerPC, it fails, as it should:

 {{{
 # /opt/local/bin/port install wine
 Error: wine cannot be installed for the configured build_arch 'ppc'
 because it only supports the arch(s) 'i386'.
 To report a bug, follow the instructions in the guide:
     http://guide.macports.org/#project.tickets
 Error: Processing of port wine failed
 }}}

 However, when the buildbot tries to
 [https://build.macports.org/builders/ports-10.5_ppc_legacy-
 builder/builds/895/steps/install-dependencies/logs/stdio install
 dependencies of wine], using [browser:contrib/mp-
 buildbot/tools/dependencies.tcl dependencies.tcl], it fails with a weirder
 error:

 {{{
 Error: Cannot install wine for the arch(s) 'powerpc' because
 Error: its dependency bison does not build for the required arch(s) by
 default
 Error: and the configured universal_archs 'i386 ppc' are not sufficient.
 architecture mismatch
     while executing
 "mportdepends $mport "activate""
     invoked from within
 "if {[mportdepends $mport "activate"] != 0} {
     ui_error "mportdepends $portname activate failed."
     exit 1
 }"
     (file
 "/opt/bblocal/var/buildworker/ports/build/mpbb/tools/dependencies.tcl"
 line 74)
 }}}

 It should fail, of course, but the reason given for the failure is wrong.

 1. "powerpc" is not a valid build architecture. It's a valid ''system''
 architecture—a valid value for `${os.arch}`—but not a valid
 `${build_arch}`.
 2. The problem is not that wine's dependencies can't be built on this
 system. The problem is that wine itself can't be built on this system.

 I didn't see any architecture-related code in dependencies.tcl, so this
 might actually be a base bug.

-- 
Ticket URL: <https://trac.macports.org/ticket/52161>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list