qt5-mac fails to install

[eburghardt@…]

Yosemite on Mac Mini

Ernests-Mac-mini:~ echobravo$ sudo port install qt5-mac
--->  Computing dependencies for qt5-mac
--->  Building qt5-mac
Error: org.macports.build for port qt5-mac returned: command execution failed
Please see the log file for port qt5-mac for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_qt5-mac/qt5-mac/main.log

[eburghardt@…]

error log

[larryv (Lawrence Velázquez)]

:debug:main Skipping completed org.macports.archivefetch (qt5-mac)
:debug:main Privilege de-escalation not attempted as not running as root.
:debug:main Skipping completed org.macports.fetch (qt5-mac)
:debug:main Privilege de-escalation not attempted as not running as root.
:debug:main Skipping completed org.macports.checksum (qt5-mac)
:debug:main Privilege de-escalation not attempted as not running as root.
:debug:main Skipping completed org.macports.extract (qt5-mac)
:debug:main Privilege de-escalation not attempted as not running as root.
:debug:main Skipping completed org.macports.patch (qt5-mac)
:debug:main Privilege de-escalation not attempted as not running as root.
:debug:main Skipping completed org.macports.configure (qt5-mac)
:debug:main Privilege de-escalation not attempted as not running as root.
:debug:build build phase started at Fri Jun 19 14:27:08 MDT 2015

This is not a clean log. As per ​the Guide, please clean, try again, and attach the new main.log.

[mkae (Marko Käning)]

Cc Me!

[RJVB (René Bertin)]

Curious error message:

:info:build make[3]: *** No rule to make target `rendering/style/GridT', needed by `.obj/svg/SVGAllInOne.o'.  Stop.

I have the object file, but the only thing matching the missing target is qt-everywhere-opensource-src-5.4.2//qtwebkit/Source/WebCore/rendering/style/GridTrackSize.h . On first sight I'd say that either something goes very wrong during the configure step, or else we're seeing a form of logfile corruption caused by several processes writing at once (those usuallllyyy tttaaakkkeee ttthhhiiisss fffooorrrmmm ttthhhoououugh ;)).

do you get this exact error systematically?

How many parallel jobs do you use for building?

As an experiment (mostly meant to help looking for an answer), I'd invite you to do the following in a terminal window:

> cd `port work qt5-mac`
> sudo -u macports vi .macports.qt5-mac.state

(or use any text editor you prefer, or pico) remove the line that says target: org.macports.configure and everything below it, save the file and exit from the editor

Then repeat the port command that failed earlier, but add -v before the install command. This will make the build process repeat the configure step, and then will build only some of the things you already built, plus anything not already built. If the same error occurs (you'll see it on your terminal this time, because of -v), repeat the command once more but this time add build.jobs=1 at the end of the line. Hopefully that will give a slightly more readable (and a certainly shorter) log, so please upload it.

[RJVB (René Bertin)]

Replying to eburghardt@…:

Apologies, I did not RTFM enuf... the clean is allowing me to install now.

Thank you very much for the support and patience,

Copying the resolution here for the record.

There's no shame in what happened, but I still don't understand the error you got. I've seen port builds fail and then succeed when trying again, for unclear reasons, but never one of the Qt ports.

Given the error you found I'd suggest you run a check on your harddisk. Something like:

> sudo port install smartmontools
## start a long self-test on disk0, presuming that is the device on which your MacPorts install lives
> sudo smartctl -t long /dev/disk0
## leave the computer running for the indicated duration then check for any reported errors
> sudo smartctl -a /dev/disk0

You can use the system normally during that self-test; disk IO may be a bit slower. Just take care that the disk cannot go "to sleep" (via the Energy Sys Prefs. panel).

[MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)]

Closing since the issue seems to be resolved with a clean reinstall.