cmake 3.12.4_0 fails to build

[dershow]

I have cmake 3.12.3_0 installed and I'm trying to upgrade to 3.12.4_0 and it fails to configure.

--->  Verifying checksums for cmake
--->  Extracting cmake
--->  Applying patches to cmake
--->  Configuring cmake
Error: Failed to configure cmake: configure failure: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cmake/cmake/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.

I've attached my log.

[michaelld (Michael Dickens)]

I see you're trying to build on 10.14 ... are you also trying to build as +universal? If so: +universal is not supported natively on 10.14.

[dershow]

No. I'm still on 10.13.6, not 10.14

[michaelld (Michael Dickens)]

Hmm ... OK ... but you've updated to Xcode 10.1 , yes?

[dershow]

Yes Xcode 10.1 (actually, the app store did it for me without my consent, when I had been putting it off for a little while...)

[michaelld (Michael Dickens)]

Are you trying to build cmake as +universal?

[dershow]

Yes. Some dependency needed it that way. At some point, I'm planning to upgrade to 10.14 and that will require rebuilding for migration, and I hope to figure out what is causing me to have a bunch of universal builds. I think, and hope, that it was just something historical that has stayed around, but for now, I have a bunch of +universal ports.

[michaelld (Michael Dickens)]

OK ... interesting. Could be a CMake thing checking for Xcode 10.1 & assuming building for 10.14 & thus failing for +universal; I don't know. What I can say is that, at least for your OS / MP install, this version of cmake +universal fails because of the +universal part. Since CMake cannot be a library dependency -- it's just an executable and related non-binary files -- you should be able to install it as -universal:

sudo port clean cmake
sudo port install cmake -universal

If you don't know why you're using +universal, then I'd strongly suggest getting rid of it. I think there's some FAQ for doing so; don't recall where. Might as well do it now so that you're better prepared for the migration to 10.14!

[dershow]

That worked. Thanks. I figured that the easiest way to handle the migration would be to output my list of installed ports, as the migration instructions suggest. Then, edit out +universal, then use that to install in 10.14. I used to have wine installed, and that required that many ports be built universal. And, once that happens, they all stay that way through updates etc. I never figured out an easy way to undo that, except by going through them all by hand, in the right order....

[michaelld (Michael Dickens)]

Glad that worked.

Wine is a 32-bit build right now, which means it won't build natively on 10.14 or with Xcode 10.1. Folks are finding creative ways to get it to build and run using the 10.13 SDK.

If I were to redo the +universal, I'd like do what you note: get the ports list into a file, edit the file to change +universal to -universal & then install those changed ports. Or, roughly something like:

port installed and active | grep universal | sed -e "s@(active)@@g" | sed -e "s|@[^+]*+|+|g" | sed -e "s@+universal@-universal@g" | tr '\n' ' ' > /tmp/ports_to_migrate.txt
sudo port -p -N install $(cat /tmp/ports_to_migrate.txt)

I'm going to go ahead and close this ticket as fixed, since it is, sort of.