Paths to compiler, binutils etc. in 4.5.0 beta 3 build

[Nick.SIMON at syntegra.bt.co.uk]

Thanks, Joel.  At the time I posted, my PATH was correct, but I had first
run configure when it wasn't - it seems that configure remembers certain
things from past runs. Caveat configurator, as they said in the coding shops
of ancient Herculaneum. 


-- Nick Simon 

> -----Original Message-----
> From: Joel Sherrill [mailto:joel.sherrill at OARcorp.com]
> Sent: 17 May 2000 19:05
> To: Nick.SIMON at syntegra.bt.co.uk
> Cc: rtems-users at oarcorp.com
> Subject: Re: Paths to compiler, binutils etc. in 4.5.0 beta 3 build
> 
> 
> Nick.SIMON at syntegra.bt.co.uk wrote:
> > 
> > Chaps,
> > 
> > Having decided it's safe to put beta3 on our main Linux box 
> ('cos the spare
> > PC I've been using is S-L-O-W) I'm now getting all the old 
> tools invoked,
> > from usr/locals/rtems/bin, instead of the shiny new ones from
> > /opt/rtems/bin.
> > 
> > Where do the CC_FOR_TARGET and so on, in the makefiles, 
> come from?  How can
> > I get the 4.5 build to use the new tools without disturbing 
> 4.0 based work?
> 
> During the configure process, they come from your PATH.
> 
> I think you need to adjust your PATH.
> 
> > Thanks In Advance,
> > 
> > -- Nick Simon
> 
> -- 
> Joel Sherrill, Ph.D.             Director of Research & Development
> joel at OARcorp.com                 On-Line Applications Research
> Ask me about RTEMS: a free RTOS  Huntsville AL 35805
>    Support Available             (256) 722-9985
>