This is the mail archive of the
mailing list for the Cygwin project.
Re: Windows API calls that don't work? (Was RE: Stupid stupid question :/)
- To: Colin Peters <colin at bird dot fu dot is dot saga-u dot ac dot jp>
- Subject: Re: Windows API calls that don't work? (Was RE: Stupid stupid question :/)
- From: Chin Chee-Kai <cheekai at gen dot co dot jp>
- Date: Mon, 24 Mar 1997 17:48:11 +0000 (JST)
- Cc: "'A. Phillip Smith'" <asmith at www dot aeinc dot com>, "'GNU-Win32'" <gnu-win32 at cygnus dot com>
I am not sure the talk about "unstripped binaries don't run on
WinNT" is applicable in general.
I've got Mingw32 installed on b17.1 WinNT4.0. But there was
no problem running unstripped or stripped executables. Is your
reference on Win3.51 or a very specific stress-test program?
BTW, stripped *.o files still don't compile up to an executable
(this works on Unix alright). I got:
C:\cygnus\H-i386-..../lib/libcygwin.a(libcmain.o): In function
undefined reference to `WinMain@16'
==> "strip.exe" overstripped.
Chin Chee-Kai (Last, First)
Internet Email-ID: firstname.lastname@example.org
On Mon, 24 Mar 1997, Colin Peters wrote:
> >A. Phillip Smith[SMTP:email@example.com] wrote:
> >This is further complicted on Windows NT by the fact that unless you strip
> >the executable, the binary will not run.
> PS. Any confirmations on that statement about NT from other readers?
> Does stripping an executable make it work? Do you *have* to strip
> on NT?
For help on using this list, send a message to
"firstname.lastname@example.org" with one line of text: "help".