Date: Wed, 15 Nov 1995 19:13:04 -0500
From: dj (DJ Delorie)
To: wstewa AT atl DOT com
Cc: djgpp AT sun DOT soe DOT clarkson DOT edu
Subject: Re: Building djgpp/gcc 2.6.3


>     1) 'touch' command missing.

Oops.  Yup, you need one of those. :-(

>     2) GNU make seems to want to update 'Makefile' which is
>        a dependency of 's-objlist'.  I'm not sure if the DOS
>        port of GNU make sees 'Makefile' and 'makefile' as
>        being different targets/files, but to 'build' Makefile
>        it's trying to do a '/bin/sh config.status' which fails
>        on my PC.  Could this be due to the missing 'more smart
>        shell'?

This is a result of the 'touch' missing, I think.  If not, commenting
out the action for Makefile is the Right Thing.

>     3) If I comment out the action for 'Makefile', it goes on to
>        try to update 's-objlist' by running:
> 
>        echo.exe -o s-objlist <lots of object file names>
> 
>        This command line exceeds the 127 character limit and
>        I can't seem to find an echo.exe that takes a '-o'
>        option.  So I see about 120 characters of '-o s-objlist ...'
>        echoed to the screen and the s-objlist target never
>        gets updated.

echo.exe comes with djgpp, and make *can* give it a command line
longer than 127 characters, if you use the djgpp make.  If not, rename
echo.exe and the makefile entry to something that won't get confused
with command.com's builtin echo.

> Is this even the right 'makefile' to use?
> Has anyone successfully used this 'makefile' to build the gcc
> part of djgpp?  If so, how?

I use it all the time.  Of course, I have a touch program.