This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Porting to 64 bit Cygwin (was Re: Difference in 32/64-bit curl.)
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 25 Apr 2013 11:57:37 +0200
- Subject: Re: Porting to 64 bit Cygwin (was Re: Difference in 32/64-bit curl.)
- References: <51766C22 dot 10702 at bahnhof dot se> <51770372 dot 4070408 at t-online dot de> <20130424125930 dot GQ26397 at calimero dot vinschen dot de> <20130424134749 dot GR26397 at calimero dot vinschen dot de> <517803D9 dot 3060504 at t-online dot de> <20130424174401 dot GY26397 at calimero dot vinschen dot de> <51783547 dot 9010002 at t-online dot de>
- Reply-to: cygwin at cygwin dot com
On Apr 24 21:40, Christian Franke wrote:
> Corinna Vinschen wrote:
> >>- DON'T forget to add casts if such Win32 API types are used with
> >>printf(). This:
> >>
> >> printf("Win32 Error=%lu\n", GetLastError());
> >>
> >>worked for all i686 and Windows x86_64, but fails now on Cygwin x86_64.
> >I skipped that because the FAQ entry is not exactly what I wrote in my
> >mail. Do you still think this is necessary?
>
> No - these cases would be reported by compiler if -W[error=]format
> is enabled.
>
> Yes - the knowledge that there is no portable way to pass DWORD,
> LONG, ... to printf() without a cast might help to write correct
> code without test builds on all platforms :-)
I extended the FAQ entry and added two more:
http://cygwin.com/faq-nochunks.html#faq.programming.64bitporting
http://cygwin.com/faq-nochunks.html#faq.programming.64bitporting-fail
http://cygwin.com/faq-nochunks.html#faq.programming.64bitporting-cygwin64
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple