From: Christian Plessl <plessl@tik.ee.ethz.ch>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Sandbox violation, ebuild creation
Date: Fri, 14 Feb 2003 10:33:20 +0100 [thread overview]
Message-ID: <b2id0n$jl8$1@main.gmane.org> (raw)
Im trying to create my own ebuild for PerlQt, the Qt bindings for Perl.
Compiling of the ebuild works well, but when it comes to installation the
ebuild fails with a 'sandbox violation', see error message below.
!!! ERROR: dev-perl/PerlQt-3.006 failed.
!!! Function perl-module_src_install, Line -846, Exitcode 2
!!! (no error message)
--------------------------- ACCESS VIOLATION SUMMARY
---------------------------
LOG FILE = "/tmp/sandbox-PerlQt-3.006-29386.log"
open_wr: /usr/bin/pqtsh
chmod: /usr/bin/pqtsh
open_wr: /usr/bin/pqtapi
chmod: /usr/bin/pqtapi
open_wr: /usr/kde/3.1/bin/puic
------------------------------------------------------
The package installs a perl modules and some additional programs, the ones
that fail. The installation of the perl modules works well.
The ebuild is very short (due to the wonderfull per-module eclass!)
DESCRIPTION="Perl bindings for the Qt 3.x toolkit"
HOMEPAGE="http://perlqt.sourceforge.net/"
inherit kde perl-module
SRC_URI="mirror://sourceforge/perlqt/${P}.tar.gz"
LICENSE="GPL-2"
SLOT="0"
KEYWORDS="x86"
DEPEND=" >=x11-libs/qt-3.0.0"
mydoc="ChangeLog README TODO INSTALL COPYING"
How can I fix these sandbox violations?
Best regards,
Christian
--
Christian Plessl <plessl@tik.ee.ethz.ch>
Computer Engineering and Networks Lab, ETH Zurich, Switzerland
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2003-02-14 9:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-14 9:33 Christian Plessl [this message]
2003-02-14 15:15 ` [gentoo-dev] Sandbox violation, ebuild creation Joachim Blaabjerg
2003-02-14 15:58 ` Martin Holzer
2003-02-14 16:28 ` [gentoo-dev] " Christian Plessl
2003-02-14 15:58 ` Christian Plessl
2003-02-17 7:58 ` Christian Plessl
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='b2id0n$jl8$1@main.gmane.org' \
--to=plessl@tik.ee.ethz.ch \
--cc=gentoo-dev@gentoo.org \
/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