Opened 3 years ago
Last modified 3 years ago
#63131 assigned defect
mono: ccache: error: Could not find compiler "-DBORINGSSL_IMPLEMENTATION" in PATH
| Reported by: | TruePath (Peter Gerdes) | Owned by: | MarcusCalhoun-Lopez (Marcus Calhoun-Lopez) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.7.1 |
| Keywords: | arm64 | Cc: | |
| Port: | mono |
Description
I've attached the log file here as it seems clear that mono is trying to link x86 assembler during compilation (hence the failure) but any more insight is above my pay grade.
Attachments (1)
Change History (10)
Changed 3 years ago by TruePath (Peter Gerdes)
comment:1 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)
| Keywords: | arm64 added; m1 arm removed |
|---|---|
| Owner: | set to MarcusCalhoun-Lopez |
| Status: | new → assigned |
| Summary: | Mono fails to build on M1 mac → mono: ccache: error: Could not find compiler "-DBORINGSSL_IMPLEMENTATION" in PATH |
comment:2 follow-up: 6 Changed 3 years ago by kencu (Ken)
Probably not relevant, but your MacPorts is outdated:
debug:sysinfo MacPorts 2.6.99
when you install from git head or similar, you may not be able to know when a new version of MacPorts has been released, which it was a while ago. And IIRC, port selfupdate won't update you either.
So you need to update to 2.7.1 one way or another. I would clone the git repo and checkout the 2.7 branch and install from source, but you could do some other method to get back on the proper track.
comment:3 follow-up: 7 Changed 3 years ago by TruePath (Peter Gerdes)
Ohh, that's weird since I literally just downloaded the installer yesterday when I got my new M1 mac. I hadn't checked the version but I'm pretty sure I downloaded the latest package from the webpage.
comment:4 follow-up: 5 Changed 3 years ago by TruePath (Peter Gerdes)
Wait no, I just ran port -v and it reports 2.7.1 as the version and it was installed from a package labeled MacPorts-2.7.1-11-BigSur.pkg so I don't see how it could not be 2.7.1.
Looks like there is another bug about debug:sysinfo to fix! I don't know where to submit but maybe you do. And I even followed the directions on removing all my existing ports after xfering to the new computer so everything should be just as is on a new install.
comment:5 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to TruePath:
Looks like there is another bug about debug:sysinfo to fix!
There is no bug. If you look more closely in the log, you'll see that it contains five separate installation attempts. The first one was made with MacPorts 2.6.99, later ones were made with MacPorts 2.7.0 and 2.7.1.
comment:6 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to kencu:
And IIRC,
port selfupdatewon't update you either.
selfupdate will update you to newer version numbers. If you've installed from git and have MacPorts "2.6.99", selfupdate will not update you to newer versions of "2.6.99" but it will update you to 2.7.0 or later.
comment:7 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to TruePath:
Ohh, that's weird since I literally just downloaded the installer yesterday when I got my new M1 mac.
So this is on an Apple Silicon Mac? Because it doesn't look like it. The log shows:
:debug:main OS darwin/20.5.0 (macOS 11.4) arch i386
That means MacPorts thinks it is running on an Intel Mac and will consequently try to build things for Intel.
One way that MacPorts can get the wrong idea about this is if you are running port from within a third-party terminal program that is compiled for Intel. If so, don't do that: run MacPorts in a terminal program that's compiled for Apple Silicon, such as Apple's Terminal or the latest version of iTerm2.
comment:8 Changed 3 years ago by TruePath (Peter Gerdes)
Ahh, I'll try from terminal rather than iterm and see what happens.
comment:9 Changed 3 years ago by TruePath (Peter Gerdes)
Go ahead and close this one…it was my bad. I thought I'd updated my macports.conf but apparently it was still set to x86.
compile log