gcc-2.9x & gcc-3.3x peacfully coinciding?

[Bill Campbell]

On Mon, Jul 07, 2003 at 02:56:59PM -0400, Kurt Wall wrote:
>Quoth Net Llama!:
>> On Mon, 7 Jul 2003, Kurt Wall wrote:
>> >
>> > If you do ./configure, the new one will go into /usr/local and you
>> > won't break anything. To get it used for future builds, invoke the
>> > new GCC using the full path:
>
>[...]
>
>> OK, so how would i control which one gets used by default when i'm , say,
>> rebuilding an SRPM?  I'm guessing that i'd have to edit the SPEC file?
>
>Manipulate your PATH so the new gets found first. Or, hack your
>$HOME/.rpmrc file to find the new compiler - I guess, I don't use
>RPM.

Probably the best way is to manipulate the PATH in the SPEC file so you
don't have to remember to deal with it externally.  If your normal PATH has
/usr/local/bin in PATH after /bin:/usr/bin this will do the trick.

	PATH="/usr/local/bin:$PATH"; export PATH

Better yet, fix the program so it builds properly with the current gcc and
submit the patches back to the maintainers.  This is reasonably easy to do
given the RPM philosophy of building from pristine sources.

Bill
--
INTERNET:   bill at Celestial.COM  Bill Campbell; Celestial Software LLC
UUCP:               camco!bill  PO Box 820; 6641 E. Mercer Way
FAX:            (206) 232-9186  Mercer Island, WA 98040-0820; (206) 236-1676
URL: http://www.celestial.com/

``Most people, sometime in their lives, stumble across truth. Most jump
up, brush themselves off, and hurry on about their business as if
nothing had happened.'' - Sir Winston Churchill