X-Authentication-Warning: atd7.resnet.cornell.edu: atd7 owned process doing -bs Date: Mon, 12 Apr 1999 16:15:26 -0400 (EDT) From: Andrew Dodd X-Sender: atd7 AT atd7 DOT resnet DOT cornell DOT edu To: PGCC Mailing List Subject: Re: Has anyone created a pgcc v1.1.2 RPM? In-Reply-To: <199904121539.KAA26582@indy1.indy.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: pgcc AT delorie DOT com X-Mailing-List: pgcc AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk 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.