Jim Wilson wrote:
Moving trees around has worked for a long time, but it required
manually setting the GCC_EXEC_PREFIX environment variable.
Cygnus got this working reliably sometime in the early '90s I think.
In gcc-3.0 and later, there is code (make_relative_prefix) that
computes and sets G
Dan Kegel wrote:
Moving an installed gcc/glibc crosstoolchain
to a different directory was not allowed
for gcc-2.96 and below, I seem to recall,
but became permissible around gcc-3.0.
Moving trees around has worked for a long time, but it required manually
setting the GCC_EXEC_PREFIX environment v
Daniel Jacobowitz wrote:
On Tue, Mar 29, 2005 at 10:37:33PM -0800, Dan Kegel wrote:
Since I need to handle old versions of gcc, I'm
going to code up a little program to fix all
the embedded paths anyway, but I was surprised
by the paths in the pch file. Guess I shouldn't
have been, but now I'm a
On Tue, Mar 29, 2005 at 10:37:33PM -0800, Dan Kegel wrote:
> Since I need to handle old versions of gcc, I'm
> going to code up a little program to fix all
> the embedded paths anyway, but I was surprised
> by the paths in the pch file. Guess I shouldn't
> have been, but now I'm a little less conf
On 2005-03-30, at 08:37, Dan Kegel wrote:
Since I need to handle old versions of gcc, I'm
going to code up a little program to fix all
the embedded paths anyway, but I was surprised
by the paths in the pch file. Guess I shouldn't
have been, but now I'm a little less confident
that this will work.
Moving an installed gcc/glibc crosstoolchain
to a different directory was not allowed
for gcc-2.96 and below, I seem to recall,
but became permissible around gcc-3.0.
(Sure, there are still embedded paths,
but they don't seem to be used in practice.
I don't really trust it, but that's what I observ
