[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: Compiling busybox to .s assembly file
From:       Harald Becker <ralda () gmx ! de>
Date:       2011-02-26 22:32:14
Message-ID: 4D697F6E.3050007 () gmx ! de
[Download RAW message or body]

 Hallo Denys!

>> Amendment: The fake tool chain needs to be placed in /usr/bin due to the
>> fact that the Busybox build clears the Path and does only allow /bin and
>> /usr/bin.
> Where?

Are you asking where Busybox clears the search path? I do not know where
this happens.

Before invoking Busybox make my search path consisted of about 20
directories, including /usr/local/bin. So I placed my fake tool chain in
there, a usual place for local installations ... but make complaint he
is not able to find my-gcc. As this I placed a simple wrapper script
around gcc in /usr/bin:

#!/bin/sh
echo "gcc-wrapper: PATH='$PATH'" >&2
exec /usr/bin/gcc.orig ${1+"$@"}

and got:

gcc-wrapper: PATH='/bin:/usr/bin'

Where that path got set? I don't know! It looks much like the minimum
standard path, so may be the environment got cleared anywhere?

If you want me to look for something to track that down: Let me know, my
current environment allows even complete parallel installation for
testing, without risking to hurt anything.

--
Harald
_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]