| 1 |
On 25-04-2008 09:53:41 +0100, Alan Hourihane wrote: |
| 2 |
> On Fri, 2008-04-25 at 10:14 +0200, Fabian Groffen wrote: |
| 3 |
> > On 24-04-2008 23:53:51 +0100, Alan Hourihane wrote: |
| 4 |
> > > Using gcc-config fails compared to what binutils-config does for me. |
| 5 |
> > > |
| 6 |
> > > It turns out that this fails... |
| 7 |
> > > |
| 8 |
> > > env -i portageq envvar CHOST |
| 9 |
> > > |
| 10 |
> > > whereas in binutils-config we just do... |
| 11 |
> > > |
| 12 |
> > > portageq envvar CHOST |
| 13 |
> > > |
| 14 |
> > > Doing the former, gives me.... |
| 15 |
> > > |
| 16 |
> > > env: /root/gentoo/usr/bin/portageq: Invalid executable file format |
| 17 |
> > |
| 18 |
> > Does your /root/gentoo/usr/bin/portageq have an absolute shebang? Mine |
| 19 |
> > does. |
| 20 |
> |
| 21 |
> Yes. |
| 22 |
> |
| 23 |
> > > Is there any reason to use "env -i" ?? |
| 24 |
> > |
| 25 |
> > it cleans the environment, probably for that case to avoid garbage (set |
| 26 |
> > by the user) to influence portageq's output. Must have been a reason |
| 27 |
> > for it at some point. Feels wrong they aren't aligned in |
| 28 |
> > binutils-config and gcc-config, though. |
| 29 |
> |
| 30 |
> Funnily enough. |
| 31 |
> |
| 32 |
> env /root/gentoo/usr/bin/portageq - works |
| 33 |
> env -i /root/gentoo/usr/bin/portageq - Invalid executable file format |
| 34 |
|
| 35 |
I think your platform needs something in the evironment to spawn the |
| 36 |
process. env -i wipes that out. |
| 37 |
|
| 38 |
|
| 39 |
-- |
| 40 |
Fabian Groffen |
| 41 |
Gentoo on a different level |
| 42 |
-- |
| 43 |
gentoo-alt@l.g.o mailing list |
Archives