Great thanks.

I’m hopeful that libgcc is going to be OK, but if not please post a full log to 
the PR.

It would be nice if libgcc-devel also built, but this is not so important at 
this point. I had to blacklist gcc-4.2 to get it to build on intel 10.6 (so 
fallback to MPs clang-3.4) but I am not sure what this blacklist will do on 
Darwin 9 PPC. It might try and fallback to a gcc build which will then cause 
problems with a dependency loop. I am hoping instead it also defaults to 
clang-3.4 (or we can convince it to). Its also true that gcc9/libgcc-devel is 
only a snapshot, so things might improve in before a final release (which is 
why right now I don’t think its a big deal).

Chris

> On 29 Jul 2018, at 7:12 pm, Ryan Schmidt <[email protected]> wrote:
> 
> 
> 
> On Jul 29, 2018, at 11:32, Chris Jones wrote:
> 
>> Is there anyone who has a PPC machine running Darwin 9 (OSX 10.5) that would 
>> be willing to run a test of the PR
>> 
>> https://github.com/macports/macports-ports/pull/2296
>> 
>> ? For the reasons outlined in the PR it would be useful to know if the port 
>> libgcc builds properly on this platform. I have tested the rest, 10.6 
>> upwards, but Darwin 9 is one I don’t have access to.
> 
> I'll give it a try!
> 

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to