To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	Re: Trying to compile new gcc, part 2
Reply-To:	dmb AT ai DOT mit DOT edu
Date:	Sat, 10 Jul 93 11:31:24 -0400
From:	David Baggett <dmb AT xbar DOT ai DOT mit DOT edu>

Grzegorz B. Mazur <gbm AT ii DOT pw DOT edu DOT pl> writes:

>Having no idea about configuring gcc with its unix filenames and behaviors,
>I send a mail to djgpp list. After two hours I received the mail from DJ
>with some basic instructions and suggestion that all the info I need is 
>included in FAQ file. Unfortunately this was false...

I just went through a round of the same kind of frustration.  Almost
all of my problems with the build came from the fact that I was running
4DOS.  The configur.bat file won't work under 4DOS, because 4DOS is
brain-damaged in the way it handles quoting.  I think there's no
hope of massaging the file to work with 4DOS because of this.

The solution is to make a DOS boot-disk and run the configur.bat script
on a clean system, then reboot and run the rest of the process as usual.

Ndmake is also fairly flaky.  An extraneous double quote in the
generated makefile (my fault) caused ndmake to repeatedly lock up the
system.  So take care that if you edit the makefile by hand you do it
right.

Also, there is a file called "move-if-change" which got truncated
improperly on my system.  (This is because I used zoo to archive the
sources before downloading them.)  That file must be called "move-if-"
if ndmake is going to recognize it properly.

Finally, make sure that you have enough swap space.  I have 8M of RAM
and 2M of swap space wasn't enough to compile parts of the C++
compiler.

Dave Baggett

- Raw text -