libgcc-devel @14-20231001_0: Configuration aarch64-apple-darwin21 not supported

[JDLH (Jim DeLaHunt)]

When I attempt to build libgcc-devel @14-20231001_0 on a MacBook Pro with an arm64 (Apple M1 Max) processor, the build fails.

The buildbot's failure matches my own. The relevant part of ​main.log reads,

checking for clock_t... yes
checking for F_SETLKW... yes
checking for O_CLOEXEC... yes
checking for fcntl.h... (cached) yes
checking whether O_NONBLOCK is declared... yes
checking for AF_UNIX... yes
checking for AF_INET6... yes
checking for _LK_LOCK... no
checking if mkdir takes one argument... no
*** Configuration aarch64-apple-darwin21 not supported
make[2]: *** [configure-stage1-gcc] Error 1

I presently have libgcc-devel @12-20221229_0 installed. It seemed to build correctly.

I don't understand the buildbot system well, but on this port's ​Port Health listing I see red X's for all platforms. Is that the same problem, or something else?

[barracuda156]

It is broken across the board now -_-

​https://ports.macports.org/port/libgcc-devel/details

[ryandesign (Ryan Carsten Schmidt)]

This ticket is specific to arm64 systems; #68679 is for x86_64 systems.

[zsoltbarat]

Is there any chance this will be fixed soon? Is there a workaround?

[kencu (Ken)]

probably not until xcode 15.1 comes out.

you should not use gcc-devel for anything anyway…is something calling it in for you?

use the current latest gcc, currently gcc13, instead.

[JDLH (Jim DeLaHunt)]

Replying to zsoltbarat:

…Is there a workaround?

For what it's worth, my workaround was: "I blundered around until I fixed the problem (I think) by 1. deactivating libgcc-devel, blasting past the warning that five ports would break; then 2. installing port gcc13, which seemed to fill the hole left by libgcc-devel."

This seems to supports the insight that the presence of the libgcc-devel and gcc-devel is probably part of a user's past expedient workaround to a past problem, so switching to use a current port like gcc13 instead of gcc-devel may be the user's best way out of a situation like this. In parallel, I imagine it is also desirable to have gcc-devel catch up to current systems and OSs in due course.

There was a brief thread on the macports-users email list in October 2023 about this situation: "​Help me understand dependents of libgcc-devel vs gcc13?". Maybe the answers there will help others facing this situation.

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #68748.

[shuxiao9058 (Aaron Ji)]

How can I resolve this issue now ?

[rmv (Ramon Montoya Vozmediano)]

As mentioned, this also worked for me: (ignore the warnings)

sudo port deactivate libgcc-devel
sudo port install gcc13

Maybe gcc12 would work too

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #68793 on arm64 Sonoma (Configuration aarch64-apple-darwin23 not supported).

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #69177 on arm64 Ventura (Configuration aarch64-apple-darwin22 not supported).

[fmw42 (Fred Weinhaus)]

Sorry, I do not understand the comment by Ryan Schmidt.

[kencu (Ken)]

libgcc-devel has no maintainer and it is not a super-clean port. It fails various places and it is mostly for our testing purposes.

Please don't use it for anything and you will be much happier.

[fmw42 (Fred Weinhaus)]

Why are many of my port using it? How do I get around it? I see notes about installing gcc13 and removing libgcc-devel. But won't my ports still be looking for libgcc-devel? I have gcc12 installed also, but it does not seem to use that?

I do not understand, when I got my M1 Mac, the ports that are now having trouble installed fine presumably with libgcc-devel.

Can someone tell me if my concerns above are not founded and that my ports will install after installing gcc13 and removing libgcc-devel ? I am not an expert with MacPorts.

Thanks

[kencu (Ken)]

they won't.

sudo port -f deactivate libgcc-devel
sudo port -v install libgcc

and you should be fine.

[fmw42 (Fred Weinhaus)]

Sorry, you say install libgcc and others say gcc13. Do either work on M1 Mac?

[kencu (Ken)]

libgcc gives you the gcc libraries that some things need to link against to work

gcc13 gives you gcc13, if you need to compile things using gcc and will also bring in libgcc as part of it's installation.

Either way, you get libgcc.