Date:	Wed, 12 May 1999 10:03:56 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Tokihiro Funakoshi <Kiyokofunakoshi AT email DOT msn DOT com>
cc:	djgpp AT delorie DOT com
Subject:	Re: Re: #include problem
In-Reply-To:	<00b701be9be2$27c6b280$1e4995c1@default>
Message-ID:	<Pine.SUN.3.91.990512100321.20820Q-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Tue, 11 May 1999, Tokihiro Funakoshi wrote:

> Well, here is the contents of my environ.dat:

This seems to be okay.

> The contents of my autoexec.bat is:

Nothing wrong here.

> And the contents of my config.sys is:

Nothing wrong here, either.

> >In addition, add "-v" to the compilation command line,
> > redirect compiler's stderr stream to a file and post here the contents
> > of that file.
> 
> Err.. I don't no what that means

See section 6.14 of the FAQ.  You need to invoke the compiler via the
`redir' utility, like this:

	redir -o compile.log -eo gcc -v -o file.exe file.c

Then post the contents of the file `compile.log'.  It is also a good
idea for you to look at that file, as it might simply tell you enough
to find the cause of the problem.  If not, somebody here will figure
it out.

> OK, and I found it said about go32-v2, so here it is:

This is also okay, except that it seems you are using an old version
2.01 of DJGPP (the current version is 2.02, and 2.03 will be released
soon).

> If youve noticed that I haven't put this up on the newsgoup, its because I
> couldn't find the message you sent me.

Simply cc: your message to <djgpp AT delorie DOT com>, which is the address
of an email gateway into the news group, and your message will be
posted as well.

- Raw text -