1 |
Ryan Shaw <ryan.shaw@××××××××××××××.org> writes: |
2 |
|
3 |
> I am currently working on an ebuild for gwc (gnome wave cleaner). |
4 |
> I've done about 20 ebuilds before, but this time I've run into |
5 |
> something new. When I run: |
6 |
> |
7 |
> # ebuild /usr/local/portage/media-sound/gwc/gwc-0.17.4.ebuild compile |
8 |
> |
9 |
> the compile fails. |
10 |
> |
11 |
> BUT, if I do: |
12 |
> |
13 |
> # ebuild /usr/local/portage/media-sound/gwc/gwc-0.17.4.ebuild unpack |
14 |
> # cd /var/tmp/portage/gwc-0.17.4/work/gwc-0.17-4/ |
15 |
> # ./configure --host=i686-pc-linux-gnu --prefix=/usr \ |
16 |
> --infodir=/usr/share/info --mandir=/usr/share/man |
17 |
> # make |
18 |
|
19 |
Ryan, |
20 |
|
21 |
Are you using "emake" instead of "make" within your ebuild? It is |
22 |
often the case that a given package won't build successfully with |
23 |
emake (because of its -j options). |
24 |
|
25 |
Matt |
26 |
|
27 |
-- |
28 |
Matthew Kennedy |
29 |
Gentoo Linux Developer |
30 |
|
31 |
Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x6C25B0A2 |
32 |
Finger Print: 0C61 0CBC C669 5F26 8DBF 006D FBAB 30EA 6C25 B0A2 |