X-Authentication-Warning: ieva01.lanet.lv: pavenis owned process doing -bs
Date: Fri, 1 Oct 1999 09:45:58 +0300 (WET)
From: Andris Pavenis <pavenis AT lanet DOT lv>
To: Rodimus Prime <rodimus AT micoks DOT net>
cc: djgpp AT delorie DOT com
Subject: Re: A Thought, maybe a request...
In-Reply-To: <000001bf0bc8$97a37560$306f99d1@cybertron>
Message-ID: <Pine.A41.4.05.9910010938020.48740-100000@ieva01.lanet.lv>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk



On Thu, 30 Sep 1999, Rodimus Prime wrote:

> 
> 
> I've been trying to build a copy of PGCC for quite a while now.
> 
> I'd like to try to build a copy of PGCC 2.951 from your instructions...
> 
> I'm sure there are going to be some 'gotchas' though..

If You really want this, then get v2gnu/gcc2951s2.zip from DJGPP
distribution, libg++-2.8.1.3, gcc-2.95.1 and corresponding pgcc
patch;

apply pgcc patch to gcc and put libg++ sources into gcc tree;

use scripts from gcc2951s2.zip to modify sources for DJGPP and build
pgcc after that. I have heard that it works, but I don't have plans to do
it myself in nearest future. 

Andris

PS. But think whether You really need it. Perhaps You'll get some
improvement in speed of generated code, but You'll rather certainly lose
in stability. Last time I tried pgcc (it was pgcc-1.1.1) I was not able to
compile BYTE benchmarks with it to do some comparisson.
 

> 
> Could you either:
> 
> 1)  Help me through doing this via patching the DJGPP source and seeing what
> falls through the cracks with me..
> 
> or
> 
> 2)  Help me repatch the source AFTER patching the original GCC source,
> whichever is easier.
> 
> or
> 
> 3)  Do it for me and save me some major headaches :)
> 
> Bud Crittenden
> Rodimus Prime
> rodimus AT onramp DOT micoks DOT net
> http://onramp.micoks.net/~rodimus
> 
>