1 |
I am currently working on an ebuild for gwc (gnome wave cleaner). |
2 |
I've done about 20 ebuilds before, but this time I've run into |
3 |
something new. When I run: |
4 |
|
5 |
# ebuild /usr/local/portage/media-sound/gwc/gwc-0.17.4.ebuild compile |
6 |
|
7 |
the compile fails. |
8 |
|
9 |
BUT, if I do: |
10 |
|
11 |
# ebuild /usr/local/portage/media-sound/gwc/gwc-0.17.4.ebuild unpack |
12 |
# cd /var/tmp/portage/gwc-0.17.4/work/gwc-0.17-4/ |
13 |
# ./configure --host=i686-pc-linux-gnu --prefix=/usr \ |
14 |
--infodir=/usr/share/info --mandir=/usr/share/man |
15 |
# make |
16 |
|
17 |
the compile succeeds. |
18 |
|
19 |
My experience up until now has been that portage behaves just |
20 |
like issuing command from the command line, but here the behavior |
21 |
is clearly different. Why? |
22 |
|
23 |
I assume something in the portage environment is causing this |
24 |
but I'm not sure what; any suggestions are welcome. I'm using |
25 |
portage 2.0.38. |
26 |
|
27 |
Ryan |