| 1 |
On Tue, 2002-10-15 at 00:19, Matthew Kennedy wrote: |
| 2 |
|
| 3 |
> Ryan Shaw <ryan.shaw@××××××××××××××.org> writes: |
| 4 |
> |
| 5 |
> > I am currently working on an ebuild for gwc (gnome wave cleaner). |
| 6 |
> > I've done about 20 ebuilds before, but this time I've run into |
| 7 |
> > something new. When I run: |
| 8 |
> > |
| 9 |
> > # ebuild /usr/local/portage/media-sound/gwc/gwc-0.17.4.ebuild compile |
| 10 |
> > |
| 11 |
> > the compile fails. |
| 12 |
> > |
| 13 |
> > BUT, if I do: |
| 14 |
> > |
| 15 |
> > # ebuild /usr/local/portage/media-sound/gwc/gwc-0.17.4.ebuild unpack |
| 16 |
> > # cd /var/tmp/portage/gwc-0.17.4/work/gwc-0.17-4/ |
| 17 |
> > # ./configure --host=i686-pc-linux-gnu --prefix=/usr \ |
| 18 |
> > --infodir=/usr/share/info --mandir=/usr/share/man |
| 19 |
> > # make |
| 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 |
I am using make. Originally I was using emake, and changing that |
| 26 |
was the first thing I tried, since I have run into that problem |
| 27 |
before. But now I am using make, and I am literally cutting and |
| 28 |
pasting the contents of the src_compile() subroutine into a shell |
| 29 |
when I test building outside of portage...yet the results differ. |
Archives