Opened 15 months ago
Closed 12 months ago
#68008 closed defect (fixed)
rust-bootstrap: attempts to build universal, but the latter no longer supported by cmake-bootstrap
Reported by: | mascguy (Christopher Nielsen) | Owned by: | MarcusCalhoun-Lopez (Marcus Calhoun-Lopez) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.8.1 |
Keywords: | Cc: | kencu (Ken) | |
Port: | rust-bootstrap cmake-bootstrap |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
It's not clear whether this is an issue with rust-bootstrap
, cmake-bootstrap
, or both. But the former enables +universal
by default, whilst the latter no longer supports universal builds as of 2023-06:
[a4fda7b98703ff055b9dacb7e1dca58d5376d490/macports-ports]
Perhaps that's fine though...?
However, the build for rust-bootstrap
is blocked, due to cmake-bootstrap
failing to build:
--------------------------------------------- CMake 3.9.6, Copyright 2000-2017 Kitware, Inc. and Contributors --------------------------------------------- Error when bootstrapping CMake: Cannot find appropriate C compiler on this system. Please specify one using environment variable CC. See cmake_bootstrap.log for compilers attempted.
Full log also attached: cmake-bootstrap-build-13-arm.log.gz
.
Attachments (1)
Change History (7)
Changed 15 months ago by mascguy (Christopher Nielsen)
Attachment: | cmake-bootstrap-build-13-arm.log.gz added |
---|
comment:1 Changed 15 months ago by mascguy (Christopher Nielsen)
comment:2 Changed 15 months ago by kencu (Ken)
there should be no need for cmake-bootstrap to build universal, even if rust-bootstrap wants to build universal.
it is marked as "installs_libs no" I believe, and base is supposed to see that and ignore the need for universal in cmake-bootstrap.
sometimes we need to "depends skip archcheck" things, even though we shouldn't need to -- pretty much every time someone adds that, one of Josh or Ryan points out it is unnecessary and removes it. So that is kinda voodoo to me...
comment:3 Changed 15 months ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|
Replying to mascguy:
It's not clear whether this is an issue with
rust-bootstrap
,cmake-bootstrap
, or both. But the former enables+universal
by default, whilst the latter no longer supports universal builds as of 2023-06:[a4fda7b98703ff055b9dacb7e1dca58d5376d490/macports-ports]
Perhaps that's fine though...?
This did not disable the universal variant. It added universal_variant no
which merely tells MacPorts base not to add the default universal variant. But the port still includes the muniversal portgroup which adds its own universal variant. To disable the universal variant would require removing the muniversal portgroup.
comment:4 follow-up: 5 Changed 15 months ago by kencu (Ken)
comment:5 Changed 15 months ago by mascguy (Christopher Nielsen)
Replying to kencu:
In 45f5a540a2d4c8596a92b61eb8bf26462a1bc2f3/macports-ports (master):
Thanks Ken! I also re-queued builds for rust-bootstrap
.
comment:6 Changed 12 months ago by kencu (Ken)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
fixed by [45f5a540a2d4c8596a92b61eb8bf26462a1bc2f3/macports-ports] (master):
cmake-bootstrap: remove muniversal PG
see: #68008
Perusing the build history for
rust-bootstrap
, perhaps this is an existing issue/limitation:https://ports.macports.org/port/rust-bootstrap/builds/
If so - and some macOS releases and/or archs aren't supported - the port should probably be updated with
known_fail
. (Or{platforms xxx}
, etc.)