On Wed, 16 Jan 2002, Jukka Santala wrote:
> The best way to avoid this is probably:
> export PATH=/skiff/local/arm-linux/bin:$PATH
I picked this suggestion up from somewhere else, however a closer look at
what files are in said directory, at least with GCC 3.1 pre, releases
quite few of the binaries are already included in said directory. For the
trivial and maybe some pathological cases (as stated) it works, but any
more complex builds are apt to fail with that definition/path alone. On
the other hand, most configure scripts know to look for arm-linux-* as
well if you're doing a cross-compile, so having /skiff/local/bin in your
path as well catches most of those, I guess. Ofcourse, soon enough the
problem becomes build-scripts that require a native compiler for something
:)
-Jukka Santala
Received on Fri Jan 18 05:02:50 2002
This archive was generated by hypermail 2.1.8 : Tue May 04 2004 - 09:44:22 EDT