From: lhall AT rfk DOT com (Larry Hall)
Subject: RE: Bugs with gcc
24 Jan 1997 10:18:25 -0800
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <2.2.32.19970124144908.0091a7b0.cygnus.gnu-win32@ma.ultranet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Sender: lhall AT ma DOT ultranet DOT com
X-Mailer: Windows Eudora Pro Version 2.2 (32)
Original-To: dahms AT ifk20 DOT mach DOT uni-karlsruhe DOT de, D DOT H DOT Akehurst AT ukc DOT ac DOT uk
Original-Cc: gnu-win32 AT cygnus DOT com, dahms AT ifk20 DOT mach DOT uni-karlsruhe DOT de
Original-Sender: owner-gnu-win32 AT cygnus DOT com

At 12:58 AM 1/24/97 EST, dahms AT ifk20 DOT mach DOT uni-karlsruhe DOT de wrote:
>Hi, you wrote:
>
>: firstly, compiling/linking with the -s flag to g++ causes an executable
>: to be produced, that will not run, - apparently a non NT executable.
>
>What do you expect -s to do, please?
>The great thing about gcc/gdb/cygwin is that I can use exactly the same
>commands and switches as on unix, and often also get the same errors and
>warnings, but my (maybe outdated) gcc/g++ man pages (on unix) list no -s.
>Closest thing is -S, but that isn't supposed to create an executable at all.
>
>
>Bye, Heribert (dahms AT ifk20 DOT mach DOT uni-karlsruhe DOT de)

As I remember, -s is an ld flag that is supposed to strip the executable
of symbols (-S being strip debug symbols).  This doesn't produce a valid
executable.  In the past, I believe I heard recommendations to use strip
instead although from recent mail it does sound like there is still an
issue with using strip on DLLs (which should not be a problem for you if
you have an executable).  This is all just stuff I recall from memory and
which I have not tried personally but maybe it will help resolve your
problem.

Larry

-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".