Opened 2 months ago

Closed 7 weeks ago

#70716 closed defect (duplicate)

cmake-bootstrap @3.9.6_0: Unable to install on MacOS15 (Sequoia)

Reported by: cemb007 Owned by:
Priority: Normal Milestone:
Component: ports Version:
Keywords: sequoia Cc: EvilJordan (Jordan Holberg), razzfazz (Daniel Becker), breun (Nils Breunese), radarhere (Andrew Murray), fmirkes (Florian Mirkes), hnarayanan (Harish Narayanan)
Port: cmake-bootstrap

Description (last modified by jmroot (Joshua Root))

Running on 10.15 (24A335), I installed the latest RC 16 Xcode from Apple and then reinstalled MacPorts (2.10.1, from source). When I try to install cmake-bootstrap (among a few others as this is a dependency), I receive the following:

:info:configure CMake 3.9.6, Copyright 2000-2017 Kitware, Inc. and Contributors
:info:configure C compiler on this system is: /usr/bin/clang -pipe -Os -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX15.sdk -arch x86_64 -std=gnu11
:info:configure ---------------------------------------------
:info:configure Error when bootstrapping CMake:
:info:configure Cannot find appropriate C++ compiler on this system.
:info:configure Please specify one using environment variable CXX.

Attachments (4)

main.log (26.1 KB) - added by cemb007 2 months ago.
main.log output
cmake_bootstrap.log (50.0 KB) - added by cemb007 2 months ago.
main.2.log (20.1 KB) - added by EvilJordan (Jordan Holberg) 8 weeks ago.
cmake_bootstrap.2.log (49.8 KB) - added by EvilJordan (Jordan Holberg) 8 weeks ago.

Download all attachments as: .zip

Change History (34)

Changed 2 months ago by cemb007

Attachment: main.log added

main.log output

comment:1 Changed 2 months ago by jmroot (Joshua Root)

Description: modified (diff)
Keywords: sequoia added
Summary: Unable to install on MacOSx 10.15 (Sequoia)cmake-bootstrap @3.9.6_0: Unable to install on MacOSx 10.15 (Sequoia)

Can you attach cmake_bootstrap.log?

comment:2 Changed 2 months ago by cemb007

already attached as "main.log", pulled from /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cmake-bootstrap/cmake-bootstrap/main.log

comment:3 Changed 2 months ago by ryandesign (Ryan Carsten Schmidt)

In addition to the main.log, please attach the cmake_bootstrap.log.

Changed 2 months ago by cemb007

Attachment: cmake_bootstrap.log added

comment:4 Changed 2 months ago by cemb007

Added bootstrap, hoping its helpful.

Changed 8 weeks ago by EvilJordan (Jordan Holberg)

Attachment: main.2.log added

comment:5 Changed 8 weeks ago by EvilJordan (Jordan Holberg)

Official MacOS 15 and XCode 16 release results in the same error. main.log and cmake_bootstrap.log attached.

Last edited 8 weeks ago by EvilJordan (Jordan Holberg) (previous) (diff)

comment:6 Changed 8 weeks ago by EvilJordan (Jordan Holberg)

Cc: EvilJordan added

Changed 8 weeks ago by EvilJordan (Jordan Holberg)

Attachment: cmake_bootstrap.2.log added

comment:7 Changed 8 weeks ago by razzfazz (Daniel Becker)

Cc: razzfazz added

comment:8 Changed 8 weeks ago by mbaehr (Michael Baehr)

This appears to be a general issue with being able to access C++ headers from the stdlib. See also #70716. I am experiencing this after a fresh install on Sequoia with any port that builds C++ - have so far reproduced with this one (cmake-bootstrap), as well as gmp, and a few others. My assumption is that this error was introduced with the macOS 15/Xcode 16 combination.

The issue seems to be specific to commands executed by macports during the build process. If I run configure by hand, using the same arguments that macports uses, and as the macports user, it succeeds. I can then advance the statefile and execute the build step via the port command and it will succeed. However, on other ports, this strategy does not always bring success.

comment:9 Changed 8 weeks ago by shuxiao9058 (Aaron Ji)

The same issue.

comment:10 Changed 8 weeks ago by Bradford-Miller (Bradford Miller)

Also same issue, just updated OS to Sequoia.

Version 0, edited 8 weeks ago by Bradford-Miller (Bradford Miller) (next)

comment:11 Changed 8 weeks ago by mattbishop (Matt Bishop)

I have two machines, one M1 Mini and one M2 MacBook. Both updated to Sequoia. The M1 Mini updated MacPorts, including cmake-bootstrap, with no issues. The M2 MacBook failed with this bug. Not sure why the difference, but both have numerous ports installed that require this lib to be present.

comment:12 Changed 8 weeks ago by Bradford-Miller (Bradford Miller)

Additional point of interest: while I do have Xcode and command-line tools installed and updated for Sequoia, port select --summary shows "none" as the options for all tools, while the prior version showed both any port installed versions AND the Apple supplied ones!

Setting CXX as the error suggests, to /usr/bin/gcc (or g++) doesn't help either.

Last edited 8 weeks ago by Bradford-Miller (Bradford Miller) (previous) (diff)

comment:13 Changed 8 weeks ago by breun (Nils Breunese)

Cc: breun added

comment:14 Changed 8 weeks ago by breun (Nils Breunese)

I don't know why, but I noticed that after removing/renaming /Library/Developer/CommandLineTools, this issues was gone.

comment:15 Changed 8 weeks ago by breun (Nils Breunese)

I guess that's related to ticket:70750

Last edited 8 weeks ago by breun (Nils Breunese) (previous) (diff)

comment:16 Changed 8 weeks ago by cemb007

I saw Sequoia version of MacPorts posted just recently, installed that and with the Command Line tools, all is installing correctly so far.

UPDATE: while some port installs have advanced/completed, I'm stuck with port "cmake", reattempting with CommandLineTools renamed. This did not work but running the compile command (per the main.log) manually with 'sudo', it compiled and following with sudo port install cmake, it worked. Very weird.

Last edited 8 weeks ago by cemb007 (previous) (diff)

comment:17 Changed 8 weeks ago by ttelford (Troy Telford)

I'll add my own entry: I too became stuck (unable to either continue, or roll back using sudo port restore --last (due to cmake-bootstrap failing in both cases as others have reported).

So, I've re-attempted after renaming /Library/Developer/CommandLineTools, and as others have reported, I've at least progressed past cmake-bootstrap on my M1 MacBook Pro.

Perhaps the wiki:Migration page should be updated to say "Please don't attempt an upgrade until we've fixed a few bugs"? Or at least reference this (and similar) workarounds for those who are less familiar with Trac?

I'm certain it can help many users avoid a few headaches and frustration.

Last edited 8 weeks ago by ryandesign (Ryan Carsten Schmidt) (previous) (diff)

comment:18 Changed 8 weeks ago by radarhere (Andrew Murray)

Cc: radarhere added

comment:19 in reply to:  17 ; Changed 8 weeks ago by ryandesign (Ryan Carsten Schmidt)

Replying to ttelford:

Perhaps the wiki:Migration page should be updated to say "Please don't attempt an upgrade until we've fixed a few bugs"?

A wiki is a community document; anyone can make reasonable edits to it.

This is not our bug to fix; it's Apple's.

ProblemHotlist is the best page to put this information on.

comment:20 Changed 7 weeks ago by fmirkes (Florian Mirkes)

Cc: fmirkes added

comment:21 in reply to:  19 ; Changed 7 weeks ago by EvilJordan (Jordan Holberg)

Replying to ryandesign:

This is not our bug to fix; it's Apple's.

Are you saying we're SOL with MacPorts until Apple notices this?

comment:22 Changed 7 weeks ago by mthused

I also saw this on my first 'port restore --last' migration attempt after installing Sequoia (release) and Xcode/CLT. Deleting the command-line tools and reinstalling fixed it for me and the C++ ports can find the headers they need, including cmake-bootstrap. Odd, but this seems to be a reasonable workaround for now.

comment:23 in reply to:  22 Changed 7 weeks ago by EvilJordan (Jordan Holberg)

Replying to mthused:

I also saw this on my first 'port restore --last' migration attempt after installing Sequoia (release) and Xcode/CLT. Deleting the command-line tools and reinstalling fixed it for me and the C++ ports can find the headers they need, including cmake-bootstrap. Odd, but this seems to be a reasonable workaround for now.

So your ooo was:

  • rm /CommandLineTools
  • port restore --last
  • reinstall CommandLineTools via the app store?

comment:24 in reply to:  21 ; Changed 7 weeks ago by kencu (Ken)

Replying to EvilJordan:

Replying to ryandesign:

This is not our bug to fix; it's Apple's.

Are you saying we're SOL with MacPorts until Apple notices this?

5 minute fix seems to work, give it a try, YMMV, blah blah:

comment:ticket:70750:35

Last edited 7 weeks ago by ryandesign (Ryan Carsten Schmidt) (previous) (diff)

comment:25 in reply to:  24 Changed 7 weeks ago by EvilJordan (Jordan Holberg)

Replying to kencu:

Replying to EvilJordan:

Replying to ryandesign:

This is not our bug to fix; it's Apple's.

Are you saying we're SOL with MacPorts until Apple notices this?

5 minute fix seems to work, give it a try, YMMV, blah blah:

comment:ticket:70750:35

This did indeed to seem to work! Thank you!

UPDATE: ok, that super-didn't work. (I tried only removing the offending subfolder and not the entirety of CommandLineTools). Lots of failures on later ports. Going to try again by removing CommandLineTools completely.

Last edited 7 weeks ago by ryandesign (Ryan Carsten Schmidt) (previous) (diff)

comment:26 Changed 7 weeks ago by cjones051073 (Chris Jones)

Summary: cmake-bootstrap @3.9.6_0: Unable to install on MacOSx 10.15 (Sequoia)cmake-bootstrap @3.9.6_0: Unable to install on MacOS15 (Sequoia)

comment:27 Changed 7 weeks ago by hnarayanan (Harish Narayanan)

Cc: hnarayanan added

comment:28 Changed 7 weeks ago by kencu (Ken)

Resolution: fixed
Status: newclosed

cmake-bootstrap installs without any trouble on Sequoia at present (cleanly reinstalled CLTs on this system).:

% port -v installed cmake-bootstrap
The following ports are currently installed:
  cmake-bootstrap @3.9.6_0 (active) requested_variants='' platform='darwin 24' archs='arm64' date='2024-09-21T09:50:29-0700'

comment:29 Changed 7 weeks ago by jmroot (Joshua Root)

Resolution: fixed
Status: closedreopened

comment:30 Changed 7 weeks ago by jmroot (Joshua Root)

Resolution: duplicate
Status: reopenedclosed

We didn't fix anything, this is just a duplicate of #70750.

Note: See TracTickets for help on using tickets.