webkit-gtk configure failure

[deesto (John S. De Stefano Jr.)]

DEBUG: Executing command line:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_svn.macports.org_trunk_dports_www_webkit-gtk/webkit-gtk/work/webkitgtk-2.0.0" && ./configure --prefix=/opt/local --with-gtk=2.0 --disable-webkit2 --disable-introspection --enable-svg --enable-geolocation --enable-media-stream --enable-webgl --enable-video 
Error: org.macports.configure for port webkit-gtk returned: configure failure: command execution failed
DEBUG: Error code: NONE
DEBUG: Backtrace: configure failure: command execution failed
    while executing
"$procedure $targetname"
DEBUG: Registry error: google-test not registered as installed & active.
Error: Unable to upgrade port: 1

configure: error: Compiler GCC >= 4.7 or Clang >= 3.0 is required for C compilation

Note that when google-test is installed and activated, installer debug mentions that it is "not registered as installed & active", and when it is installed and active, it complains that it "cannot be built while google-test is active."

[mf2k (Frank Schima)]

In the future, please Cc the port maintainer(s).

[jeremyhu (Jeremy Huddleston Sequoia)]

r104778

[deesto (John S. De Stefano Jr.)]

Thanks for looking at this. While it may be due to some self-inflicted config problem, all other ports upgrade successfully, while ufraw now fails with a different problem.

Warning: All compilers are either blacklisted or unavailable; using first fallback entry as last resort

[deesto (John S. De Stefano Jr.)]

latest upgrade debug stdout output

[deesto (John S. De Stefano Jr.)]

latest port log

[jmroot (Joshua Root)]

I think Jeremy forgot that the fallback list in 2.1.3 is different to that in trunk.

[jeremyhu (Jeremy Huddleston Sequoia)]

Ah yep, we'll need that ugly dependency-addition workaround until 2.2 is released.

[jeremyhu (Jeremy Huddleston Sequoia)]

r104843

[ryandesign (Ryan Carsten Schmidt)]

I still have "All compilers are either blacklisted or unavailable; using first fallback entry as last resort", followed by configure failing with "configure: error: Compiler GCC >= 4.7 or Clang >= 3.0 is required for C compilation" because the first fallback compiler in MacPorts 2.1.3 is one of the compilers the port blacklists. I still don't understand how ports are meant to deal with this. I don't understand why MacPorts would try the "first fallback entry" if it's a blacklisted compiler. Why wouldn't it try the first fallback entry that's not blacklisted? Then ports could simply append a suitable compiler to compiler.fallback.

[cooljeanius (Eric Gallager)]

Cc Me!

[deesto (John S. De Stefano Jr.)]

Replying to ryandesign@…:

I still have "All compilers are either blacklisted or unavailable; using first fallback entry as last resort", followed by configure failing with "configure: error: Compiler GCC >= 4.7 or Clang >= 3.0 is required for C compilation" because the first fallback compiler in MacPorts 2.1.3 is one of the compilers the port blacklists.

I can confirm that I still see the same error.

[jeremyhu (Jeremy Huddleston Sequoia)]

r104875 should do it then

[jmroot (Joshua Root)]

Replying to ryandesign@…:

I don't understand why MacPorts would try the "first fallback entry" if it's a blacklisted compiler.

Because, as the message plainly says, "All compilers are either blacklisted or unavailable". You obviously don't want a port to ever be in this state; that's why there is a warning message.

Why wouldn't it try the first fallback entry that's not blacklisted? Then ports could simply append a suitable compiler to compiler.fallback.

It does if there is one, and you can and should.