From: j DOT aldrich6 AT genie DOT com
Message-Id: <199607230252.AA001400321@relay1.geis.com>
Date: Tue, 23 Jul 96 02:34:00 UTC 0000
To: pengzh AT ix DOT netcom DOT com
Cc: djgpp AT delorie DOT com
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
Subject: Re: Crash after running...??

Reply to message 1689118    from PENGZH AT IX DOT NET on 07/22/96  6:48PM


>    I've been expriencing some thing like this:  After the compilation,
>the a.out is produced.  Are you suppose to convert it using coff2exe?
>or stubify?  Any way, after converting it, I tried to make it run.  But
>it crashes living windows with a message like illegal operation and
>have to restart dos again.  The executable runs OK with go32, but not
>without.  What is wrong????

Okay...

First, it's much easier on the mind and soul to simply specify the name
of the output file you want with the -o option, i.e.:

gcc -o foo foo.c

That gives you 'foo', not 'a.out'.  It also gives you 'foo.exe', if you are
using DJGPP v2, so you shouldn't need to run stubify at all.  If you are
using an older version like v1.*, you simply need to run 'coff2exe' on
'foo'.  This gives you an executable that can be run as long as you
have 'go32' somewhere in the path.  For maximum portability, use
DOS copy to prepend go32.exe to the 'foo' image.  (Instructions
are in the readme.1st of the v1.* distribution.)

However, all these things are completely obsolete with the release
of DJGPP v2, which I suggest you obtain as rapidly as possible.  :)
Go to any simtel mirror, such as ftp.simtel.net, and look in the
pub/simtelnet/gnu/djgpp/v2* directories.  Download the 'readme.1st'
file to find out what to download and how to install it, and then proceed
from there.  I HIGHLY recommend that you get the FAQ (faq201b.zip)
and read at least the sections pertaining to the differences between
v1.* and v2.

If I'm mistaken, and you already have v2, then you are obviously
doing something wrong when you compile.  Add -v to your gcc
command line and post everything it prints here on the newsgroup.
(Hint:  use the 'redir' program to capture gcc's output.)  And I still
recommend that you read the FAQ.  :)

John