Re: relocating the compiler and associated tools

[Dan Kegel <dank at kegel dot com>]

Robert P. J. Day wrote:
> > >  i then copied all of .../gcc-3.4.1-glibc-2.3.3/ to /usr/local/sh3,
> > > and reset my PATH to instead include /usr/local/sh3/bin.  ran same
> > > test compiles, got the same output.  i realize this doesn't constitute
> > > a rigorous test, but it seems promising.  (once i read more, i'll
> > > probably realize that i didn't need to copy *everything* from that
> > > results directory over to /usr/local/sh3 but better safe than sorry).
> >
> > Well, that depends... did you *copy* everything or did you *move* the tree?
>
>
> "cp -a" since it was in a different filesystem.  is that a problem?

The copied toolchain has hardcoded paths to the old location,
so what you did is no test at all.  You need to rename the
old one so that the hardcoded paths are invalid, and see
if the new copy still works.

And then what if you decide to build a new toolchain in the
original location?  Then when you run the old copied one,
you might get a mix of toolchains.  Thus if you do relocate,
you should definitely build the toolchain in a unique and
unlikely location so that any stray references to the hardcoded
paths are sure to fail.
- Dan

--
Trying to get a job as a c++ developer?  See http://kegel.com/academy/getting-hired.html

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com