[gentoo-dev] ebuild problem

[gentoo-dev] ebuild problem

[Doug Shea]

    Hello. I'm trying to make a new .ebuild file for a package that I 
like to use under Linux (DVD::Rip), and I'm testing it on my machine, 
and it's giving me an error that I don't understand. The dependencies 
work, and it seems to finish the compile part okay, but it fails when 
installing into the image directory.
    The error is this:

ACCESS DENIED  open_wr:   /usr/share/man/man1/splitpipe.1
Installing /usr/share/man/man1/splitpipe.1
ACCESS DENIED  utime:     /usr/share/man/man1/splitpipe.1
ACCESS DENIED  chmod:     /usr/share/man/man1/splitpipe.1

    ...and there's a summary containing basically those three lines, at 
the end; no new information there.

    What can be causing this error, and how can I fix it? I'm guessing 
that the package that I'm trying to install is doing something wrong, 
but I don't want to go mucking around in that until I'm sure that's the 
right thing to do.
    Any help would be appreciated, especially pointers to TFM, if there 
is one I don't know about, other than the HOWTO link on the Gentoo 
homepage. Thanks!

Doug

Re: [gentoo-dev] ebuild problem

[Jason Ritchie]

The package is trying to put the manpages directly into your /usr tree instead of ${D}/usr.  Try adding --mandir=${D}/usr/share/man to your configure or make line.

-----Original Message-----
From: Doug Shea <doug_shea@alumni.ucsd.edu>
To: gentoo-dev@gentoo.org
Date: Sat, 13 Apr 2002 15:42:20 -0700 
Subject: [gentoo-dev] ebuild problem


    Hello. I'm trying to make a new .ebuild file for a package that I 
like to use under Linux (DVD::Rip), and I'm testing it on my machine, 
and it's giving me an error that I don't understand. The dependencies 
work, and it seems to finish the compile part okay, but it fails when 
installing into the image directory.
    The error is this:

ACCESS DENIED  open_wr:   /usr/share/man/man1/splitpipe.1
Installing /usr/share/man/man1/splitpipe.1
ACCESS DENIED  utime:     /usr/share/man/man1/splitpipe.1
ACCESS DENIED  chmod:     /usr/share/man/man1/splitpipe.1

    ...and there's a summary containing basically those three lines, at 
the end; no new information there.

    What can be causing this error, and how can I fix it? I'm guessing
that the package that I'm trying to install is doing something wrong,
but I don't want to go mucking around in that until I'm sure that's the
right thing to do.
    Any help would be appreciated, especially pointers to TFM, if there
is one I don't know about, other than the HOWTO link on the Gentoo
homepage. Thanks!

Doug

[gentoo-dev] Ebuild problem

[John P. Marr]

I am trying to install kdemultimedia, and I am getting an error message:

kde_src_compile, Line -3694 Exitcode 2

What can i do to fix this?

Re: [gentoo-dev] Ebuild problem

[Spider]

[-- Attachment #1: Type: text/plain, Size: 641 bytes --]

please. 
please.
PLEASE.
tell us what goes wrong?

to hear theres an error here. it says an invalid line-number and a code.

its just as bad as saying : "My computer won't work" when you have
forgotten your password to your account.


//Spider


begin  quote
On Wed, 12 Jun 2002 22:26:52 -0400
"John P. Marr" <jpmarr@optonline.net> wrote:

> I am trying to install kdemultimedia, and I am getting an error
> message:
> 
> kde_src_compile, Line -3694 Exitcode 2
> 
> What can i do to fix this?
> 
--
begin  .signature
This is a .signature virus! Please copy me into your .signature!
See Microsoft KB Article Q265230 for more information.
end

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-dev] ebuild problem

[mschroer]

I am new to Gentoo and having trouble with an ebuild.  I put the latest 
tarball of anjuta-0.9.99.tar.gz in the distfile directory and built a 
new ebuild file from the anjuta-0.1.9.ebuild.  When I emerge, running as 
root, I get the following error:

******** all the unpack and compile seem to work fine and the image is 
built in var///  and I get to here *******
 
make  install-man1
make[3]: Entering directory 
`/var/tmp/portage/anjuta-0.9.99/work/anjuta-0.9.99/doc'
/bin/sh ../mkinstalldirs /usr/share/man/man1
 /bin/install -c -m 644 ./anjuta.1 /usr/share/man/man1/anjuta.1
ACCESS DENIED  open_wr:   /usr/share/man/man1/anjuta.1
/bin/install: cannot create regular file `/usr/share/man/man1/anjuta.1': 
Permission denied
 /bin/install -c -m 644 ./anjuta_launcher.1 
/usr/share/man/man1/anjuta_launcher.1
ACCESS DENIED  open_wr:   /usr/share/man/man1/anjuta_launcher.1
/bin/install: cannot create regular file 
`/usr/share/man/man1/anjuta_launcher.1': Permission denied
make[3]: *** [install-man1] Error 1
make[3]: Leaving directory 
`/var/tmp/portage/anjuta-0.9.99/work/anjuta-0.9.99/doc'
make[2]: *** [install-man] Error 2
make[2]: Leaving directory 
`/var/tmp/portage/anjuta-0.9.99/work/anjuta-0.9.99/doc'
make[1]: *** [install-am] Error 2
make[1]: Leaving directory 
`/var/tmp/portage/anjuta-0.9.99/work/anjuta-0.9.99/doc'
make: *** [install-recursive] Error 1

!!! ERROR: The ebuild did not complete successfully.
!!! Function src_install, Line 8, Exitcode 2
!!! (no error message)

--------------------------- ACCESS VIOLATION SUMMARY 
---------------------------
LOG FILE = "/tmp/sandbox-anjuta-0.9.99-23571.log"

open_wr:   /usr/share/man/man1/anjuta.1
open_wr:   /usr/share/man/man1/anjuta_launcher.1
--------------------------------------------------------------------------------
!!! emerge aborting on  /usr/portage/dev-util/anjuta/anjuta-0.9.99.ebuild .


Can anyone help me ?

Re: [gentoo-dev] ebuild problem

[Paul de Vrieze]

On Saturday 31 August 2002 21:54, mschroer wrote:
> I am new to Gentoo and having trouble with an ebuild.  I put the latest
> tarball of anjuta-0.9.99.tar.gz in the distfile directory and built a
> new ebuild file from the anjuta-0.1.9.ebuild.  When I emerge, running as
> root, I get the following error:
>
> ******** all the unpack and compile seem to work fine and the image is
> built in var///  and I get to here *******
>
> make  install-man1
> make[3]: Entering directory
> `/var/tmp/portage/anjuta-0.9.99/work/anjuta-0.9.99/doc'
> /bin/sh ../mkinstalldirs /usr/share/man/man1
>  /bin/install -c -m 644 ./anjuta.1 /usr/share/man/man1/anjuta.1
> ACCESS DENIED  open_wr:   /usr/share/man/man1/anjuta.1
> /bin/install: cannot create regular file `/usr/share/man/man1/anjuta.1':
> Permission denied
>  /bin/install -c -m 644 ./anjuta_launcher.1
> /usr/share/man/man1/anjuta_launcher.1
> ACCESS DENIED  open_wr:   /usr/share/man/man1/anjuta_launcher.1
> /bin/install: cannot create regular file
> `/usr/share/man/man1/anjuta_launcher.1': Permission denied
> make[3]: *** [install-man1] Error 1
> make[3]: Leaving directory
> `/var/tmp/portage/anjuta-0.9.99/work/anjuta-0.9.99/doc'
> make[2]: *** [install-man] Error 2
> make[2]: Leaving directory
> `/var/tmp/portage/anjuta-0.9.99/work/anjuta-0.9.99/doc'
> make[1]: *** [install-am] Error 2
> make[1]: Leaving directory
> `/var/tmp/portage/anjuta-0.9.99/work/anjuta-0.9.99/doc'
> make: *** [install-recursive] Error 1
>
> !!! ERROR: The ebuild did not complete successfully.
> !!! Function src_install, Line 8, Exitcode 2
> !!! (no error message)
>
> --------------------------- ACCESS VIOLATION SUMMARY
> ---------------------------
> LOG FILE = "/tmp/sandbox-anjuta-0.9.99-23571.log"
>
> open_wr:   /usr/share/man/man1/anjuta.1
> open_wr:   /usr/share/man/man1/anjuta_launcher.1
> ---------------------------------------------------------------------------
>----- !!! emerge aborting on 
> /usr/portage/dev-util/anjuta/anjuta-0.9.99.ebuild .
>
>
> Can anyone help me ?
>

The trick is that portage uses sandboxing. This means building is only allowed 
in /var/tmp/portage/<bla>

This means you must persuade anjuta to install in the destination root which 
is given in an ebuild by ${D}. This technique makes it a lot easier to track 
which files should become part of the package.

Oftern this persuading can be done with the DESTDIR variable, but sometimes 
further tricks are nescesary. I advise you to look at some ebuilds (look for 
PREFIX=${D}/usr/ ), and check the makefile of anjuta.

Paul

-- 
Paul de Vrieze
Junior Researcher
Mail: pauldv@cs.kun.nl
Homepage: http://www.devrieze.net

Re: [gentoo-dev] ebuild problem

[Thomas T. Veldhouse]

It would probably help if you ran the ebuild as root :)

Tom Veldhouse

----- Original Message -----
From: "Paul de Vrieze" <pauldv@cs.kun.nl>
To: <gentoo-dev@gentoo.org>
Sent: Monday, September 02, 2002 3:07 AM
Subject: Re: [gentoo-dev] ebuild problem


On Saturday 31 August 2002 21:54, mschroer wrote:
> I am new to Gentoo and having trouble with an ebuild.  I put the latest
> tarball of anjuta-0.9.99.tar.gz in the distfile directory and built a
> new ebuild file from the anjuta-0.1.9.ebuild.  When I emerge, running as
> root, I get the following error:
>
> ******** all the unpack and compile seem to work fine and the image is
> built in var///  and I get to here *******
>
> make  install-man1
> make[3]: Entering directory
> `/var/tmp/portage/anjuta-0.9.99/work/anjuta-0.9.99/doc'
> /bin/sh ../mkinstalldirs /usr/share/man/man1
>  /bin/install -c -m 644 ./anjuta.1 /usr/share/man/man1/anjuta.1
> ACCESS DENIED  open_wr:   /usr/share/man/man1/anjuta.1
> /bin/install: cannot create regular file `/usr/share/man/man1/anjuta.1':
> Permission denied
>  /bin/install -c -m 644 ./anjuta_launcher.1
> /usr/share/man/man1/anjuta_launcher.1
> ACCESS DENIED  open_wr:   /usr/share/man/man1/anjuta_launcher.1
> /bin/install: cannot create regular file
> `/usr/share/man/man1/anjuta_launcher.1': Permission denied
> make[3]: *** [install-man1] Error 1
> make[3]: Leaving directory
> `/var/tmp/portage/anjuta-0.9.99/work/anjuta-0.9.99/doc'
> make[2]: *** [install-man] Error 2
> make[2]: Leaving directory
> `/var/tmp/portage/anjuta-0.9.99/work/anjuta-0.9.99/doc'
> make[1]: *** [install-am] Error 2
> make[1]: Leaving directory
> `/var/tmp/portage/anjuta-0.9.99/work/anjuta-0.9.99/doc'
> make: *** [install-recursive] Error 1
>
> !!! ERROR: The ebuild did not complete successfully.
> !!! Function src_install, Line 8, Exitcode 2
> !!! (no error message)
>
> --------------------------- ACCESS VIOLATION SUMMARY
> ---------------------------
> LOG FILE = "/tmp/sandbox-anjuta-0.9.99-23571.log"
>
> open_wr:   /usr/share/man/man1/anjuta.1
> open_wr:   /usr/share/man/man1/anjuta_launcher.1
> --------------------------------------------------------------------------
-
>----- !!! emerge aborting on
> /usr/portage/dev-util/anjuta/anjuta-0.9.99.ebuild .
>
>
> Can anyone help me ?
>

The trick is that portage uses sandboxing. This means building is only
allowed
in /var/tmp/portage/<bla>

This means you must persuade anjuta to install in the destination root which
is given in an ebuild by ${D}. This technique makes it a lot easier to track
which files should become part of the package.

Oftern this persuading can be done with the DESTDIR variable, but sometimes
further tricks are nescesary. I advise you to look at some ebuilds (look for
PREFIX=${D}/usr/ ), and check the makefile of anjuta.

Paul

--
Paul de Vrieze
Junior Researcher
Mail: pauldv@cs.kun.nl
Homepage: http://www.devrieze.net

_______________________________________________
gentoo-dev mailing list
gentoo-dev@gentoo.org
http://lists.gentoo.org/mailman/listinfo/gentoo-dev

Re: [gentoo-dev] ebuild problem

[Paul de Vrieze]

On Monday 02 September 2002 20:46, Thomas T. Veldhouse wrote:
> It would probably help if you ran the ebuild as root :)
>
> Tom Veldhouse

Portage doesn't even try to run as non-root, he is just being sandboxed

Paul

-- 
Paul de Vrieze
Junior Researcher
Mail: pauldv@cs.kun.nl
Homepage: http://www.devrieze.net

[gentoo-dev] ebuild problem

[Norberto BENSA]

[-- Attachment #1.1: body text --]
[-- Type: text/plain, Size: 789 bytes --]

Hello,

I'm trying to update BasiliskII. I got the source tarball and I've copied (and 
modified) the ebuild from basiliskII-0.9.0, but when I do "emerge 
basiliskII," I get this:

nbensa@venkman nbensa $ PORTDIR_OVERLAY=/home/nbensa/portage sudo emerge 
basiliskII
Password:
Calculating dependencies ...done!
>>> emerge (1 of 1) app-emulation/basiliskII-1.0.0 to /
>>> md5 ;-) BasiliskII-jit-1.0-mdk-src.tar.bz2
/usr/sbin/ebuild.sh: line 1041: 
/home/nbensa/portage/app-emulation/basiliskII/basiliskII-1.0.0.ebuild: 
Permission denied

!!! ERROR: app-emulation/basiliskII-1.0.0 failed.
!!! Function , Line 1041, Exitcode 1
!!! error sourcing ebuild


Attached, the ebuild. Could someone please take a look and tell what's wrong?

Many thanks in advance,
Norberto

[-- Attachment #1.2: basiliskII-1.0.0.ebuild --]
[-- Type: text/plain, Size: 2653 bytes --]

# Copyright 1999-2003 Gentoo Technologies, Inc.
# Distributed under the terms of the GNU General Public License v2
# $Header: /home/cvsroot/gentoo-x86/app-emulation/basiliskII/basiliskII-0.9.0.ebuild,v 1.11 2003/03/16 22:22:11 mholzer Exp $

IUSE="X gtk xv esd dga"

inherit flag-o-matic

### This package requires a Mac II/Classic ROM, A Mac OS Image
### Mac OS 7.5.3r2 is available freely from the Apple Homepage
### System ROMS can be retreived from a 'real' Mac, See info/man pages

DESCRIPTION="BasiliskII-1.0.0 Macintosh Emulator (Stable Release)"
HOMEPAGE="http://gwenole.beauchesne.online.fr/basilisk2/"
LICENSE="GPL-2 | LGPL-2.1"
KEYWORDS="x86 -ppc"
SLOT="0"

### We'll set $S Manually, it's version dependant, and nested strangely.
S=${WORKDIR}/BasiliskII-jit-1.0/src/Unix

### fbdev support in the stable release...  the cvs branch is broken, period!
### gtk and esd support are compile time options, we'll check the usual
### use variables here and set ./configure options accordingly

DEPEND="gtk? ( x11-libs/gtk+ )
	esd? ( media-sound/esound )"


SRC_URI="http://hometown.aol.de/wimdk/files/BasiliskII-jit-1.0-mdk-src.tar.bz2"

src_compile() {

	#fpu_x86 doesnt compile properly if -O3 or greater :(
	replace-flags -O[3-9] -O2

	local myflags

### Default ./configure options are all =yes by default. we'll check for
### and use -values and switch them accordingly

	use X || myflags="${myflags} --with-x=no"
	use esd || myflags="${myflags} --with-esd=no"
	use gtk || myflags="${myflags} --with-gtk=no"
	use dga || myflags="${myflags} --with-dga=no"
	use xv || myflags="${myflags} --enable-xf86-vidmode=no"

	./configure \
		--host=${CHOST} \
		--prefix=/usr \
		--infodir=/usr/share/info \
		--mandir=/usr/share/man \
		${myflags} || die "BasiliskII ./configure Failed"

	#hack to link against libstdc++ for gcc3.x compatibility
	cp Makefile Makefile.old
	sed -e 's:-o $(OBJ_DIR)/gencpu:-lstdc++ -o $(OBJ_DIR)/gencpu:' \
		Makefile.old > Makefile

	emake || die "BasiliskII Make Failed"
}

src_install () {
	make \
		prefix=${D}/usr \
		mandir=${D}/usr/share/man \
		infodir=${D}/usr/share/info \
		install || die "BasiliskII Make Install Failed"

### Networking is _disabled_ in this revision,  hopefully -r2 will
### resolve the permissions issue / linux src compilation problem
### that prevents it's inclusion

### Uncomment the following, and read the manual _carefully_ if you really
### need networking, this will create a sheep_net.o kernel module that
### provides (effectivly) an ethernet bridge between basliskII and the kernel

#	make modules

}

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] ebuild problem

[Aron Griffis]

[-- Attachment #1: Type: text/plain, Size: 884 bytes --]

Norberto BENSA wrote:   [Sun Apr 27 2003, 05:09:32AM EDT]
> nbensa@venkman nbensa $ PORTDIR_OVERLAY=/home/nbensa/portage sudo emerge 
> basiliskII
> Password:
> Calculating dependencies ...done!
> >>> emerge (1 of 1) app-emulation/basiliskII-1.0.0 to /
> >>> md5 ;-) BasiliskII-jit-1.0-mdk-src.tar.bz2
> /usr/sbin/ebuild.sh: line 1041: 
> /home/nbensa/portage/app-emulation/basiliskII/basiliskII-1.0.0.ebuild: 
> Permission denied
> 
> !!! ERROR: app-emulation/basiliskII-1.0.0 failed.
> !!! Function , Line 1041, Exitcode 1
> !!! error sourcing ebuild

Have you tried doing this directly as root instead of sudo?  I dimly
recall having trouble using sudo this way.

Also you could

    chmod a+r basiliskII-1.0.0.ebuild

That would probably do the trick.  The error message above clearly says
that Portage does not have permission to read the ebuild.

Aron

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] ebuild problem

[Norberto BENSA]

[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 589 bytes --]

nbensa@venkman ~ $ date ; echo ${Aron Griffis}
Sunday 27 April 2003 03:25 pm

> Norberto BENSA wrote:   [Sun Apr 27 2003, 05:09:32AM EDT]
>
> > !!! ERROR: app-emulation/basiliskII-1.0.0 failed.
> > !!! Function , Line 1041, Exitcode 1
> > !!! error sourcing ebuild
>
> Have you tried doing this directly as root instead of sudo?  I dimly
> recall having trouble using sudo this way.

Yup. Same problem.

It seems that the .ebuild is the problem here but I can't find what's wrong. 
I've checked the tarball and is OK, I can 'tar jxf' as user and root.

Thanks,
Norberto

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] ebuild problem

[Aron Griffis]

[-- Attachment #1: Type: text/plain, Size: 448 bytes --]

Norberto BENSA wrote:	[Sun Apr 27 2003, 03:26:20PM EDT]
> It seems that the .ebuild is the problem here but I can't find what's wrong. 
> I've checked the tarball and is OK, I can 'tar jxf' as user and root.

I suspect the directories are owned by you and -rwx------ or something
like that.  Root can read the files, but the "portage" user can't, so it
breaks when portage transitions to the "portage" user.

chmod -R a+rX portage

Aron

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] ebuild problem (SOLVED)

[Norberto BENSA]

[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 436 bytes --]

nbensa@venkman ~ $ date ; echo ${Aron Griffis}
Sunday 27 April 2003 07:47 pm

> I suspect the directories are owned by you and -rwx------ or something

Yup... /home/nbensa is -rwx------ (only me can read: I feel stupid now :-/

I've moved my portdir-overlay to /usr/local/portage and I'm emerging 
BasiliskII 1.0 right now. I'll summit this to http://bugs.gentoo.org/ if it 
works.

Thanks Aron!!

Best regards,
Norberto

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]