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