| 1 |
Ryan Shaw <ryan.shaw@××××××××××××××.org> writes: |
| 2 |
|
| 3 |
> > > |
| 4 |
> > > # ebuild /usr/local/portage/media-sound/gwc/gwc-0.17.4.ebuild unpack |
| 5 |
> > > # cd /var/tmp/portage/gwc-0.17.4/work/gwc-0.17-4/ |
| 6 |
> > > # ./configure --host=i686-pc-linux-gnu --prefix=/usr \ |
| 7 |
> > > --infodir=/usr/share/info --mandir=/usr/share/man |
| 8 |
> > > # make |
| 9 |
> > |
| 10 |
> > Are you using "emake" instead of "make" within your ebuild? It is |
| 11 |
> > often the case that a given package won't build successfully with |
| 12 |
> > emake (because of its -j options). |
| 13 |
> |
| 14 |
> I am using make. Originally I was using emake, and changing that |
| 15 |
> was the first thing I tried, since I have run into that problem |
| 16 |
> before. But now I am using make, and I am literally cutting and |
| 17 |
> pasting the contents of the src_compile() subroutine into a shell |
| 18 |
> when I test building outside of portage...yet the results differ. |
| 19 |
|
| 20 |
You *might* have run into a short-coming of the sandbox. Try turning |
| 21 |
the sandbox off for your ebuild (see the emacs or xemacs ebuilds). If |
| 22 |
this is the case, and it works with the sandbox off, then welcome to a |
| 23 |
sweet chunk of frustration :) |
| 24 |
|
| 25 |
Matt |
| 26 |
|
| 27 |
-- |
| 28 |
Matthew Kennedy |
| 29 |
Gentoo Linux Developer |
Archives