On 25-04-2008 09:53:41 +0100, Alan Hourihane wrote: > On Fri, 2008-04-25 at 10:14 +0200, Fabian Groffen wrote: > > On 24-04-2008 23:53:51 +0100, Alan Hourihane wrote: > > > Using gcc-config fails compared to what binutils-config does for me. > > > > > > It turns out that this fails... > > > > > > env -i portageq envvar CHOST > > > > > > whereas in binutils-config we just do... > > > > > > portageq envvar CHOST > > > > > > Doing the former, gives me.... > > > > > > env: /root/gentoo/usr/bin/portageq: Invalid executable file format > > > > Does your /root/gentoo/usr/bin/portageq have an absolute shebang? Mine > > does. > > Yes. > > > > Is there any reason to use "env -i" ?? > > > > it cleans the environment, probably for that case to avoid garbage (set > > by the user) to influence portageq's output. Must have been a reason > > for it at some point. Feels wrong they aren't aligned in > > binutils-config and gcc-config, though. > > Funnily enough. > > env /root/gentoo/usr/bin/portageq - works > env -i /root/gentoo/usr/bin/portageq - Invalid executable file format
I think your platform needs something in the evironment to spawn the process. env -i wipes that out. -- Fabian Groffen Gentoo on a different level -- [email protected] mailing list
