ting it within the ebuild.
> Does "inherit git-r3" redefine something.
>
> Many thanks for hint,
> Helmut
>
Network access is disabled in ebuild phase functions by
FEATURES="network-sandbox". You can disable that by adding
RESTRICT="network-sandbox&quo
u boot your machine with prior to starting the installation?
Please also include the version and URL where you downloaded this from.
> I didn't try your advices as I don't now how to try them. How do I
> deactivate sandbox?
Michael "grimlog" Schreckenbauer actually already
86_64-pc-linux-gnu-gccbug
lightning ~ #
It seems that others may have fixed this by erasing the
/usr/bin/i686-pc-* files.
- Mark
Richard,
I moved the i686-gcc files to a remote directory. With that change
sandbox now emerges cleanly:
Original instance of package unmerged safely.
Regeneratin
Thank you. Disabling ccache fixed it.
p MAKEOPTS /etc/make.conf
> MAKEOPTS="-j1"
> [EMAIL PROTECTED] ~ #
>
> Besides, a colegue of mine has the same problem
while wondering why it's trying to access the floppy disk,
you can try
#FEATURES="-sandbox" emerge foo/bar
This will disable the cage
proc/13606/cmdline:
../../coreconf/nsinstall/Linux2.6_x86_64_x86_64-pc-linux-gnu-gcc_glibc_PTH_64_OPT.OBJ/nsinstall
-D ../../dist public dbm
I would try it with sandbox disabled.
FEATURES="-*sandbox*"
It may work. Certainly worth a shot I guess.
Dale
:-) :-)
Microsoft and Intel free
>
> 08:47:40 up 23:30, 5 users, load average: 0.10, 0.11, 0.33
> Linux 2.6.5-gentoo-r1 i686 AMD Athlon(tm) XP 2400+
OK so it built with FEATURES="-sandbox" but I guess I don't understand why.
Could someone give a brief description of the cause of s
I wouldn't mind the package to write to its own working directory
> /var/tmp/portage/dev-python/grako-3.99.9/work
> but I cannot find out how to disable setuptools.sandbox
>
> I've tried addwrite "$S" and FEATURES=-usersandbox -sandbox
>
> but nothing helps.
T
> * LOG FILE: "/var/log/sandbox/sandbox-29464.log"
> *
> VERSION 1.0
> FORMAT: F - Function called
> FORMAT: S - Access Status
> FORMAT: P - Path as passed to function
> FORMAT: A - Absolute Path (not canonical)
> FORMAT: R - Canonical Path
> FORM
table with
> >> stuff like this hanging about)
> >>
> >> Cheers,
> >> Mark
> >
> > The libmpfr change bit me on one of my amd64 machines. I did the
> > revdep-rebuild on the library and then gcc was broken. I recompiled
> > ever
ady exists.
--- ACCESS VIOLATION SUMMARY
---
LOG FILE = "/var/log/sandbox/sandbox-net-p2p_-_dcpp-0.-25040.log"
[...]
it seems to me like scons is littering
out from square 1 with a "sandbox" or "Virtual
Machine". That didn't stop vulnerabilities from showing up in Java.
Netscape's Livescript (damn the @##holes for renaming it Javascript)
started off with so little power that the attitude was "Sandbox? We
don't
group/lp-0-r1
* Repository: gentoo
* Maintainer: syst...@gentoo.org print...@gentoo.org
* USE: abi_x86_64 amd64 elibc_glibc kernel_linux userland_GNU
* FEATURES: network-sandbox preserve-libs sandbox userpriv usersandbox
>>> Unpacking source...
>>> Source unpacked in /var/tmp/
On Fri, Nov 09, 2007 at 03:08:53PM -0600, Albert Hopkins wrote:
> > ACCESS DENIED open_wr: /etc/passwd
> > ...
> > ACCESS DENIED open_wr: /etc/passwd
> > --- ACCESS VIOLATION SUMMARY
> > ---
> > LOG FILE =
my system fubar? Any ideas?
Why is unlink getting ACCESS DENIED errors when I run emerge as sudo?
Thanks,
Tom
...
>>> Source compiled.
--- ACCESS VIOLATION SUMMARY
---
LOG FILE =
"/var/log/sandbox/sandbox-gnome-base_-_gnome-desktop-2
---
LOG FILE = "/var/log/sandbox/sandbox-gnome-base_-_gdm-2.8.0.1-1869.log"
open_wr: /etc/pam.d/gdm
open_wr: /etc/pam.d/gdm-autologin
--
gentoo-user@gentoo.org mailing list
Zac Medico wrote:
If you run "equery depends -a scons" and read some of those ebuilds
you'll see something like this:
scons DESTDIR=${D}
See the explanation of ${D} in the ebuild(5) manpage. That helps keep
you inside the sandbox.
Thanks for the tip. It led me to a way
_CONFIG_H -o xgcc gcc.o gccspec.o intl.o \
prefix.o version.o ../libiberty/libiberty.a
* Creating a hardened no-pie no-ssp gcc specs file
--- ACCESS VIOLATION SUMMARY
---
LOG FILE = "/var/log/sandbox/sandbox-sys-devel_-_gcc-3.4.4-r1-25838
sys-devel/libtool-2.4.6-r3)
>
> * Error: The above package list contains packages which cannot be
> * installed at the same time on the same system.
> --
> I did not switch to new profile "17" yet. I was trying to rebuild
> "sys-devel/libtool" first, b
ce the value of having a group of volunteer guinea pigs
> (anybody running ~arch) is demonstrated. That said, masking big
> changes and calling for volunteers among the volunteers doesn't hurt.
>
> Seems like we need to be more careful with code that runs outside the
> sandbox. C
On Tue, Jul 9, 2019 at 2:10 PM Andrew Lowe wrote:
>
> * ACCESS DENIED: open_wr: /dev/snd/controlC0
> * ACCESS DENIED: open_wr: /dev/snd/controlC0
This has nothing to do with permissions, and everything to do with the sandbox.
Most emerge phases are sandboxed.
emp/build.log
* Package: acct-group/lp-0-r1
* Repository: gentoo
* Maintainer: syst...@gentoo.org print...@gentoo.org
* USE: abi_x86_64 amd64 elibc_glibc kernel_linux userland_GNU
* FEATURES: network-sandbox preserve-libs sandbox userpriv
usersandbox
>>> Unpacking source...
SSAGES/csound5.mo
>
> this is the summary:
>
> ---------- ACCESS VIOLATION SUMMARY ---
> LOG FILE = "/var/log/sandbox/sandbox-15019.log"
>
> unlink:/usr/share/locale/de/LC_MESSAGES/csound5.mo
> unlink:/usr/share/locale/en_GB/LC_
:4.4.1-r1::gentoo
dev-build/meson: 1.4.0-r1::gentoo
dev-lang/perl: 5.38.2-r3::gentoo
dev-lang/python: 3.11.9::gentoo, 3.12.3::gentoo
sys-apps/baselayout: 2.15::gentoo
sys-apps/openrc: 0.54::gentoo
sys-apps/sandbox: 2.38::gentoo
sys-devel
too 2.34 p4) 2.34.0
app-shells/bash: 5.0_p17::gentoo
dev-lang/perl:5.30.3::gentoo
dev-lang/python: 2.7.18::gentoo, 3.6.10-r2::gentoo, 3.7.7-r2::gentoo,
3.8.3::gentoo, 3.9.0_beta1::gentoo
dev-util/cmake: 3.17.3::gentoo
sys-apps/baselayout: 2.7::gentoo
sys-a
::gentoo
sys-apps/baselayout: 2.6-r1::gentoo
sys-apps/openrc: 0.42.1::gentoo
sys-apps/sandbox: 2.13::gentoo
sys-devel/autoconf: 2.13-r1::gentoo, 2.69-r4::gentoo
sys-devel/automake: 1.16.1-r1::gentoo
sys-devel/binutils: 2.32-r1::gentoo, 2.33.1-r1::gentoo
sys-devel
On November 27, 2007, Philip Webb wrote:
> 071127 Dmitry S. Makovey wrote:
> > I decided that the time has come to switch over to 64bit computing
> > and went with fresh LiveDVD install of gentoo.
> > After doing stage3 install and making syncing portage
> > I'm fa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom Brown wrote:
>>>> Source compiled.
> --- ACCESS VIOLATION SUMMARY
> ---
> LOG FILE =
> "/var/log/sandbox/sandbox-gnome-base_-_gnome-desktop-2.20.1-27301.log"
Zac Medico wrote:
Maybe you can configure the build so that it won't write outside of the
sandbox. If you post your ebuild then we might be able to help.
Here it is:
# Copyright 1999-2005 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $H
Unable to make KDIR=/usr/src/linux
default.
!!! If you need support, post the topmost build error, NOT this status
message.
--- ACCESS VIOLATION SUMMARY
---
LOG FILE = "/var/log/sandbox/sandbox-media-libs_-_svgalib-1.9.21-r
p/portage/gtkhtml-1.1.10-r1/image/
--- ACCESS VIOLATION SUMMARY
---
LOG FILE =
"/var/log/sandbox/sandbox-gnome-extra_-_gtkhtml-1.1.10-r1-32251.log"
open_wr: /usr/share/gnome/html/gtkhtml/gtkhtml-gtk
> Ebuilding this packages dies of a Sandbox Violation:
>
Post the full build log and ebuild? I was able to get the new version
to
compile and install after using "sed" to loosen the sphinx dependency,
sed -i "s/1\.5/2.0/" setup.py || die
Hi Michael,
this 'sed&
e check if you have this file,
> check it permissions
> and delete it in case you have it.
>
> Helmut
>
I don't think the file exists, also why should he delete it? It is
setuptools/pycrypto which tries to write files outside the sandbox
which is not allowed.
Tamer you can try if pycrypto installs fine with setuptools 0.7.3. If
yes you should open a bug about the pycrypto-2.6-r2 sandbox issue
with setuptools 0.6.30-r1
--
Regards
Daniel
red.
> So this is the real error - portage can't (pre)load libsandbox.so.
> 1) When is the last time you did a full upgrade? I'm now wondering if
> you have inconsistent versions of different packages installed.
> 2) Try re-emerging sys-apps/sandbox.
>
- I just did
mkstemp:
> > >
> >
/run/user/0/orcexec.XX-]
> > > Building documentation: morituri.common.checksum
> > > (/var/tmp/portage/media-
> > sound/morituri-0.2.3/work/moritu
mkstemp:
> > >
> >
/run/user/0/orcexec.XX-]
> > > Building documentation: morituri.common.checksum
> > > (/var/tmp/portage/media-
> > sound/morituri-0.2.3/work/moritu
On Mon, Oct 25, 2010 at 5:36 AM, Dale wrote:
> FEATURES=" buildpkg sandbox fixpackages parallel-fetch --keep-going"
I thought --keep-going goes into EMERGE_DEFAULT_OPTS, no?
--
Fatih
> It will be included in 2.6.20 kernel, as it seems. But it's not in
> 2.6.19.1 :-(
But it will be in 2.6.19.2 - hooray!
signature.asc
Description: OpenPGP digital signature
On Sun, 2024-09-01 at 18:56 -0500, Dale wrote:
> FEATURES="-usersync userpriv usersandbox buildpkg sandbox
> parallel-fetch parallel-install"
No candy? You struck me as a candy guy.
o
dev-lang/perl:5.30.3::gentoo
dev-lang/python: 2.7.18-r2::gentoo, 3.6.11-r2::gentoo,
3.7.8-r2::gentoo, 3.8.5::gentoo
dev-util/ccache: 3.7.11::gentoo
dev-util/cmake: 3.16.5::gentoo
dev-util/pkgconfig: 0.29.2::gentoo
sys-apps/baselayout: 2.7::gentoo
t all I will ever get is this error page.
>
> That's not all, though, I also get to see error messages, namely the
> following in my terminal:
>
> ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf
> failure in syscall 0265
>
> And
Hi All
I cant install neon, it gives me sandbox violation :-(
Is there any way to solve this ?
10nx
--
Jabber: [EMAIL PROTECTED]
ICQ: 105266647
6774-neon-0.24.7.log.bz2
Description: BZip2 compressed data
pgpscZpz8QGjQ.pgp
Description: PGP signature
> ACCESS DENIED open_wr: /etc/passwd
> ...
> ACCESS DENIED open_wr: /etc/passwd
> ------- ACCESS VIOLATION SUMMARY
> ---
> LOG FILE = "/var/log/sandbox/sandbox-dev-libs_-_glib-2.14.3-11618.log"
>
> open_wr: /e
compiled.
| --- ACCESS VIOLATION SUMMARY
| ---
| LOG FILE = "/var/log/sandbox/sandbox-16382.log"
|
| unlink:/usr/share/xml2po/docbook.pyc
| unlink:/usr/share/xml2po/docbook.pyc
| unlink:/usr/share/xml2po/docbook.pyc
| unlink:/usr/share/xml2po/docbook.py
userpriv will
>
> "Allow portage to drop root privileges and compile packages as
> portage:portage without a sandbox"
According to my emerge --info output I have sandbox, usersandbox and userpriv,
all set. The owner of my portage directory and all files therein is
root:root. Sh
Kevin wrote:
> and here it is emerge --info:
> http://dpaste.com/hold/47084/
According to http://bugs.gentoo.org/267053, downgrading sandbox to version
1.7 should work around the problem until it is fixed properly.
here you downloaded this from.
> I didn't try your advices as I don't now how to try them. How do I
> deactivate sandbox?
Michael "grimlog" Schreckenbauer actually already told you how to do this:
**
If you cannot upgrade your kernel right now, you can disable the sa
nching alsa correctly. Also the above could be a
sandboxing limitation?
> Amongst this stuff is a line:
>
> LOG FILE: "/var/log/sandbox/sandbox-20431.log"
>
> which I think confirms my suspicions that something is wrong with my
> sandbox as I also get this erro
On Sunday, 5 March 2023 16:13:24 GMT Arve Barsnes wrote:
> On Sun, 5 Mar 2023 at 16:21, Peter Humphrey wrote:
> > Hello list,
> >
> > Am I the only one unable to install net-libs/nodejs-18.14.2? The log file
> > has>
> > some interesting entries:
> > *
ntoo
> dev-build/libtool: 2.4.7-r4::gentoo
> dev-build/make:4.4.1-r1::gentoo
> dev-build/meson: 1.4.0-r1::gentoo
> dev-lang/perl: 5.38.2-r3::gentoo
> dev-lang/python: 3.11.9::gentoo, 3.12.3::gentoo
> sys-apps/baselayout:
uild/meson: 1.4.0-r1::gentoo
> dev-lang/perl: 5.38.2-r3::gentoo
> dev-lang/python: 3.11.9::gentoo, 3.12.3::gentoo
> sys-apps/baselayout: 2.15::gentoo
> sys-apps/openrc: 0.54::gentoo
> sys-apps/sandbox: 2.38::gentoo
&
-lang/perl:5.30.3::gentoo
dev-lang/python: 2.7.18-r2::gentoo, 3.7.8-r2::gentoo, 3.8.5::gentoo
dev-util/cmake: 3.17.4-r1::gentoo
sys-apps/baselayout: 2.7::gentoo
sys-apps/openrc: 0.42.1::gentoo
sys-apps/sandbox: 2.18::gentoo
sys-devel/autoconf:
morituri-0.2.3/work/morituri-0.2.3'
> > > > ** Message: pygobject_register_sinkfunc is deprecated (GstObject)
> > > > Progress:
> > > > 00:10
> > > > (null)*(null) (null)ACCESS DENIED(null): mkstemp:
> > > >
> > >
> /
--- Stoian Ivanov <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] ~ # emerge -a foomatic-db-engine
>
Oops, thats FEATURES=-sandbox
__
Discover Yahoo!
Have fun online with music videos, cool games, IM and more. Check i
On Thu, 17 Nov 2011 03:17:23 -0600, Dale wrote:
> FEATURES="buildpkg sandbox parallel-fetch --keep-going"
Shouldn't --keep-going be in EMERGE_DEFAULT_OPTS?
--
Neil Bothwick
Vuja De: the feeling that you've never been here before.
signature.asc
Description: PGP signature
FEATURES="autoconfig ccache distlocks fixpackages sandbox sfperms strict
userpriv usersandbox"
I would try getting rid of ccache, first.. and if you have distcc
installed (portage still could be using it if you updated your profile
and path).
--
gentoo-user@gentoo.org mailing list
Hey,
Quoting itsgrant (2021-04-02 18:58:56)
>* ACCESS DENIED: unlink: /dev/null.dwo
I had the same issue, I found a bug report about it,
it was due to ccache:
https://bugs.gentoo.org/770931
Guillaume
6.5::gentoo
sys-apps/baselayout: 2.6-r1::gentoo
sys-apps/openrc: 0.42.1::gentoo
sys-apps/sandbox: 2.18::gentoo
sys-devel/autoconf: 2.13-r1::gentoo, 2.69-r4::gentoo
sys-devel/automake: 1.11.6-r3::gentoo, 1.16.1-r1::gentoo
sys-devel/binutils: 2.33.1-r1::
t related to hal daemon problem?
emerge -vuD glibc
[...]
usr/lib/libc_nonshared.a
>>> Completed installing glibc-2.9_p20081201-r2 into
>>> /var/tmp/portage/sys-libs/glibc-2.9_p20081201-r2/image/
--- ACCESS VIOLATION SUMMARY -
> Source compiled.
> --- ACCESS VIOLATION SUMMARY
> ---
> LOG FILE =
> "/var/log/sandbox/sandbox-gnome-base_-_gnome-desktop-2.20.1-27301.log"
>
> unlink:/usr/share/xml2po/docbook.pyc
I seem to have gotten past the unlink issue. I modified
On 2019.01.21 13:41, Jacques Montier wrote:
Le lun. 21 janv. 2019 à 19:19, Jack
a
écrit :
>
> I have a suspicion that this really might be sandbox related.
> /dev/fd/whatever are all in the live system, and if I understand
> correctly, emerge works within the sandbox, so you s
uild.log'.
> * The ebuild environment file is located at
> '/var/tmp/portage/net-irc/anope-/temp/environment'.
> * Working directory:
> '/var/tmp/portage/net-irc/anope-/work/anope-_build'
> * S: '/var/tmp/portage/net-irc/anope-/wor
Am 25.10.2010 04:36, schrieb Dale:
> FEATURES=" buildpkg sandbox fixpackages parallel-fetch --keep-going"
Hi,
parallel-fetch is default and no need to list it in make.conf any more.
I notices when I had to add -parallel-fetch to one of my boxes.
kh
he version 3.7.11 [enabled]
app-shells/bash: 5.0_p18::gentoo
dev-java/java-config: 2.3.1::gentoo
dev-lang/perl:5.30.3::gentoo
dev-lang/python: 2.7.18-r2::gentoo, 3.6.11-r2::gentoo,
3.7.8-r2::gentoo, 3.8.5::gentoo
dev-util/ccache: 3.7.11::gentoo
dev-util/cm
--- Stoian Ivanov <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] ~ # emerge -a foomatic-db-engine
USE=-sandbox emerge foomatic-db-engine
See http://bugs.gentoo.org/show_bug.cgi?id=91516
Zac
__
Discover Yahoo!
Find restaurant
Any usage of emerge gets:
ACCESS DENIED open_rd: /root/.bash_history
ACCESS DENIED open_rd: /root/.bash_history
if I:
mv ~/.bash_history ~/.bash_historyX
It works fine.
ls -l ~/.bash_history
-rw--- 1 root root 1841 Dec 24 12:14 /root/.bash_history
I've tried chmodding it
On Fri, 2007-11-09 at 23:09 +0100, Hemmann, Volker Armin wrote:
[...]
> > https://bugs.gentoo.org/show_bug.cgi?id=196720 ?
> >
> > Upgrade sandbox to -r2 ?
>
> -r2 is bugged too:
> http://bugs.gentoo.org/show_bug.cgi?id=198509
BTW I was not able to reproduce #198
On Mon, 10 Nov 2008 09:35:27 +, Peter Humphrey wrote:
> Certainly did - thanks. Now to figure out how to resume the emerge -e
> world from where it stopped :-)
emerge --resume
Single package emerges don't affect the resume list.
--
Neil Bothwick
Do PAL taglines take up two scanlines?
s
> ** Message: pygobject_register_sinkfunc is deprecated (GstObject)
> > > > Progress:
> > > > 00:10
> > > > (null)*(null) (null)ACCESS DENIED(null): mkstemp:
> > > >
> > >
>
/run/user/0/orcexec.XX--
dev-util/cmake: 3.20.5::gentoo
sys-apps/baselayout: 2.7-r3::gentoo
sys-apps/openrc: 0.44.8::gentoo
sys-apps/sandbox: 2.25::gentoo
sys-devel/autoconf: 2.13-r1::gentoo, 2.71-r1::gentoo
sys-devel/automake: 1.16.4::gentoo
sys-devel/binutils: 2.37_p1::gento
entoo
dev-util/meson:1.0.1::gentoo
sys-apps/baselayout: 2.13-r1::gentoo
sys-apps/sandbox: 2.30-r1::gentoo
sys-apps/systemd: 253.4::gentoo
sys-devel/autoconf:2.71-r6::gentoo
sys-devel/automake:1.16.5-r1::gentoo
sys-devel/binutils:
t; > dev-lang/perl: 5.38.2-r3::gentoo
> > dev-lang/python: 3.11.9::gentoo, 3.12.3::gentoo
> > sys-apps/baselayout: 2.15::gentoo
> > sys-apps/openrc: 0.54::gentoo
> > sys-apps/sandbox: 2.38::gentoo
> > sys-devel/binutils:
----------- ACCESS VIOLATION SUMMARY ---
LOG FILE = "/var/log/sandbox/sandbox-26803.log"
open_rd: /root/.bash_history
open_rd: /root/.bash_history
E
1;01mACCESS DENIED [0m
open_wr: /usr/kde/3.5/share/applications/googleearth.desktop
cp: cannot create regular file
`/usr/kde/3.5/share/applications/googleearth.desktop': Permission denied
>>> Completed installing googleearth-4_beta
into /var/tmp/portage/googleearth-4_beta/imag
lso thought it would be safer if I tested them with the
minimum capabilities required. But, it appears that setting that
capability on the python executable (setting it on a .py file is
pointless) breaks the sandbox feature used by emerge.
After removing the NET_RAW capability from /usr/bin/python
da make it better ? Just create that folder??
>
The short answer is to edit make.conf and create a new directory. For
example, here is a copy from my make.conf of the relevant location
(sorry for the line numbers):
FEATURES="collision-protect sandbox ccache userpriv usersandbox buildpkg"
ter ? Just create that folder??
The short answer is to edit make.conf and create a new directory. For
example, here is a copy from my make.conf of the relevant location
(sorry for the line numbers):
FEATURES="collision-protect sandbox ccache userpriv usersandbox buildpkg"
# featur
: /bin/bash -rcfile /usr/share/sandbox/sandbox.bashrc -c
/var/tmp/portage/._portage_reinstall_.um_l05vt/bin/misc-functions.sh
__dyn_instprep
F: open_wr
S: deny
P: /dev/tty
A: /dev/tty
R: /dev/tty
C: /bin/bash
/var/tmp/portage/._portage_reinstall_.um_l05vt/bin/misc-functions.sh
__dyn_instprep
F: open
When I try to emerge gthumb, I get this at the end:
>>> Completed installing gthumb-2.6.3 into /var/tmp/portage/gthumb-2.6.3/image/
--- ACCESS VIOLATION SUMMARY ---
LOG FILE = "/tmp/sandbox-media-gfx_-_gthumb-2.6.3-25558.log"
Pandu Poluan writes:
> In my case, it always fail during the following stage:
>
> chmod
> g+s /var/tmp/portage/sys-apps/util-linux-2.20-r1/image//usr/bin/write
Does this command work when you enter it manually in the chroot?
Maybe FEATURES=-sandbox emerge sys-apps/util
On Mon, 2005-06-06 at 13:13 +0200, Jules Colding wrote:
> --- ACCESS VIOLATION SUMMARY
> ---
> LOG FILE = "/tmp/sandbox-mail-client_-_evolution-2.2.1.1-9278.log"
>
> open_wr: /var/lib/scrollkeeper/scrollkeeper_d
commands
>>> Source configured.
--- ACCESS VIOLATION SUMMARY
---
LOG FILE "/var/log/sandbox/sandbox-15710.log"
VERSION 1.0
FORMAT: F - Function called
FORMAT: S - Access Status
FORMAT: P - Path as passed to function
FORMAT: A - Absolute
x.mod.o
LD
[M]
/var/tmp/portage/ati-drivers-8.32.5/work/common/lib/modules/fglrx/build_mod/fglrx.ko
make[1]: Leaving directory `/usr/src/linux-2.6.19'
>>> Source compiled.
--- ACCESS VIOLATION
SUMMARY -------
LOG FILE
= "/var/log
g.status
config.status: creating clamassassin
config.status: creating Makefile
>>> Source compiled.
--- ACCESS VIOLATION SUMMARY
-------
LOG FILE =
"/var/log/sandbox/sandbox-mail-filter_-_clamassassin-1.2.3-11762.log"
open_
e appreciated.
thanks,
allan
* Messages for package app-misc/ca-certificates-20110502-r1:
* Package:app-misc/ca-certificates-20110502-r1
* Repository: gentoo
* Maintainer: base-sys...@gentoo.org
* USE:amd64 elibc_glibc kernel_linux multilib userland_GNU
* FEATURES: sandbo
too devs are
(supposed to) play in the same sandbox. This means the behaviors of
different packages and their dependencies and interactions with each
other are somewhat predictable, and when problems occur, they are easier
to debug and solve because everyone's playing in the same sandbox.
ystem uname: 2.6.11 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz
Gentoo Base System version 1.6.13
dev-lang/python: 2.3.5, 2.4.1-r1
sys-apps/sandbox:1.2.11
sys-devel/autoconf: 2.13, 2.59-r6
sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9
cs
>path = /home/mp3
>security = share
>writeable = no
>browseable = yes
>guest ok = yes
>printable = no
>guest only = yes
>
> [sandbox]
>comment = Sand Box to genrate releases
>path = /home/sandbox
>
ivileges to
portage:portage during the fetching of package
sources.
userpriv
Allow portage to drop root privileges and compile
packages as portage:portage without a sandbox
entoo
> > Install path/usr
> > Compiler flags:
> > C -march=native -O -pipe
> > C++
> > Linker flags:
> > Executable -Wl,-O1 -Wl,--as-needed
> > Module -Wl,-O1 -Wl,--as-needed
> > Shared -Wl,-O1 -Wl,--as-needed
On Fri, Jun 23, 2017 at 6:58 AM, Michael Orlitzky wrote:
>
> If you're worried about this stuff (and have network namespace support
> built-in to your kernel), you can set FEATURES="network-sandbox" in your
> make.conf to prevent ebuilds from accessing the network. The
ys-apps/baselayout: 2.7::gentoo
sys-apps/openrc: 0.42.1-r1::gentoo
sys-apps/sandbox: 2.20::gentoo
sys-devel/autoconf: 2.13-r1::gentoo, 2.69-r5::gentoo
sys-devel/automake: 1.16.2-r1::gentoo
sys-devel/binutils: 2.34-r2::gentoo, 2.35.1-r1::gentoo
sys-devel/gcc:
5::gentoo
sys-apps/baselayout: 2.7::gentoo
sys-apps/openrc: 0.42.1-r1::gentoo
sys-apps/sandbox: 2.22::gentoo
sys-devel/autoconf: 2.69-r5::gentoo
sys-devel/automake: 1.16.2-r1::gentoo
sys-devel/binutils: 2.35.2::gentoo
sys-devel/gcc: 10.2.0-r5::gentoo
s
gentoo, 3.11.2_p2::gentoo
dev-lang/rust-bin: 1.66.1-r1::gentoo
dev-util/cmake:3.25.3::gentoo
dev-util/meson:1.0.1::gentoo
sys-apps/baselayout: 2.13-r1::gentoo
sys-apps/openrc: 0.46::gentoo
sys-apps/sandbox: 2.29::gentoo
sys-devel/au
son:1.0.1::gentoo
sys-apps/baselayout: 2.13-r1::gentoo
sys-apps/sandbox: 2.30-r1::gentoo
sys-apps/systemd: 253.4::gentoo
sys-devel/autoconf:2.71-r6::gentoo
sys-devel/automake:1.16.5-r1::gentoo
sys-devel/binutils:2.40-r5::gentoo
sys
7;/var/tmp/portage/dev-python/setuptools-0.6_rc8-r1/temp/environment'.
*
--- ACCESS VIOLATION SUMMARY
--- LOG FILE =
"/var/log/sandbox/sandbox-32513.log"
open_wr: /usr/lib64/python2.6/site-packages/pkg_resources.py
-
-O1 -Wl,--as-needed
> Shared -Wl,-O1 -Wl,--as-needed
>
> -- Configuring done
> -- Generating done
> -- Build files have been written to:
> /var/tmp/portage/media-libs/libjpeg-turbo-2.0.1/work/libjpeg-turbo-2.0.1-abi_x86_64.amd64
> >>> Source configured.
> * ---
On Mon, 2005-06-06 at 13:38 +0200, Jules Colding wrote:
> On Mon, 2005-06-06 at 13:13 +0200, Jules Colding wrote:
> > --- ACCESS VIOLATION SUMMARY
> > ---
> > LOG FILE = "/tmp/sandbox-mail-client_-_evolution-2.2.1.1-
Neil Bothwick wrote:
On Thu, 17 Nov 2011 03:17:23 -0600, Dale wrote:
FEATURES="buildpkg sandbox parallel-fetch --keep-going"
Shouldn't --keep-going be in EMERGE_DEFAULT_OPTS?
It should and it was. I must have pasted it from somewhere and not
noticed it. No need in i
_NASM compiler identification is NASM
> > > -- Found assembler: /usr/bin/nasm
> > > -- CMAKE_ASM_NASM_COMPILER = /usr/bin/nasm
> > > -- CMAKE_ASM_NASM_OBJECT_FORMAT = elf64
> > > -- CMAKE_ASM_NASM_FLAGS = -DELF -D__x86_64__ -DPIC
> > > -- SIMD exten
201 - 300 of 1473 matches
Mail list logo
