Re: Compiling for native Windows

2015-12-14 Thread sisyphus1
-Original Message- From: Ken Brown Sent: Tuesday, December 15, 2015 1:46 PM To: cygwin@cygwin.com Subject: Re: Compiling for native Windows Assuming that gmp supports cross-compiling (which is likely), you can just use the configure option --host=x86_64-w64-mingw32. This will autom

Re: Compiling for native Windows

2015-12-14 Thread Ken Brown
On 12/14/2015 8:14 PM, sisyph...@optusnet.com.au wrote: -Original Message- From: Marco Atzeri Sent: Tuesday, December 15, 2015 1:16 AM To: cygwin@cygwin.com Subject: Re: Compiling for native Windows you need to use the cross compiler package mingw64-x86_64-gcc-core /usr/bin/x86_64-w6

Re: Compiling for native Windows

2015-12-14 Thread sisyphus1
-Original Message- From: Marco Atzeri Sent: Tuesday, December 15, 2015 1:16 AM To: cygwin@cygwin.com Subject: Re: Compiling for native Windows you need to use the cross compiler package mingw64-x86_64-gcc-core /usr/bin/x86_64-w64-mingw32-gcc.exe replaces the old "-mno-cygwin" usage

Re: Compiling for native Windows

2015-12-14 Thread Charles Russell
On 12/14/2015 8:16 AM, Marco Atzeri wrote: On 14/12/2015 15:06, sisyph...@optusnet.com.au wrote: Hi, Last time I built gmp on Cygwin for Windows it was using gcc-3.4.5 - and was, I think, done as a cross-compilation involving the -mno-cygwin option. Am I right in thinking that the days of "-mn

Re: __STRICT_ANSI__ and stdio.h

2015-12-14 Thread KIMURA Masaru
Hi, >> is cygwin's __STRICT_ANSI__ and stdio.h behavior not so compatible to >> glibc's? > > Cygwin is using newlib, newlib is BSD based. We introduced the > compatibility checking macros from FreeBSD lately. i roughly checked FreeBSD include/stdio.h and sys/sys/cdefs.h. https://github.com/free

Re: posix vs. win32 paths (segfault vs. gdb)

2015-12-14 Thread Martin Landa
Hi, 2015-12-10 23:58 GMT+01:00 Warren Young : first of all thanks for the feedback! > Have you read this? > > https://trac.osgeo.org/grass/wiki/CompileOnWindows Yes, some parts of this page has been written by me some years ago:-) Now I came back to establish 64bit workflow. After some playin

Re: How to bring ddrescue up to date?

2015-12-14 Thread Webbed . Pete
Christian wrote: >I will provide ddrescue 1.21 soon after its release. Great! I worked out how to build a new version for myself (but not the test 1.21 versions... how do I make a .sig file?) The new features make a HUGE difference. I can still see some room for improvement, but not much. I

Re: Compiling for native Windows

2015-12-14 Thread Marco Atzeri
On 14/12/2015 15:06, sisyph...@optusnet.com.au wrote: Hi, Last time I built gmp on Cygwin for Windows it was using gcc-3.4.5 - and was, I think, done as a cross-compilation involving the -mno-cygwin option. Am I right in thinking that the days of "-mno-cygwin" have now passed ? If I want to bui

Compiling for native Windows

2015-12-14 Thread sisyphus1
Hi, Last time I built gmp on Cygwin for Windows it was using gcc-3.4.5 - and was, I think, done as a cross-compilation involving the -mno-cygwin option. Am I right in thinking that the days of "-mno-cygwin" have now passed ? If I want to build (say) gmp on Cygwin for Windows, do I still need t

Re: __STRICT_ANSI__ and stdio.h

2015-12-14 Thread Corinna Vinschen
On Dec 12 16:51, KIMURA Masaru wrote: > Hi, > > is cygwin's __STRICT_ANSI__ and stdio.h behavior not so compatible to glibc's? Cygwin is using newlib, newlib is BSD based. We introduced the compatibility checking macros from FreeBSD lately. Corinna -- Corinna Vinschen Please

Re: SegFault running "ls -l" after Microsoft Patch Day

2015-12-14 Thread Corinna Vinschen
On Dec 14 14:04, Dr Rainer Woitok wrote: > Greetings, > > last Wednesday was Windows Patch Day, causing me to install the follow- > ing eighteen patches (the comments ("# ...") reflect what I think the > corresponding knowledge base articles were about): > [...] > After that and after the nece

Re: __STRICT_ANSI__ and stdio.h

2015-12-14 Thread cyg Simple
On 12/13/2015 11:56 PM, KIMURA Masaru wrote: > Hi, > >>> is cygwin's __STRICT_ANSI__ and stdio.h behavior not so compatible to >>> glibc's? >>> especially, i meant routines in POSIX 1003.1:2001 (popen(), pclose(), etc). >>> for a specific example, see a cparser issue[1] i submitted. >>> >> >> Cyg