[MacPorts] #68421: libgcc-devel @14-20231001_0: Configuration aarch64-apple-darwin21 not supported

MacPorts noreply at macports.org
Sun Nov 19 00:23:20 UTC 2023


#68421: libgcc-devel @14-20231001_0: Configuration aarch64-apple-darwin21 not
supported
---------------------------+--------------------
  Reporter:  JDLH          |      Owner:  (none)
      Type:  defect        |     Status:  new
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.8.1
Resolution:                |   Keywords:  arm64
      Port:  libgcc-devel  |
---------------------------+--------------------

Comment (by JDLH):

 Replying to [comment:7 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: "[https://lists.macports.org/pipermail/macports-
 users/2023-October/052304.html Help me understand dependents of libgcc-
 devel vs gcc13?]". Maybe the answers there will help others facing this
 situation.

-- 
Ticket URL: <https://trac.macports.org/ticket/68421#comment:9>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list