[MacPorts] #66024: libgcc10 does not seem to install libgcc_ext.10.x dylibs, leaves gcc7 broken

MacPorts noreply at macports.org
Tue Oct 25 04:40:36 UTC 2022


#66024: libgcc10 does not seem to install libgcc_ext.10.x dylibs, leaves gcc7
broken
---------------------------+----------------------
  Reporter:  barracuda156  |      Owner:  kencu
      Type:  defect        |     Status:  assigned
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.7.2
Resolution:                |   Keywords:
      Port:  libgcc10      |
---------------------------+----------------------

Comment (by barracuda156):

 Replying to [comment:4 kencu]:
 > If and when someone, hopefully not me, actually goes through the project
 of updating systems 10.4 and 10.5 PPC and Intel to a newer libgcc,
 probably libgcc12/gcc12 (built with gcc10-bootstrap), I imagine we will
 arrange things so that none of gcc/libgcc 8,9,10,or 11 are needed.
 >
 > gcc12 will depend on libgcc12. gcc7 will depend on libgcc7. libgcc7 will
 depend on libgcc12. Easy. Anything that exists in libgcc12 that is the
 same, only newer, than what is in libgcc7 will be replaced by the ones in
 libgcc12.
 >
 > For the Intel systems from 10.6 up, this developed organically. Each
 system upgraded to the next one, so it was natural to have all the gccs.
 But in fact, it would be quite simple, and possibly very beneficial, to
 just DELETE gcc 8-11 and libgcc 8-11 on all systems, as they are pretty
 much useless now anyway, and just a maintenance burden for no reason.

 I would keep gcc11 for the time-being. `gcc12` has some issues with PPC,
 as of now.
 (I mean, I understand we are not deleting anything now, but just for the
 record.)

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


More information about the macports-tickets mailing list