Fwd: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more
René J.V. Bertin
rjvbertin at gmail.com
Sun Dec 11 14:38:14 CET 2016
- Previous message: Fwd: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more
- Next message: Fwd: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
On Sunday December 11 2016 14:56:23 Clemens Lang wrote:
> Two options:
>
> 1. Modify port(1) to print notes before installation of a port
I've volunteered to help find a solution to this situation, but with the underwhelming reception that got I'm not that enchanted to insist.
> Because it runs 'port -q info --line --subports' and parses the result.
> The flags to info guarantee that only the list of subports is printed.
Portindex? I'm pretty sure I've had a ui_msg for a while in one of my PortGroups without ever running into side-effects.
I kind of appreciate certain messages in the portindex output, in fact.
On Sunday December 11 2016 14:59:52 Mojca Miklavec wrote:
> There is no way to fix the buildbot scripts to work around that.
I doubt that, esp. not if you consider the possibility (and overall good idea) to extent `port info` to print information for machine reading.
> I find that ui_msg a bit strange, one should fix the code and either
> predict that the build would work or fail straight away. But until
> that part is fixed, I surrounded the code with "pre-fetch { ... }" to
> avoid problems like the one seen above.
As I said, I do not want to disallow building the port on a standard 10.6 because that worked just fine when I was still running 10.6 myself. I can confirm now that gcc 4.7+ still builds the code. Evidently I cannot run it on 10.9 because of a C++ runtime conflict that won't exist on 10.6 .
A pre-fetch fail is acceptable only if there's a way to introduce a variant that will let the code build with an appropriate gcc compiler of choice.
> But as you probably noticed none of the subports currently build on
> the 10.6 buildbots anyway:
Yes, I noticed one reason which Marko had caught before pushing (but without leaving me the time to address it). The Qt5 subport will probably fail because there currently is no Qt5 for 10.6, but that applies to all Qt5 dependents.
That's all I've been able to glean from the ragtag buildbot output that's been flooding my MacPorts in folder.
R.
- Previous message: Fwd: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more
- Next message: Fwd: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the macports-dev
mailing list