Subject: Re: Windows API calls that don't work? (Was RE: Stupid stupid question :/)
From: [email-masked] (Fergus Henderson)

24 Mar 1997 04:14:32 -0800
Approved: [email-masked]
Distribution: cygnus
Message-ID: <[email-masked]>
Content-Type: text
Original-To: [email-masked] (Colin Peters)
Original-Cc: [email-masked] (gnu-win32)
In-Reply-To: <01BC386B.709FACA0@gbird0> from "Colin Peters" at Mar 24, 97 03:52:54 pm
X-Mailer: ELM [version 2.4 PL24]
Original-Sender: [email-masked]

Colin Peters, you wrote:
> 
> 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? Is there a difference between the -s link option and using
>     strip after linking?

In my experience executables that are not stripped at all work fine.
My experience was that building with the `-s' option on either Windows
95 or NT produced executables that would not run on NT.  There is a
difference between using the `-s' link option and using strip after
linking; in my experience the latter worked on NT, while the former
didn't.

-- 
Fergus Henderson <[email-masked]>   |  "I have always known that the pursuit
WWW: <http://www.cs.mu.oz.au/~fjh>   |  of excellence is a lethal habit"
PGP: finger [email-masked]         |     -- the last words of T. S. Garp.
-
For help on using this list, send a message to
"[email-masked]" with one line of text: "help".