Sender:	plong AT mbunix DOT mitre DOT org
Message-ID:	<37122C0A.576E290E@mitre.org>
Date:	Mon, 12 Apr 1999 17:23:23 +0000
From:	Philip Long <plong AT mitre DOT org>
X-Mailer:	Mozilla 4.51 [en] (X11; I; Linux 2.2.5 i686)
X-Accept-Language:	ko, en
MIME-Version:	1.0
To:	pgcc AT delorie DOT com
Subject:	Re: Has anyone created a pgcc v1.1.2 RPM?
References:	<Pine DOT LNX DOT 4 DOT 04 DOT 9904121611140 DOT 828-100000 AT atd7 DOT resnet DOT cornell DOT edu>
Reply-To:	pgcc AT delorie DOT com

If you'll look in the SRPMS of  RH/Contrib I modified the same 1.1a for 1.1.1
and compiled it for i686.
Presumably the .spec will still work (very  similar to the 1.1a spec)

Andrew Dodd wrote:

> On Mon, 12 Apr 1999, Steve Snyder wrote:
>
> > I try to keep my RedHat v5.2 system all-RPM to help in keeping track of the
> > installed files.  My brainstorm was to take RedHat's v1.1.2 egcs RPM
> > (egcs-1.1.2-12.src.rpm) and patch it with the pgcc diff, creating a pgcc
> > RPM.
> >
> > Alas, the RedHat patches and the the pgcc patch conflict regardless of
> > order applied to the egcs source files.  Sigh.  Has anyone created a pgcc
> > v1.1.2 RPM yet?
> I might have one in a few days...  I've got a pgcc-1.1.1 RPM that I just
> compiled right now, I'm working on fixing my pgcc-recompiled kernel.  (I
> installed the PGCC kernel patches, the kernel works great, but in
> rebuilding the RPM/SRPM, the sound modules didn't recompile correctly,
> specifically awe_wave.o.  I don't think it's the compiler, I probably just
> goofed.  I'm getting unresolved symbol errors.)
>
> As to how I created the 1.1.1 RPM:
>
> Somewhere (I think it's on RedHat's contrib site), there's an RPM for
> pgcc-1.1a.  I took that and updated the spec for a pgcc-1.1.1 tarball that
> I created from patching an egcs tarball.  I'll do the same for pgcc-1.1.2
> soon.

- Raw text -