public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Thomas T. Veldhouse" <veldy@veldy.net>
To: "Paul de Vrieze" <pauldv@cs.kun.nl>, <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] ebuild problem
Date: Mon, 2 Sep 2002 13:46:20 -0500	[thread overview]
Message-ID: <00da01c252b1$077df720$0101a8c0@cascade> (raw)
In-Reply-To: 200209021007.42932.pauldv@cs.kun.nl

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





  reply	other threads:[~2002-09-02 18:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-31 19:54 [gentoo-dev] ebuild problem mschroer
2002-09-02  8:07 ` Paul de Vrieze
2002-09-02 18:46   ` Thomas T. Veldhouse [this message]
2002-09-02 19:07     ` Paul de Vrieze
  -- strict thread matches above, loose matches on Subject: below --
2003-04-27  9:09 Norberto BENSA
2003-04-27 18:25 ` Aron Griffis
2003-04-27 19:26   ` Norberto BENSA
2003-04-27 22:47     ` Aron Griffis
2002-06-13  2:26 [gentoo-dev] Ebuild problem John P. Marr
2002-06-13 15:55 ` Spider
2002-04-13 23:16 [gentoo-dev] ebuild problem Jason Ritchie
2002-04-13 22:42 Doug Shea

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='00da01c252b1$077df720$0101a8c0@cascade' \
    --to=veldy@veldy.net \
    --cc=gentoo-dev@gentoo.org \
    --cc=pauldv@cs.kun.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox