>
> Clever!
>
> One question of mine which did not get answered: "Q: why are ports like
> fftw-3 reported as dependents of port libgcc-devel? I don't see anything in
> fftw-3's portfile[2] which mentions port libgcc-devel, or indeed any gcc or
> libgcc, are dependencies.
>
> "I suspect
Ken:
Thank you for your explanation. I can imagine this is how my ports
collection came to include gcc-devel/libgcc-devel.
On 2023-10-17 00:36, Ken Cunningham wrote:
There was a time when the only version of gcc that built on arm64 was
gcc-devel/libgcc-devel. So ports put a specific
There was a time when the only version of gcc that built on arm64 was
gcc-devel/libgcc-devel. So ports put a specific dependency on that on arm. This
was a long time ago now. It got things built.
Then various gcc versions came out, gcc-12, gcc-13 that would build on arm64
(with extra patches,
Hi folks:
My "port upgrade outdated" commands were being blocked for a couple of
weeks because a) port libgcc-devel was failing to build (see ticket
#68421 [1]), and b) several ports were dependents of libgcc-devel for
reasons I don't understand, and c) I had port libgcc-devel and not port
