This is the mail archive of the
mailing list for the GCC project.
Daniel Jacobowitz <firstname.lastname@example.org> writes:
> > 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.
> Have you tried it?
No. I haven't checked the attic for ghosts either.
> I've been testing relocation every release since 3.1, and it does work.
How? If $prefix is /usr/local, then $libdir will be /usr/local/lib,
$libsubdir will be /usr/local/lib/gcc/target/3.4, and $gcc_tooldir
will be /usr/local/lib/gcc/target/3.4/../../../target. If you move
gcc from /usr/local, then /usr/local/lib/gcc/target/3.4/ will not
exist and the entire path will be illegal. How can that work?
How would it work less if $gcc_tooldir was /usr/local/target?