This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: gcc_tooldir


"H. J. Lu" <hjl@lucon.org> writes:

> You can relocate the whole gcc to a different direcory since everything
> is referenced relatively. That is even if you configured gcc with
> --prefix=foo, you can move it "bar" and it should work fine.

That's assuming you're using a relative path as $prefix, which means
that the compiler will only work if your cwd is a particular directory
when you run it.  Doesn't sound very useful.  If you use an absolute
path as prefix, then $(gcc_tooldir) will also be an absolute path, and
moving gcc will not work.


> > So what is the proposed solution?
> > 
> 
> Please follow
> 
> http://gcc.gnu.org/ml/gcc-patches/2000-07/msg00830.html

Rather weak, but better than nothing.  For some reason it seems this
did not make it into CVS though?


  // Marcus



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]