--- On Fri, 5/22/09, David Korn <[email protected]> wrote:
> From: David Korn <[email protected]>
> Subject: Re: [uwin-users] where should stdarg.h come from ?
> To: [email protected]
> Date: Friday, May 22, 2009, 5:53 AM
> Subject: Re: [uwin-users] where
> should stdarg.h come from ?
> --------
>
> > I'm trying to compile something with UWIN headers and
> libraries, and
> > the first failure is missing mingw/stdarg.h file - the
> file which
> > includes mingw/stdarg.h is
> >
> > /usr/include/stdarg.h
> >
> > in UWIN.
> >
> >
> > First of all, stdarg.h does _not_ come with modern
> MinGW.
> >
> > Has anybody tried to work with UWIN and any modern
> MinGW ?
> >
> > Anyway, where should I take this file from ?
> >
> > Thanks,
> > Sergei.
> >
>
> We haven't compiled with MinGW for a long time since MSVC
> can be
> freely downloaded.
>
> You can modify /usr/include/stdarg.h to put
>
> #if !defined(__GNUC__)
> #endif
>
> around the file.
>
> If you make changes and are able to compile with a modern
> MinGW send them to us and we will integrate them into the
> source.
>
> David Korn
> [email protected]
I do not quite understand the sense of the proposed workaround.
The __GNUC__ macro is gcc-specific, not MinGW specific. MinGW uses gcc,
So, if I introduce an ifdef or ifndef statement based on __GNUC__, it will
affect all gcc based environments, not only MinGW. Is the goal ?
I do not think so - under Linux stdarg.h exists and in easily includable.
So, why to do this ?
I think that __MINGW32__ macro should be used instead __GNUC__ to identify
compilation under MinGW gcc. Something along the following piece:
http://www.eldos.com/forum/read.php?FID=9&TID=1473&MID=8157#message8157 :
void MCMMFSenderThread::SendMessage(void)
{
MCMessageInfo* Info;
#if defined(__GNUC__) && !(defined(__MINGW32__) || defined(__MINGW64__))
MCEvent *RFreeMutex, *RReplyEvent, *RRequestEvent, *RReceiptEvent;
int RMMF;
#else
//$ifndef LINUX
MCHandle HandleArray[2];
MCHandle RFreeMutex, RReplyEvent, RRequestEvent, RReceiptEvent;
MCHandle RMMF;
//$endif
#endif
...
Reliance on MSVC deserves a separate thread.
Thanks,
Sergei.
_______________________________________________
uwin-users mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/uwin-users
