Mail Archives: djgpp/1998/06/14/21:15:49
From: | myknees AT aol DOT com (Myknees)
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | Re: Help. I'm cracking up ...
|
Date: | 15 Jun 1998 00:25:02 GMT
|
Lines: | 31
|
Message-ID: | <1998061500250201.UAA29851@ladder01.news.aol.com>
|
NNTP-Posting-Host: | ladder01.news.aol.com
|
References: | <01bd9604$e1a0f6a0$5205e8c3 AT default>
|
Organization: | AOL http://www.aol.com
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
In article <01bd9604$e1a0f6a0$5205e8c3 AT default>, "David Wyn Davies"
<ansawdd AT compuserve DOT com> writes:
>I cannot get GCC to work. At first, I thought it was RHIDE then I
>eventually plucked up the
>courage to try out GCC from the DOS command line and I got the same
>problem. The hard drive starts for a few seconds and then everything hangs
>up.
>
>When I rebooted Windows 95 back into DOS mode and tried it from there, it
>came up with the following error message:
>
>Exiting due to signal SIGSEGV
>
>
>Haven't got a clue what this is. Unless I can get this sorted, I won't be
>able to use DJGPP since the problems happen with every program I try to
>compile.
It is likely an installation problem. Try re-reading the readme.1st file and
the FAQ. Then transcribe the error messages you're getting and search the
djgpp mail archives for keywords in the error message. If you are still having
trouble, post as much relevant info as you can, e.g. your autoexec.bat, your
environment:
set >postme.txt
and the exact text of the errors you're getting.
Good luck! :-)
--Ed (Myknees)
- Raw text -