failed migration to Sequoia

[Joshua Root]

On 21/9/2024 03:36, Artemio González López wrote:
> 
> I just ran port selfupdate, but the only outdated port it found is xorg- 
> libXi  (which I updated). I guess it is not worth to give port restore — 
> last another try, since the problematic por was libgcc14, which hasn’t¡t 
> been updated. Am I right? I would also like to know whether anybody else 
> who, like me, got rid of the c++ directory one way or another (and with 
> an M1 chip) is having the same problem with libgcc14. If this is the 
> case perhaps something else is going on, apart from the rogue c++ 
> directory problem.

A port can only be considered outdated if you have an older version 
installed, so if you have never been able to install any version, it 
will not be shown as outdated. There have definitely been updates to 
libgcc14 in the last several days, so depending on when you previously 
selfupdated, it may now work.

Yes, some users are still having problems with libgcc14 after fixing the 
SDK and the -pipe problem, see the ticket I previously referenced: 
<https://trac.macports.org/ticket/70641> But it seems to be working for 
others.

- Josh