[MacPorts] #63251: GILDAS build fail on Big Sur / arm64
MacPorts
noreply at macports.org
Tue Jul 20 00:41:24 UTC 2021
#63251: GILDAS build fail on Big Sur / arm64
-----------------------+----------------------
Reporter: rampante | Owner: bardeau
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: gildas |
-----------------------+----------------------
Old description:
> I've been trying to install gildas on macOS Big Sur 11.4 (Xcode version
> 12.5, M1 chip) without success:
> - at first I got a "ld: framework not found CoreFoundation" error.
> Following [https://trac.macports.org/ticket/59347 this ticket], I
> reinstalled gcc11 and python38 from source
> - now, on the other hand, this warning appears:
> {{{
> --> Found 3 broken files, matching files to ports
> ---> Found 1 broken port, determining rebuild order
> You can always run 'port rev-upgrade' again to fix errors.
> The following ports will be rebuilt: gildas @202107a+gcc11
> }}}
> and, after a few of attempts, the build is still broken. Running port -d
> -y rev-upgrade yields the following output.
New description:
I've been trying to install gildas on macOS Big Sur 11.4 (Xcode version
12.5, M1 chip) without success:
- at first I got a "ld: framework not found CoreFoundation" error.
Following [ticket:59347 this ticket], I reinstalled gcc11 and python38
from source
- now, on the other hand, this warning appears:
{{{
--> Found 3 broken files, matching files to ports
---> Found 1 broken port, determining rebuild order
You can always run 'port rev-upgrade' again to fix errors.
The following ports will be rebuilt: gildas @202107a+gcc11
}}}
and, after a few of attempts, the build is still broken. Running port -d
-y rev-upgrade yields the following output.
--
Comment (by ryandesign):
> Why does MacPorts says "this installation is configured to use libc++"?
Because MacPorts installations on Mac OS X 10.6 and later are configured
by default to use libc++. The setting is `cxx_stdlib`. It can be changed
in macports.conf. The setting does not appear in the default macports.conf
because it is not really intended to be changed, and if you change it you
must uninstall and reinstall all C++-using ports.
> What should be done to avoid this error?
The port should not compile C++ software using g++. If that cannot be
avoided, and if the port does not use any C++ libraries installed by
another port, and if the port does not install any C++ libraries that are
to be used by other ports, then the port can suppress the warning by
setting (IIRC) `configure.cxx_stdlib macports-libstdc++`.
--
Ticket URL: <https://trac.macports.org/ticket/63251#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list