From: Francesco Talamona <ti.liame@email.it>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Re: gcc 4.1.1 access violation
Date: Mon, 30 Oct 2006 20:52:32 +0100 [thread overview]
Message-ID: <200610302052.32944.ti.liame@email.it> (raw)
In-Reply-To: <200610302019.28862.volker.armin.hemmann@tu-clausthal.de>
On Monday 30 October 2006 20:19, Hemmann, Volker Armin wrote:
> you have experienced it. You just don't see it. Somewhere in your
> filesystem are files, that should not be there. Files, that portage
> does not know about and that won't be removed, when the package gets
> uninstalled.
I ran findcruft some months ago, and it found some cruft around, but
nothing really dangerous. Of course was impossible to track back every
mud spot...
> If a package does not build with sandbox, it is broken. Open a bug.
Anyway, I just followed your advice and unset "-sandbox" fom my
FEATURES. I really don't need it (anymore).
If anything tries to escape its sandbox should be considered potentially
dangerous, lesson learned.
Thanks
Francesco
--
Linux Version 2.6.18-gentoo-r1, Compiled #1 PREEMPT Wed Oct 18 22:52:55
CEST 2006
One 1.8GHz AMD Athlon 64 Processor, 2GB RAM, 3607.13 Bogomips Total
aemaeth
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2006-10-30 19:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-27 23:20 [gentoo-amd64] gcc 4.1.1 access violation Harry Holt
2006-10-28 5:02 ` [gentoo-amd64] " Duncan
2006-10-28 9:08 ` Hemmann, Volker Armin
2006-10-28 19:15 ` Duncan
2006-10-28 22:54 ` Harry Holt
2006-10-29 3:41 ` Harry Holt
2006-10-29 3:51 ` Hemmann, Volker Armin
2006-10-29 4:01 ` Harry Holt
2006-10-30 18:57 ` Francesco Talamona
2006-10-30 19:19 ` Hemmann, Volker Armin
2006-10-30 19:37 ` Vladimir G. Ivanovic
2006-10-30 19:52 ` Francesco Talamona [this message]
2007-02-09 21:06 ` Harry Holt
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=200610302052.32944.ti.liame@email.it \
--to=ti.liame@email.it \
--cc=gentoo-amd64@lists.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