X-Authentication-Warning:	acp3bf.physik.rwth-aachen.de: broeker owned process doing -bs
Date:	Fri, 12 Nov 1999 16:07:12 +0100 (MET)
From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
X-Sender:	broeker AT acp3bf
To:	DJGPP Workers <djgpp-workers AT delorie DOT com>
Subject:	Re: GCC porting questions
In-Reply-To:	<382C1E95.AE7530D1@softhome.net>
Message-ID:	<Pine.LNX.3.93.991112160453.21722K-100000@acp3bf>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Fri, 12 Nov 1999, Laurynas Biveinis wrote:

> -------
>    in such parts Win95 DPMI server can take. Second reason was to
>    simulate bootstraping gcc which was impossible in other way due to
>    absence of fully functional symbolic links.
> -------
> So, where should I start looking ?

Before that can work, you'ld need *all* the utilities used by configure
and the generated makefiles to know about symlinks. Bash, fileutils,
shellutils, textutils, sed, and make, and may some others I forgot.

> Another question - are changes to DJGPP-specific files in GCC (files
> config/mh-djgpp, gcc/config/djgpp.h etc.) incorporated back into
> mainstream sources ? 

They 'are' not incorporated, in the sense that it would happen
automatically, or so. *You*, as the author, have to contact the GCC
maintainers, and offer your patches. They'll talk you through the details
of the procedure. 

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

- Raw text -