Date: Wed, 5 Aug 1998 10:00:42 +0200 (WET)
From: Andris Pavenis <pavenis AT lanet DOT lv>
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
cc: djgpp-workers AT delorie DOT com
Subject: Re: One more problem with newest MAKE
In-Reply-To: <Pine.SUN.3.91.980805093626.11089G-100000@is>
Message-ID: <Pine.A32.3.91.980805095111.45814B-100000@ieva01.lanet.lv>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk

y

On Wed, 5 Aug 1998, Eli Zaretskii wrote:

> 
> On Tue, 4 Aug 1998, Andris Pavenis wrote:
> 
> > So the conclusion is that one MUST use djdev202 to build 
> > make-3.77
> 
> I'm not sure.  I did NOT use djdev202 to build my binary.  I used a
> patched v2.01 libc, and I cannot reproduce the problem.
> 
> Please try to find out which function(s) that were changed since v2.01
> release cause the problem.  I cannot upload Make 3.77 if it can only
> be built with a library which isn't even in beta testing yet.  If some
> functions in stock v2.01 cause this bug, I will include their patched
> versions in the source distribution, so that Make could be built with
> v2.01 as well.
> 

I don't know internals of make well enough. Also perhaps too much functions
has changed from 201 to 202. I even has to delete config.cache and
run configure once more to be able to build make when I changed from
2.01 to 2.02.

One of ideas could be to try building make with not patched 201.
If this triggers this bug then perhaps You patched libc somewere more
than I did. I also used gcc-2.8.1 both when building under DOS and
when crossbuilding under Linux. 

One more idea would be to upload make archives for DJGPP to v2/alphas.
I don't see anything bad from releasing alpha version of port. Then
I would be able to test also Your build.

Andris