From: fjh AT cs DOT mu DOT OZ DOT AU (Fergus Henderson) Subject: Re: Windows API calls that don't work? (Was RE: Stupid stupid question :/) 24 Mar 1997 04:14:32 -0800 Approved: cygnus DOT gnu-win32 AT cygnus DOT com Distribution: cygnus Message-ID: <199703240919.UAA00538.cygnus.gnu-win32@mundook.cs.mu.OZ.AU> Content-Type: text Original-To: colin AT bird DOT fu DOT is DOT saga-u DOT ac DOT jp (Colin Peters) Original-Cc: gnu-win32 AT cygnus DOT com (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: owner-gnu-win32 AT cygnus DOT com 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 | "I have always known that the pursuit WWW: | of excellence is a lethal habit" PGP: finger fjh AT 128 DOT 250 DOT 37 DOT 3 | -- the last words of T. S. Garp. - For help on using this list, send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".