Hi, Hmm, yeah. Now I look at that again its clear the deps are not really right for older systems that do not support all the various gcc versions.
I think the fix is to not explicitly list all the libgcc versions for each older gcc, but just rely on the fact each libgcc port knows what newer libgcc deps it needs. e.g. libgcc6 knows it needs libgcc7, and so on. so change gcc libgcc7 set libgccs "path:lib/libgcc/libgcc_s.1.dylib:libgcc port:libgcc8 port:libgcc7 port:libgcc6” to just set libgccs "path:lib/libgcc/libgcc_s.1.dylib:libgcc port:libgcc6" so on newer systems, the libgcc6 will also implicitly bring in libgcc7, libgcc8, and libgcc9, but on older systems it will stop on the last supported. Chris > set libgccs "path:lib/libgcc/libgcc_s.1.dylib:libgcc port:libgcc8 > port:libgcc7 port:libgcc6 port:libgcc45"On 26 Sep 2019, at 10:04 pm, Joshua > Root <[email protected]> wrote: > > On 2019-9-27 06:01 , Christopher Jones wrote: >> Hi, >> >> From the output it appears cmake has a dependency on both libgcc and >> libgcc8. This is not correct on 10.5. >> >> You should file a ticket against cmake to bring it to the attention of the >> maintainer. > > It's not cmake doing it. The problem is actually this: > <https://github.com/macports/macports-ports/commit/3e21e859b6b935b3413a1c357d39041cdeb03921#diff-4061bdcd5b9dd81cb5a85dccd8def8ab> > > - Josh
smime.p7s
Description: S/MIME cryptographic signature
