Xref:	news-dnh.mv.net comp.os.msdos.djgpp:938
Newsgroups:	comp.os.msdos.djgpp
Path:	news-dnh.mv.net!mv!news.sprintlink.net!dish.news.pipex.net!pipex!newsfeed.internetmci.com!salliemae!uunet!in1.uu.net!psinntp!psinntp!psinntp!psinntp!netrixgw.netrix.com!jasmine!ld
From:	ld AT jasmine DOT netrix DOT com (Long Doan)
Subject:	Re: Bad craziness in STRIP
To:	"A.Appleyard" <A DOT APPLEYARD AT fs2 DOT mt DOT umist DOT ac DOT uk>
Sender:	ld AT jasmine (Long Doan)
Reply-To:	ld AT netrix DOT com
Organization:	Netrix Corporation
References:	<DBv84s DOT 4w3 AT jade DOT mv DOT net>
Date:	Mon, 17 Jul 1995 21:16:59 GMT
Lines:	18
Dj-Gateway:	from newsgroup comp.os.msdos.djgpp

In article <DBv84s DOT 4w3 AT jade DOT mv DOT net>, "A.Appleyard" <A DOT APPLEYARD AT fs2 DOT mt DOT umist DOT ac DOT uk> writes:

[snip]

|> call gcc main.o cc.o em.o display.o macros.o keyf.o -lpc
|> call strip a.out
   ^^^^
   You shouldn't use call to execute a command unless it's a batch
file. My guess is that COMMAND.COM tried to interpret the executable
strip (which is somewhere in you path) as a batch file, and failed.

Instead of doing that, try:

gcc main.o cc.o em.o display.o macros.o keyf.o -lpc
strip a.out

Hope that helps,
Long.

- Raw text -