Hi. Another example for a command that tries to be too clever. I wrote a wrapper that looks in different places for the "gcc" command. The first one it finds is used. It looks for $opkg_root/bin/gcc /usr/local/bin/gcc /opt/sfw/bin/gcc
But the builds are executed with an "env -i" which ignores the current environment. So "$opkg_root" was not set and everything was compiled with the "wrong" compiler. Especially nasty when one messes around with the frigging gcc-specs and wonders, why there is _no_ effect. The old "you're just calling a complete other command than you think, dude"- scenario :) No complaint. Just to mention it (the "env -i" fact). I think it is nice to know. (mk) PS: This way i personally like "lesspipe" much better: #!/bin/sh exec lesspipe "$1" | $PAGER -- Matthias Kurz; Fuldastr. 3; D-28199 Bremen; VOICE +49 421 53 600 47 >> Im pr�motorischen Cortex kann jeder ein Held sein. (bdw) << ______________________________________________________________________ The OpenPKG Project www.openpkg.org Developer Communication List [EMAIL PROTECTED]
