[MacPorts] #38640: webkit-gtk configure failure
#38640: webkit-gtk configure failure -------------------------------------------------+------------------------- Reporter: deesto@… | Owner: macports- Type: defect | tickets@… Priority: Normal | Status: new Component: ports | Milestone: Keywords: webkit-gtk, configure failure, gcc, | Version: 2.1.3 clang | Port: webkit-gtk -------------------------------------------------+------------------------- {{{ 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." -- Ticket URL: <https://trac.macports.org/ticket/38640> MacPorts <http://www.macports.org/> Ports system for OS X
#38640: webkit-gtk configure failure -------------------------+------------------------ Reporter: deesto@… | Owner: jeremyhu@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: webkit-gtk | -------------------------+------------------------ Changes (by macsforever2000@…): * cc: devans@… (added) * keywords: webkit-gtk, configure failure, gcc, clang => * owner: macports-tickets@… => jeremyhu@… Comment: In the future, please Cc the port maintainer(s). -- Ticket URL: <https://trac.macports.org/ticket/38640#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X
#38640: webkit-gtk configure failure -------------------------+------------------------ Reporter: deesto@… | Owner: jeremyhu@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: fixed | Keywords: Port: webkit-gtk | -------------------------+------------------------ Changes (by jeremyhu@…): * status: new => closed * resolution: => fixed Comment: r104778 -- Ticket URL: <https://trac.macports.org/ticket/38640#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X
#38640: webkit-gtk configure failure -------------------------+------------------------ Reporter: deesto@… | Owner: jeremyhu@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: fixed | Keywords: Port: webkit-gtk | -------------------------+------------------------ Comment (by deesto@…): 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 }}} -- Ticket URL: <https://trac.macports.org/ticket/38640#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X
#38640: webkit-gtk configure failure -------------------------+------------------------ Reporter: deesto@… | Owner: jeremyhu@… Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: webkit-gtk | -------------------------+------------------------ Changes (by jmr@…): * status: closed => reopened * resolution: fixed => Comment: I think Jeremy forgot that the fallback list in 2.1.3 is different to that in trunk. -- Ticket URL: <https://trac.macports.org/ticket/38640#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X
#38640: webkit-gtk configure failure -------------------------+------------------------ Reporter: deesto@… | Owner: jeremyhu@… Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: webkit-gtk | -------------------------+------------------------ Comment (by jeremyhu@…): Ah yep, we'll need that ugly dependency-addition workaround until 2.2 is released. -- Ticket URL: <https://trac.macports.org/ticket/38640#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X
#38640: webkit-gtk configure failure -------------------------+------------------------ Reporter: deesto@… | Owner: jeremyhu@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: fixed | Keywords: Port: webkit-gtk | -------------------------+------------------------ Changes (by jeremyhu@…): * status: reopened => closed * resolution: => fixed Comment: r104843 -- Ticket URL: <https://trac.macports.org/ticket/38640#comment:6> MacPorts <http://www.macports.org/> Ports system for OS X
#38640: webkit-gtk configure failure -------------------------+------------------------ Reporter: deesto@… | Owner: jeremyhu@… Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: webkit-gtk | -------------------------+------------------------ Changes (by ryandesign@…): * cc: ryandesign@… (added) * status: closed => reopened * resolution: fixed => Comment: 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. -- Ticket URL: <https://trac.macports.org/ticket/38640#comment:7> MacPorts <http://www.macports.org/> Ports system for OS X
#38640: webkit-gtk configure failure -------------------------+------------------------ Reporter: deesto@… | Owner: jeremyhu@… Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: webkit-gtk | -------------------------+------------------------ Comment (by deesto@…): Replying to [comment:7 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. -- Ticket URL: <https://trac.macports.org/ticket/38640#comment:9> MacPorts <http://www.macports.org/> Ports system for OS X
#38640: webkit-gtk configure failure -------------------------+------------------------ Reporter: deesto@… | Owner: jeremyhu@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: fixed | Keywords: Port: webkit-gtk | -------------------------+------------------------ Changes (by jeremyhu@…): * status: reopened => closed * resolution: => fixed Comment: r104875 should do it then -- Ticket URL: <https://trac.macports.org/ticket/38640#comment:10> MacPorts <http://www.macports.org/> Ports system for OS X
#38640: webkit-gtk configure failure -------------------------+------------------------ Reporter: deesto@… | Owner: jeremyhu@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: fixed | Keywords: Port: webkit-gtk | -------------------------+------------------------ Comment (by jmr@…): Replying to [comment:7 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. -- Ticket URL: <https://trac.macports.org/ticket/38640#comment:11> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts