On Thursday May 11 2017 07:38:01 Ryan Schmidt wrote:
> I will work on it later.
I think you're on the ticket CC list but in case you missed it:
https://trac.macports.org/ticket/53605#comment:8
R.
>> I have been updating gcc7 snapshots weekly and stopped recently when I
>> realized they were preparing for the first release. I did not know they had
>> now done so. I will update the ports once a snapshot of gcc8 is available
>> (probably already is), since gcc6, gcc7 and gcc8 will need to
OK, I'm completely flabbergasted now. The build goes fine WITHOUT my patch so
apparently there is something to it after all that interferes with the build.
It's clearly not a patch that I managed to get to work by applying it *after* a
first successful build completion because it looks like
On Thursday May 11 2017 03:23:31 Ryan Schmidt wrote:
Hi,
>I have not seen that problem building gcc6 before.
Any idea what it could be? Even something silly as having the version already
installed? I don't see how that could influence the parsing behaviour of the
1st bootstrapping compiler
I have not seen that problem building gcc6 before.
I have been updating gcc7 snapshots weekly and stopped recently when I realized
they were preparing for the first release. I did not know they had now done so.
I will update the ports once a snapshot of gcc8 is available (probably already
Hello,
Please excuse the interruption - has anyone else been seeing this error when
trying to build GCC (or possible, libgcc)?
And what about gcc 7, anyone been looking at that? 7.1 is out so there's no
reason port should still be marked experimental...
Thanks,
René
