Date:	Mon, 8 Mar 1999 17:18:24 -0600 (CST)
From:	Dustin Marquess <jailbird AT alcatraz DOT fdf DOT net>
To:	Jason S <jstelzer AT serve DOT com>
cc:	pgcc AT delorie DOT com
Subject:	Re: Compile errors (sometimes)
In-Reply-To:	<Pine.LNX.4.04.9903081705040.30458-100000@warpath.serve.com>
Message-ID:	<Pine.LNX.4.04.9903081716380.3393-100000@alcatraz.fdf.net>
MIME-Version:	1.0
Reply-To:	pgcc AT delorie DOT com
X-Mailing-List:	pgcc AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Mon, 8 Mar 1999, Jason S wrote:

> Hi, I'm not on the mailing list as of yet. To tell you the truth this is
> the first time I've tried pgcc. To complicate matters I'm not sure if
> this is a pgcc problem, or a code problem in the current cvs tree of
> E and gimp.
> 
> I checked out the cvs version of pgcc today, ran configure and built it.
> To be on the safe side I ran 'make bootstrap' before I clobbered my 
> (working) gcc compiler. All went well. I'm currently building my 2nd 
> kernel of the day with pgcc. The first one built fine. 
> 
> The problem is, when I go to build E ( a number of freinds have built it
> fine with regular gcc) I get various error messages. I get the same sort
> of errors with Gimp also . If I use the default settings, the error is:
> gimp.c: In function `gimp_extension_process':
> gimp.c:1015: Invalid `asm' statement:
> gimp.c:1015: fixed or forbidden register 2 (cx) was spilled for class CREG.
> make[2]: *** [gimp.lo] Error 1
> make[2]: Leaving directory `/home/jstelzer/cvs/gimp/libgimp'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/jstelzer/cvs/gimp'
> make: *** [all-recursive-am] Error 2

	I believe this was answered on the mailing list a couple of
days ago.  The registered spilled message is an egcs thing (and since
pgcc is based on egcs, it gets it too).  Basically in the long shot,
the code needs to be fixed in GIMP.

	The NFS problem... I believe that is fixed in Alan Cox's ac
patches to 2.2.2.  That is a kernel problem :)

					-Dustin

- Raw text -