Subject: Re: Bugs with gcc
From: [email-masked] (Aurel Balmosan)

25 Jan 1997 01:14:19 -0800
Approved: [email-masked]
Distribution: cygnus
Message-ID: <[email-masked]>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Original-To: [email-masked]
Original-Cc: [email-masked] (Maillist Cygnus)
In-Reply-To: <[email-masked]> from "[email-masked]" at Jan 24, 97 00:58:11 am
X-Mailer: ELM [version 2.4 PL21]
Content-Length: 952       
Original-Sender: [email-masked]

> 
> 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 ([email-masked])
> -
> For help on using this list, send a message to
> "[email-masked]" with one line of text: "help".
> 

The -s flag is passed to ld and is defined on the man-page for ld
on any UNIX system. So there must be a problem with ld when
stripping a executable. -s means stripping the executable.
It is done directly by ld (no call of strip) 

        Aurel Balmosan
-
For help on using this list, send a message to
"[email-masked]" with one line of text: "help".