libunwind-headers issue

Ryan Schmidt ryandesign at macports.org
Fri Nov 8 08:42:37 UTC 2019



On Nov 8, 2019, at 02:36, Werner LEMBERG wrote:

> On Mac Lion, installing a fresh MacPorts from scratch, then calling
> 
>  port -N mpkg lilypond-devel +mactex +perl5_28 +python37
> 
> always causes a (harmless) abort.  The reason is that
> `libunwind-headers' gets installed as part of the dependencies rather
> early, but one of the very last steps is installation of `libgcc9',
> which doesn't work with activated `libunwind-headers'.

Yes.

I don't know why anything requires libunwind-headers.

If libunwind-headers is installed, many other ports (not just libgcc9) will fail to build. I wish it didn't exist.

> Is it possible to somehow tell `port' in the above command that
> `libunwind-headers' has to be deactivated before building `libgcc9'?

No.



More information about the macports-users mailing list