From: pavenis AT lanet DOT lv
To: Maurice Lombardi <Maurice DOT Lombardi AT ujf-grenoble DOT fr>, djgpp AT delorie DOT com
Date: Mon, 25 Sep 2000 17:47:56 +0200
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Subject: Re: ANNOUNCE: Binutils 2.10 update #2
Message-ID: <39CF8FCC.1346.AA574F@localhost>
In-reply-to: <39CB236B.B046C9FC@ujf-grenoble.fr>
X-mailer: Pegasus Mail for Win32 (v3.12c)
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from Quoted-printable to 8bit by delorie.com id OAD09473
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On 22 Sep 2000, at 11:16, Maurice Lombardi wrote:

> Andris Pavenis a écrit :
> > 
> > Ather possible workarounds:
> >         - for gcc only: we could try building DJGPP port of gcc with
> >           Canadian-cross type build for example under Linux. I myself
> >           am using gcc-2.95.2 binaries for DJGPP I build such way in
> >           end of March. In this way we could avoid such M$ bugs
> 
> This is what was done previously by GNU pascal maintainers which work under
> linux. But releasing djgpp binaries with each daily gpc snapshot would be much
> trouble for them. I have no Linux machine at hand, but with the work around
> indicated in my original post, I can download and build natively the pascal
> compiler alone each time I want to.
> 

I don't think, it's so hard. It's simply question of writting related scripts 
for building at first linux-to-djgpp cross-compiler and after that native 
compiler under Linux (using freshly built cross-compiler). After that all 
this stuff can be run from cron task ...

Andris