Date:	Mon, 6 Jul 1998 14:56:26 +0200 (MET DST)
From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
cc:	DJ Delorie <dj AT delorie DOT com>, djgpp-workers AT delorie DOT com
Subject:	Re: djgpp alpha 980628
In-Reply-To:	<Pine.SUN.3.91.980705154831.23984A-100000@is>
Message-ID:	<Pine.LNX.3.93.980706144844.15155F-100000@acp3bf>
MIME-Version:	1.0

On Sun, 5 Jul 1998, Eli Zaretskii wrote:

> - regcomp.c, regerror.c, engine.c regexec.c trigger numerous warnings.

That's always been the case. The regexp functions are simply not of the
same coding quality as the rest of DJ's libc (they come from outside,
IIRC), and I suspect trying to change them might easily break them. 
They're just too complicated.

> - mkdoc.exe always remakes libc2.tex, and info: always remakes
>   libc.info.  Can't they have real dependencies, so they won't
>   regenerate files which already exist?

I once had a patched makefile set (for alpha 9710* or so) that did this. 
But it was quite a hassle (you have to duplicate the whole mechanism that
does this for the .[cS] sources, like the makefile.oh and so on, to do
it). 

> - The build process expects libgcc.a to be in $(TOP)/../lib.  Patch
>   included to fix this.

gcc-2.8.1 induced problem, I suspect.

> - ../hostbin/dxegen is built as a cross-executable on DOS (the name of
>   `ld' is only good for Unix).  Patch included.

Not sure, but this may be necessary (at least theoretically) to ensure
that all the parts that end up in the '../bin' directory after a rebuild
use newly compiled files only (including a new stub).  Almost-circular
dependency issue is lurking around this corner. 

I do know I spent quite some time thinkig this through to get a workable
solution for both native and cross-builds.

Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -