On Saturday 25 August 2007 05:33, NightStrike wrote:
> On 8/24/07, Georg Nikodym <
georgn@...> wrote:
> > > Compiled with mingw's gcc (3.4.5) and run inside an MSYS bash, it
> > > operates almost as expected (the umask() and chmod() calls don't
> > > quite act the way a UNIX hand like myself would expect).
> > >
> > > However, run under a cygwin shell, I see:
> > >
> > > georgn@up /tmp
> > > $ ./temp; ls -l foo bar baz
> > > mode = 0
> > > ----------+ 1 georgn None 0 Aug 24 13:50 bar
> > > ----------+ 1 georgn None 0 Aug 24 13:50 baz
> > > ----------+ 1 georgn None 0 Aug 24 13:50 foo
> > >
> > > georgn@up /tmp
> > > $
>
> Can you just compile it for cygwin? Use i686-pc-cygwin-gcc.exe
That seems to miss the point entirely. If compiled *for* Cygwin, then
the end user needs to *have* Cygwin; if compiled with the MinGW suite,
then it's a native Woe32 application, and the end user just needs a
perfectly ordinary Woe32 system.
Cygwin is *supposed* to be able to run native Woe32 applications; in the
example given, it doesn't do so properly. That's a Cygwin problem, not
a MinGW issue.
Regards,
Keith.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>
http://get.splunk.com/_______________________________________________
MinGW-users mailing list
MinGW-users@...
You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users
