Re: cygwin 64bit on Win7 gcc internal compiler error: Segmentation fault on floating point literal 10.0

2015-11-24 Thread David Standish
Achim, I included cygcheck output in my post Sat, 21 Nov 2015 19:48:45 -0500 as prompted by Ken Brown. The web mailing list indicates it's binary, though it's not. I'll reattach with a .txt extension The processor per cygcheck is PROCESSOR_IDENTIFIER = 'Intel64 Family 6 Model 61 Stepping 4,

Re: cygwin 64bit on Win7 gcc internal compiler error: Segmentation fault on floating point literal 10.0

2015-11-24 Thread Achim Gratz
David Standish writes: > Downgrading to libgmp10-6.0.0a-2 fixes the problem. > Does that imply a problem with to libgmp10-6.0.0a-2 p? At this moment I can't really be sure, there are many systems (including all I have access to) that don't show any problems, so I'm suspecting that it is something

Re: cygwin 64bit on Win7 gcc internal compiler error: Segmentation fault on floating point literal 10.0

2015-11-23 Thread Achim Gratz
David Standish writes: > gcc is broken on fresh install of 64 bit cygwin on 64 bit Win7 > Enterprise on new laptop. > version 4.9.3-1 , but other versions broken as well (4.9.2-3, 5.2.0-1) Does the problem go away if you downgrade to libgmp10-6.0.0a-2 perhaps? Regards, Achim. -- +<[Q+

Re: cygwin 64bit on Win7 gcc internal compiler error: Segmentation fault on floating point literal 10.0

2015-11-23 Thread David Standish
Thanks Achim, Downgrading to libgmp10-6.0.0a-2 fixes the problem. Does that imply a problem with to libgmp10-6.0.0a-2 p? On 11/22/15, Achim Gratz wrote: > David Standish writes: >> gcc is broken on fresh install of 64 bit cygwin on 64 bit Win7 >> Enterprise on new

Re: cygwin 64bit on Win7 gcc internal compiler error: Segmentation fault on floating point literal 10.0

2015-11-22 Thread Ken Brown
On 11/21/2015 7:48 PM, David Standish wrote: Ken, I'm not surprised it works for you. Probably something with my machine. I've attached cygcheck -s -v -r output Sorry, nothing jumps out at me. Maybe someone else will have some ideas. Ken -- Problem reports:

Re: cygwin 64bit on Win7 gcc internal compiler error: Segmentation fault on floating point literal 10.0

2015-11-22 Thread David Standish
Thanks for giving it a look. On 11/22/15, Ken Brown wrote: > On 11/21/2015 7:48 PM, David Standish wrote: >> Ken, I'm not surprised it works for you. Probably something with my >> machine. >> >> I've attached cygcheck -s -v -r output > > Sorry, nothing jumps out at me.

Re: cygwin 64bit on Win7 gcc internal compiler error: Segmentation fault on floating point literal 10.0

2015-11-21 Thread David Standish
Ken, I'm not surprised it works for you. Probably something with my machine. I've attached cygcheck -s -v -r output David cygcheck_s_v_r.out Description: Binary data -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation:

Re: cygwin 64bit on Win7 gcc internal compiler error: Segmentation fault on floating point literal 10.0

2015-11-21 Thread Duncan Roe
On Sat, Nov 21, 2015 at 07:02:50PM -0500, Ken Brown wrote: > On 11/21/2015 3:10 PM, David Standish wrote: > >gcc is broken on fresh install of 64 bit cygwin on 64 bit Win7 > >Enterprise on new laptop. > >version 4.9.3-1 , but other versions broken as well (4.9.2-3, 5.2.0-1) > > > >I suspect there

cygwin 64bit on Win7 gcc internal compiler error: Segmentation fault on floating point literal 10.0

2015-11-21 Thread David Standish
gcc is broken on fresh install of 64 bit cygwin on 64 bit Win7 Enterprise on new laptop. version 4.9.3-1 , but other versions broken as well (4.9.2-3, 5.2.0-1) I suspect there is a straightforward fix to my problem but I have no idea where to begin. Cygwin DLL version info: DLL version:

Re: cygwin 64bit on Win7 gcc internal compiler error: Segmentation fault on floating point literal 10.0

2015-11-21 Thread Ken Brown
On 11/21/2015 3:10 PM, David Standish wrote: gcc is broken on fresh install of 64 bit cygwin on 64 bit Win7 Enterprise on new laptop. version 4.9.3-1 , but other versions broken as well (4.9.2-3, 5.2.0-1) I suspect there is a straightforward fix to my problem but I have no idea where to begin.