libvpx @1.4.0_0 fails configuring when universal_archs does not contain build_arch

[udbraumann]

As it appears, the target i386-darwin-gcc is wrong:

...
:info:configure Configuring selected codecs
:info:configure Unrecognized toolchain 'i386-darwin-gcc'
:info:configure
:info:configure Configuration failed. This could reflect a misconfiguration of your
:info:configure toolchains, improper options selected, or another problem. If you
:info:configure don't see any useful error messages above, the next step is to look
:info:configure at the configure error log file (config.log) to determine what
:info:configure Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_libvpx/libvpx/work/libvpx-1.4.0" && ./configure --prefix=/opt/local --enable-vp8 --enable-vp9 --enable-internal-stats --enable-pic --enable-postproc --enable-multithread --enable-runtime-cpu-detect --disable-install-docs --disable-debug-libs --disable-examples --disable-unit-tests --target=i386-darwin-gcc
:info:configure Exit code: 1
:error:configure Failed to configure libvpx, consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_libvpx/libvpx/work/libvpx-1.4.0/config.log
...

In /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_libvpx/libvpx/work/libvpx-1.4.0/config.log I found this configure call:

# ./configure --prefix=/opt/local --enable-vp8 --enable-vp9 --enable-internal-stats --enable-pic --enable-postproc --enable-multithread --enable-runtime-cpu-detect --disable-install-docs --disable-debug-libs --disable-examples --disable-unit-tests --target=i386-darwin-gcc
Configuring selected codecs

The problem occurs independent from the compiler selected.

[ryandesign (Ryan Carsten Schmidt)]

Please attach the main.log file and the config.log file.

[ryandesign (Ryan Carsten Schmidt)]

I've fixed one possible cause of this error in r137267: namely, if for some reason you've set universal_archs in macports.conf to a value that does not include the value of build_arch in macports.conf. Is that the case on your system?

[udbraumann]

I don't think that I have touched my macports.conf, it has a time stamp from July 1st, 2013. Here are a few lines (I have a 64bit Intel machine):

...
# CPU architecture to compile for. Defaults to i386 or ppc on Mac OS X 10.5
# and earlier, depending on the CPU type detected at runtime. On Mac OS X 10.6
# the default is x86_64 if the CPU supports it, i386 otherwise.
#build_arch                     i386

# CPU architectures to use for Universal Binaries (+universal variant)
universal_archs         i386 ppc
...

[ryandesign (Ryan Carsten Schmidt)]

Ok, that's what I thought. My change above will fix the build with that kind of configuration, but your configuration is unsupported: that value for universal_archs is appropriate for Mac OS X 10.5 and earlier, not 10.6 or later. Please change universal_archs to x86_64 i386. You can just leave it commented out, and MacPorts will use a sensible default.

# CPU architecture to target. Supported values are "ppc", "ppc64",
# "i386", and "x86_64". Defaults to:
# - OS X 10.5 and earlier: "ppc" on PowerPC, otherwise "i386".
# - OS X 10.6 and later: "x86_64" on Intel 64, otherwise "i386".
#build_arch          	i386

# Space-delimited list of CPU architectures to target when building
# universal. Defaults to "i386 ppc" on OS X 10.5 and earlier and
# "x86_64 i386" on OS X 10.6 and later.
universal_archs     	x86_64 i386

More generally, you may want to compare your macports.conf with your macports.conf.default and see what other default settings you may want to bring back into your macports.conf, since it's clear your macports.conf is outdated and may contain other settings that are no longer appropriate.