[MacPorts] #47907: libvpx: update to 1.4.0

MacPorts noreply at macports.org
Tue Jun 2 06:37:08 PDT 2015

#47907: libvpx: update to 1.4.0
  Reporter:  ryandesign@…  |      Owner:  devans@…
      Type:  update        |     Status:  assigned
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:
Resolution:                |   Keywords:
      Port:  libvpx        |

Comment (by ryandesign@…):

 `universal_variant no` doesn't disable the universal variant when the
 muniversal portgroup is included; comment out `PortGroup muniversal 1.0`
 as well to disable the universal variant.

 The only two values that `os.arch` will ever be are `i386` and `powerpc`,
 so the conditional `[string match "ppc*" ${os.arch}]` never matches, so
 the yasm dependency is always still there. Removing yasm when `os.arch` is
 `powerpc` is probably also not the right idea: what if you want to build
 universal for ppc and i386 on a ppc machine? Don't you need yasm then? I
 can test that later when universal builds are working. I think probably
 the way this should go is something like (untested):

 if {[string match "*86*" [get_canonical_archs]} {
     depends_build-append port:yasm

 That way, yasm only gets added if you're building for an Intel arch.


 It doesn't get past the configure phase on 10.5 ppc. [attachment:main.log
 main.log], [attachment:config.log config.log]. It seems it has decided to
 build universal, even though I did not select that variant, and then
 failed, possibly because the MacPorts-supplied PowerPC arch flags got
 added to the project-supplied Intel arch flags, leading to the error
 "`gcc-4.2: -E, -S, -save-temps and -M options are not allowed with
 multiple -arch flags`". Maybe this is a reason why we were specifying the
 target before.

Ticket URL: <https://trac.macports.org/ticket/47907#comment:3>
MacPorts <https://www.macports.org/>
Ports system for OS X

More information about the macports-tickets mailing list