(gnutls,10.9.1) Failed to build gnutls: command execution failed

[mrkapqa]

upon

sudo port install mpv

on mavericks 10.9.1

--->  Building gnutls
Error: Failed to build gnutls: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_gnutls/gnutls/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port mpv failed

[mrkapqa]

tried to overcome with

sudo port clean mpv sudo port install clang-5.0 sudo port activate clang-5.0 -f sudo port clean gnutls sudo port install mpv

however i ran into similar issue

--->  Fetching distfiles for gnutls
--->  Verifying checksums for gnutls
--->  Extracting gnutls
--->  Applying patches to gnutls
--->  Configuring gnutls
--->  Building gnutls
Error: Failed to build gnutls: command execution failed

please see log.

[mrkapqa]

Hello ,

this has been solved by installing Xcode 5.1.1 or some other change

prior i did only

sudo xcodebuild -install

which apparently was no more enough.

Thanks

[ryandesign (Ryan Carsten Schmidt)]

Installing a port also activates it, meaning it places its files on your disk. Activating a port that is already installed and active does nothing.

You should not attempt to force activate a port unless you know exactly why you are doing it and you are prepared to accept the consequences.

The -f flag and other single-letter flags do nothing unless placed between the word port and the subcommand. (To force activate (which again I do not recommend) you would have needed sudo port -f activate ....)

Just installing a compiler port does not automatically cause it to be used to build other ports. If a port needs a compiler that's provided by a port, it will install it for you.

The log says the problem was:

:info:build Undefined symbols for architecture x86_64:
:info:build   "___get_cpuid_count", referenced from:
:info:build       _register_x86_crypto in libaccelerated.a(x86-common.o)
:info:build ld: symbol(s) not found for architecture x86_64
:info:build clang: error: linker command failed with exit code 1 (use -v to see invocation)

This could have been a problem with an older compiler not providing this function. If your command line tools were older than Xcode 5.1.1, that could explain it. Make sure you install the latest command line tools to match your Xcode version. We should update this port's blacklist so that older compilers that don't have this function don't get used.

If you're really running OS X 10.9.1, please update to 10.9.5 plus the latest security update.

[kencu (Ken)]

Looks like this has been "repaired" as above. There appears to be nothing further to fix in the portfile, so the best closing message is "works for me", it appears.

[ryandesign (Ryan Carsten Schmidt)]

Replying to ryandesign:

We should update this port's blacklist so that older compilers that don't have this function don't get used.

{clang < 1000} was blacklisted for this, but that's way too restrictive just to address this issue. Blacklisting {clang < 500} should have been sufficient.