Re: MacPorts 2.6 - Leopard 20.6 and libgcc8

> On 27 Sep 2019, at 12:50 am, Ken Cunningham > wrote: > > If we’re talking about a 2.6.1, please look at incorporating this 10.6.8 fix > The best way to achieve that I guess would be to open a second PR that cherry picks the commit,

Re: MacPorts 2.6 - Leopard 20.6 and libgcc8

If we’re talking about a 2.6.1, please look at incorporating this 10.6.8 fix > thanks Ken

Re: MacPorts 2.6 - Leopard 20.6 and libgcc8

> On 27 Sep 2019, at 12:39 am, Chris Jones wrote: > >  > > >>> On 27 Sep 2019, at 12:34 am, Ryan Schmidt wrote: >>> >>  >> >>> On Sep 26, 2019, at 18:28, Riccardo Mottola wrote: >>> >>> Hi, >>> >>> Ryan Schmidt wrote: > I suppose this is an important fix for 10.5 user, we soon

Re: MacPorts 2.6 - Leopard 20.6 and libgcc8

> On 27 Sep 2019, at 12:34 am, Ryan Schmidt wrote: > >  > >> On Sep 26, 2019, at 18:28, Riccardo Mottola wrote: >> >> Hi, >> >> Ryan Schmidt wrote: I suppose this is an important fix for 10.5 user, we soon need a 2.6.1 >>> The list of compiler dependencies is kept in 2 places: in the

Re: MacPorts 2.6 - Leopard 20.6 and libgcc8

On Sep 26, 2019, at 18:28, Riccardo Mottola wrote: > Hi, > > Ryan Schmidt wrote: >>> I suppose this is an important fix for 10.5 user, we soon need a 2.6.1 >> The list of compiler dependencies is kept in 2 places: in the ports tree, >> and also in MacPorts base. Chris updated both to fix

Re: MacPorts 2.6 - Leopard 20.6 and libgcc8

> On 27 Sep 2019, at 12:29 am, Riccardo Mottola > wrote: > > Hi, > > Ryan Schmidt wrote: >>> I suppose this is an important fix for 10.5 user, we soon need a 2.6.1 >> The list of compiler dependencies is kept in 2 places: in the ports tree, >> and also in MacPorts base. Chris updated both

Re: MacPorts 2.6 - Leopard 20.6 and libgcc8

Hi, Ryan Schmidt wrote: I suppose this is an important fix for 10.5 user, we soon need a 2.6.1 The list of compiler dependencies is kept in 2 places: in the ports tree, and also in MacPorts base. Chris updated both to fix this issue. The list in MacPorts base only comes into effect if the

Re: MacPorts 2.6 - Leopard 20.6 and libgcc8

On Sep 26, 2019, at 18:12, Riccardo Mottola wrote: > Chris Jones wrote: >> https://github.com/macports/macports-ports/commit/2e46a05404462e04930b612ed29d9f08ece64603 >> >> I have no way though to test the logic on an OS as ancient as 10.5 > > I patched the file locally in my macports

Re: MacPorts 2.6 - Leopard 20.6 and libgcc8

> On 27 Sep 2019, at 12:13 am, Riccardo Mottola > wrote: > > Hi! > > Chris Jones wrote: >> https://github.com/macports/macports-ports/commit/2e46a05404462e04930b612ed29d9f08ece64603 >> >> I have no way though to test the logic on an OS as ancient as 10.5 > > I patched the file

Re: MacPorts 2.6 - Leopard 20.6 and libgcc8

Hi! Chris Jones wrote: https://github.com/macports/macports-ports/commit/2e46a05404462e04930b612ed29d9f08ece64603 I have no way though to test the logic on an OS as ancient as 10.5 I patched the file locally in my macports then rerun build of harfbuzz and the dependency issue is

Re: MacPorts 2.6 - Leopard 20.6 and libgcc8

https://github.com/macports/macports-ports/commit/2e46a05404462e04930b612ed29d9f08ece64603 I have no way though to test the logic on an OS as ancient as 10.5 > On 26 Sep 2019, at 10:31 pm, Christopher Jones > wrote: > > Hi, > > Hmm, yeah. Now I look at that again its clear the deps are

Re: MacPorts 2.6 - Leopard 20.6 and libgcc8

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

Re: MacPorts 2.6 - Leopard 20.6 and libgcc8

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

Re: MacPorts 2.6 - Leopard 20.6 and libgcc8

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. Chris > On 26 Sep 2019, at 8:54 pm, Riccardo Mottola > wrote: > > Hi, > > Joshua Root

Re: MacPorts 2.6 - Leopard 20.6 and libgcc8

Hi, Joshua Root wrote: Actually it looks like that's not the case on Leopard. Could you show the 'port rdeps' output for whatever you're trying to build? it shows both versions of libgcc I appear to have only one outdated port, harfbuzz, this is the tree: The following ports are

Re: MacPorts 2.6 - Leopard 20.6 and libgcc8

what OS is that on ? yes, on 10.6 and newer I would expect to see that, but on 10.5 it shouldn't be the case. Chris i.e. see line 43 in https://github.com/macports/macports-ports/blob/master/lang/gcc7/Portfile and then line 216. The depends_run on libgcc8 is only set for Darwin 10 or

Re: MacPorts 2.6 - Leopard 20.6 and libgcc8

On 2019-9-25 18:31 , Riccardo Mottola wrote: > Hi, > > Joshua Root wrote: >> Chris Jones wrote: >>> Indeed, gcc8 is not supported on 10.5 or older, and likely will never >>> be. >>> >>> What is requiring you to use libgcc8 ? >> libgcc7, apparently: >> >> % port deps libgcc7 >> Full Name: libgcc7

Re: MacPorts 2.6 - Leopard 20.6 and libgcc8

On 25/09/2019 7:55 am, Joshua Root wrote: (forgot to include the list on first sending, apologies for duplicate message) Chris Jones wrote: Indeed, gcc8 is not supported on 10.5 or older, and likely will never be. What is requiring you to use libgcc8 ? libgcc7, apparently: % port deps

Re: MacPorts 2.6 - Leopard 20.6 and libgcc8

(forgot to include the list on first sending, apologies for duplicate message) Chris Jones wrote: > Indeed, gcc8 is not supported on 10.5 or older, and likely will never be. > > What is requiring you to use libgcc8 ? libgcc7, apparently: % port deps libgcc7 Full Name: libgcc7 @7.4.0_3 Extract

Re: MacPorts 2.6 - Leopard 20.6 and libgcc8

Hi, Indeed, gcc8 is not supported on 10.5 or older, and likely will never be. What is requiring you to use libgcc8 ? You should instead be using libgcc7 on that platform. Note this is what the libgcc port is there for, to set up this dependency correctly.