Opened 6 months ago
Last modified 5 months ago
#71702 assigned defect
mariadb-10.11 install fails on Sequoia 15.2
Reported by: | inflatador (Brian King) | Owned by: | michaelld (Michael Dickens) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | arm64 sequoia | Cc: | |
Port: | mariadb-10.11 |
Description
I'm unable to install the mariadb-10.11 port on my Macbook Pro (Apple Silicon). The message "This header is only meant to be used on x86 and x64 architecture" appears frequently in the attached build log.
Thanks for taking a look, please let me know if you need additional information.
Attachments (1)
Change History (5)
comment:1 Changed 6 months ago by ryandesign (Ryan Carsten Schmidt)
Keywords: | sequoia added |
---|---|
Owner: | set to michaelld |
Status: | new → assigned |
comment:2 follow-up: 3 Changed 6 months ago by kencu (Ken)
Changed 6 months ago by jmroot (Joshua Root)
Attachment: | main.log.bz2 added |
---|
comment:3 Changed 6 months ago by jmroot (Joshua Root)
Replying to kencu:
So by any chance are you running this build from a shell that is running as Intel on an arm64 Mac? You might do that in one of several ways, either on purpose or by accident.
If this is the case, you should get a warning at startup: "MacPorts started under Rosetta 2, re-executing natively" (and as the message suggests, it then re-executes itself natively, which is intended to avoid this kind of problem.)
The SYSTEM processor
message is simply printing out the value of ${CMAKE_SYSTEM_PROCESSOR}
, so I would suggest checking the installed arch of cmake (port -v installed cmake
).
comment:4 Changed 5 months ago by inflatador (Brian King)
Thanks all. I did recently migrate from an Intel-based Mac to an Apple Silicon-based Mac, so that's likely the root cause. I'm not seeing the Rosetta warning, and the cmake command output looks correct:
port -v installed cmake The following ports are currently installed: cmake @3.31.3_0 (active) requested_variants='' platform='darwin 24' archs='arm64' date='2024-12-29T15:24:00-0600'
Regardless, it does not seem like a problem related to the mariadb port, so feel free to close this one out. I'll try to force rebuild cmake and see what happens. Thanks again for your time and Happy New Year!
I was going to take a look at this for you, but on my system, no trouble:
I see in your log:
and in my log:
and that would likely be the issue to be sorted out.
So by any chance are you running this build from a shell that is running as Intel on an arm64 Mac? You might do that in one of several ways, either on purpose or by accident.