Message-ID: <399F7618.ED2DE243@hotmail.com>
From: the Icefalcon <kourino AT hotmail DOT com>
Organization: Harumichi Otaku ... doko ni mo!
X-Mailer: Mozilla 4.05 [en] (Win95; U)
MIME-Version: 1.0
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Fun with make and glibc
References: <399EC6ED DOT 5C058F8D AT hotmail DOT com> <8011-Sat19Aug2000211835+0300-eliz AT is DOT elta DOT co DOT il> <399EF0ED DOT 9C55D71A AT hotmail DOT com> <7458-Sun20Aug2000082724+0300-eliz AT is DOT elta DOT co DOT il>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 71
Date: Sun, 20 Aug 2000 06:02:42 GMT
NNTP-Posting-Host: 12.85.129.148
X-Complaints-To: abuse AT worldnet DOT att DOT net
X-Trace: bgtnsc05-news.ops.worldnet.att.net 966751362 12.85.129.148 (Sun, 20 Aug 2000 06:02:42 GMT)
NNTP-Posting-Date: Sun, 20 Aug 2000 06:02:42 GMT
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Eli Zaretskii wrote:
> 
> > From: the Icefalcon <kourino AT hotmail DOT com>
> > Newsgroups: comp.os.msdos.djgpp
> > Date: Sat, 19 Aug 2000 20:34:35 GMT
> > >
> > > Obviously, you need to install GNU Sh-utils (which will get you
> > > echo.exe that can handle this command).  The error message you see
> > > comes from COMMAND.COM's internal ECHO, which is too dumb.
> >
> > Actually, I have :) But, since bash is so "nice" about passing stuff
> > to DOS, it defaulted to DOS' echo instead of the one in /bin.
> 
> This cannot be true, unless you have a very old port of Make and/or
> Bash.

3.79 ^^; And as the bash prompts reveal, it's 2.03. Yes, I just went to
the main DJGPP ftp and downloaded them from the v2gnu directory.

> Does the Makefile say "SHELL = /bin/sh" somewhere?  If not, this is
> your problem.

I don't believe it does. Thanks.

> Also, make sure the directory where you have all the utilities,
> including Bash, is on your PATH, 

I set that manually every time because I haven't gotten around to doing
it in autoexec.bat. I'm never actually in \bin when I start bash ...

> and that you have a sh.exe in that directory.

Yep, it was that way in the .tar file. That is, there was both bash.exe
and sh.exe in the .tar file.

> > bash-2.03$ make
> > Makefile:134: *** missing separator (did you mean TAB instead of 8
> > spaces?).  Stop.
> > bash-2.03$
> >
> > Der .. line 134 of Makefile is:
> >
> > all-Subdirs-files = $(wildcard $(addsuffix /Subdirs, $(config-sysdirs)))
> 
> This doesn't help at all, since you didn't say what $(config-sysdirs)
> expands into.

Well, it's a long line, but here, from config.make:

config-sysdirs =  sysdeps/standalone/i386 sysdeps/standalone
sysdeps/i386/fpu sysdeps/libm-i387 sysdeps/i386 sysdeps/wordsize-32
sysdeps/ieee754 sysdeps/libm-ieee754 sysdeps/generic sysdeps/stub

> > Oh, I went and changed the necessary "echo" statements in configure too.
> > Didn't seem to make a difference.
> 
> It shouldn't.  I suggest to stop these random changes, since you can
> easily break the scripts like that.

Yes @_@ I worry about that with code/documents I didn't write myself. I
back up the old version without fail if I feel I have to change
something
to get it to work. (Although, I greatly prefer not to change things
thus.)

Eeh ... well, with your suggestion (adding a SHELL= line) that echo bug
went away when I restored the original version. (Leaving the separator
error ... )
-- 

                                             -|-E the Icefalcon