[MacPorts] #54149: gcc6 fails to compile because "configure: error: cannot compute sizeof (long long)"

[Ryan Schmidt]

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 is), since gcc6, gcc7 and gcc8 will need to be updated at the same time to move the libgcc subports around. 

> On May 11, 2017, at 02:18, René J.V. Bertin <rjvbertin at gmail.com> wrote:
> 
> 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é
> 
> -------------------------------
> Forwarded message:
> Subject: [MacPorts] #54149: gcc6 fails to compile because "configure: error: cannot compute sizeof (long long)"
> 
> 
> #54149: gcc6 fails to compile because "configure: error: cannot compute sizeof
> (long long)"
> --------------------+------------------
> Reporter:  RJVB    |      Owner:
>     Type:  defect  |     Status:  new
> Priority:  Normal  |  Milestone:
> Component:  ports   |    Version:
> Keywords:          |       Port:  gcc6
> --------------------+------------------
> Back in february I successfully built port:gcc6 with a tiny patch that
> makes G++ use libc++ and thus become a proper citizen on OS X 10.9 and
> later.
> 
> Today I wanted to build a slightly improved version and find my builds
> fail no matter what I try because the bootstrapped gcc compiler (xgcc)
> chokes on the configure test to determine the sizeof(long long).
> 
> Googling the error suggests that this has to do with the presence (or not)
> of the GNU binutils - which I don't have and didn't have either back in
> February.
> 
> The only seemingly relevant port I updated since then is ld64_latest, but
> re-activating the version I had back then makes no difference. My patch
> cannot be the culprit either because it affects only the C++ compiler,
> which isn't used during the GCC build.
> 
> Any ideas?
> 
> --
> Ticket URL: <https://trac.macports.org/ticket/54149>
> MacPorts <https://www.macports.org/>
> Ports system for macOS