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