Re: still necessary to run "fix-embedded-paths" on created toolchains?

[Dan Kegel <daniel dot r dot kegel at gmail dot com>]

On 12/9/05, Robert P. J. Day <rpjday@mindspring.com> wrote:
>   i was looking at the program fix-embedded-paths.c and was wondering
> if it's still necessary to run that when moving a toolchain to another
> location.  the documentation at the top reads:
>
> "Program to fix embedded paths in files.
> Useful especially for gcc < 3.0 and binutils < 2.14, which
> do not work if you move them after installation;
> running this program fixes the paths and lets the programs work
> again."
>
>   so ... does this mean it *might* not be necessary for newer
> toolchains?  or that it's not clear?  or what?

Newer toolchains are *supposed* to not need it.
There have been scattered reports of the embedded
paths causing problems (on Cygwin, IIRC).
I run it on all my toolchains when building RPMs just to be safe.
(Nevermind the fact that fix-embedded-paths is a risky hack in and of itself :-)
- Dan

--
Why won't Johnny run Linux?  See http://kegel.com/linux/comfort

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