delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1995/11/20/02:46:34

Date: Mon, 20 Nov 1995 08:02:29 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: George van Venrooij <george AT il DOT ft DOT hse DOT nl>
Cc: djgpp AT sun DOT soe DOT clarkson DOT edu
Subject: Re: Strange re-occurring error.

On 19 Nov 1995, George van Venrooij wrote:

> >Just in case this might help, here's a dump of a gcc -v ...
> >
> >C:\djgpp\Apps>gcc -v -o progie.exe progie.c
> 
> Well, my best guess is that GCC produces a COFF- object-file with the name
> "progie.exe" and then tries to turn in it to a DOS-executable with the name
> "progie.exe". This probably makes stubify get into serious trouble.
> 
> Use the -o switch to define your output object-file name. GCC will convert
> it into an executable for you.
> 
> For example try: gcc -v -o progie.o progie.c

This is just not true!  If the original poster uses DJGPP v1.x, then the 
correct sequence of commands is this:

	gcc -v -o progie progie.c   (note: NOT `-o progie.o'!)
	coff2exe progie

If v2.0 is used, then you can either do this:

	gcc -v -o progie.exe progie.c  (generates progie.exe which can be 
                                        run directly from DOS)

or this:

	gcc -v -o progie progie.c      (generates BOTH progie and progie.exe)

You can indeed run stubify on `progie' which you get in the second case, 
but that's unnecessary, as progie.exe is already created, so you might 
only need it if want to strip the executable without relinking.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019