Date:	Tue, 17 Apr 2001 09:59:50 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Martin Svensson <bigteddybear AT tjohoo DOT se>
cc:	djgpp AT delorie DOT com
Subject:	Re: help starting up
In-Reply-To:	<200104161939.PAA24150@delorie.com>
Message-ID:	<Pine.SUN.3.91.1010417095931.10552B-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Mon, 16 Apr 2001, Martin Svensson wrote:

> when I run make it can't find cpp0 or something.

Please post the _exact_ error message; ``can't find cpp0 or
something'' doesn't help much.

Also, please add -v to the compiler switches in the Makefile, and post
here everything the compiler prints.

> It is probably becous I don't have any compiler_path in my djgpp.env

This is normal: djgpp.env should not have COMPILER_PATH in it.  GCC
should be able to find all its programs automatically.

> I did move the compiler to the bin directory

The compiler should have been in the bin directory already.

I suspect that you used some too-smart unzip programs (such as WinZip)
to unpack the DJGPP files.  If so, I suggest to remove the entire
DJGPP installation, download the program unzip32.exe from the same
site where you got the *.zip files, and then unzip all the files
again, this time using unzip32.exe.  This will do the Right Thing as
far as the DJGPP directory structure is concerned.

> but I dont know if I
> should do that, I tried to compile allegro but that said something
> about linux ,don't know what I should do.

It's useful to try to compile a short C source file before you build a
complex library such as Allegro.  If compiling a simple program works,
you may be fairly sure your compiler installation is operational.  See
the file README.1ST for some guidance.

- Raw text -