Opened 13 months ago
Last modified 4 weeks ago
#68421 new defect
libgcc-devel @14-20231001_0: Configuration aarch64-apple-darwin21 not supported
Reported by: | JDLH (Jim DeLaHunt) | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.8.1 |
Keywords: | arm64 | Cc: | barracuda156, p-bro, leebaylis, jbouttier, shuxiao9058 (Aaron Ji), DavidSagan (David Sagan), fmw42 (Fred Weinhaus), thynus, stiglitzkleiber (Kaspar) |
Port: | libgcc-devel |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
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?
Change History (24)
comment:1 Changed 13 months ago by barracuda156
comment:2 Changed 13 months ago by barracuda156
Cc: | barracuda156 added |
---|
comment:3 Changed 13 months ago by p-bro
Cc: | p-bro added |
---|
comment:4 Changed 12 months ago by leebaylis
Cc: | leebaylis added |
---|
comment:5 Changed 12 months ago by jbouttier
Cc: | jbouttier added |
---|
comment:6 Changed 12 months ago by ryandesign (Ryan Carsten Schmidt)
Keywords: | arm64 added |
---|---|
Summary: | libgcc-devel @14-20231001_0: build fails on arm64 "Configuration aarch64-apple-darwin21 not supported" → libgcc-devel @14-20231001_0: Configuration aarch64-apple-darwin21 not supported |
This ticket is specific to arm64 systems; #68679 is for x86_64 systems.
comment:7 follow-up: 9 Changed 12 months ago by zsoltbarat
Is there any chance this will be fixed soon? Is there a workaround?
comment:8 Changed 12 months ago by 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.
comment:9 Changed 12 months ago by 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.
comment:10 Changed 12 months ago by ryandesign (Ryan Carsten Schmidt)
Cc: | shuxiao9058 added |
---|
Has duplicate #68748.
comment:12 Changed 12 months ago by 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
comment:13 Changed 12 months ago by ryandesign (Ryan Carsten Schmidt)
Cc: | DavidSagan added |
---|
Has duplicate #68793 on arm64 Sonoma (Configuration aarch64-apple-darwin23 not supported
).
comment:14 Changed 12 months ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|
comment:15 Changed 10 months ago by ryandesign (Ryan Carsten Schmidt)
Cc: | fmw42 added |
---|
Has duplicate #69177 on arm64 Ventura (Configuration aarch64-apple-darwin22 not supported
).
comment:16 Changed 10 months ago by fmw42 (Fred Weinhaus)
Sorry, I do not understand the comment by Ryan Schmidt.
comment:17 Changed 10 months ago by 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.
comment:18 Changed 10 months ago by 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
comment:19 Changed 10 months ago by kencu (Ken)
they won't.
sudo port -f deactivate libgcc-devel sudo port -v install libgcc
and you should be fine.
comment:20 Changed 10 months ago by fmw42 (Fred Weinhaus)
Sorry, you say install libgcc and others say gcc13. Do either work on M1 Mac?
comment:21 Changed 10 months ago by 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.
comment:22 Changed 3 months ago by thynus
Cc: | thynus added |
---|
comment:23 Changed 4 weeks ago by ryandesign (Ryan Carsten Schmidt)
Cc: | stiglitzkleiber added |
---|
Has duplicate #71098.
comment:24 Changed 4 weeks ago by stiglitzkleiber (Kaspar)
I got the error "processing of port libgcc-devel failed" and also for me, this solved the problem:
sudo port -f deactivate libgcc-devel sudo port -v install libgcc
It is broken across the board now -_-
https://ports.macports.org/port/libgcc-devel/details