Libgcc: new version won't deactivate the old version

Ryan Schmidt ryandesign at
Sat Dec 5 02:24:53 UTC 2020

On Dec 4, 2020, at 02:58, Christopher Jones wrote:

> On 4 Dec 2020, at 2:36 am, Michael wrote:
>>> --->  Computing dependencies for libgcc
>>> The following dependencies will be installed:  libgcc10
>>> Continue? [Y/n]: y
>>> --->  Activating libgcc10 @10.2.0_3
>>> Error: Failed to activate libgcc10: Image error: /opt/local/include/gcc/c++/algorithm is being used by the active libgcc port.  Please deactivate this port first, or use 'port -f activate libgcc10' to force the activation.
>> Is there a reason that trying to activate the new libgcc does not deactivate the old libgcc?
> That particular message can only occur if you have not updated your ports in a very long time, as the change that made libgcc a stub port happened several years ago now.... If you don’t update regularly you can run into issues like this.
> In this case, just follow the instructions as given and force deactivate.

Well, yes, deactivate libgcc, but do not run the command mentioned in the error message which would force activate libgcc10.

More information about the macports-users mailing list