public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Harry Holt" <harryholt@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: gcc 4.1.1 access violation
Date: Sat, 28 Oct 2006 18:54:10 -0400	[thread overview]
Message-ID: <7c8072a00610281554r5cead30ake9f071d01e20620@mail.gmail.com> (raw)
In-Reply-To: <200610281108.21396.volker.armin.hemmann@tu-clausthal.de>

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

Well, I'm trying with gcc 4.1.1, not 4.1.1-r1 (it's masked), but if I can't
get this to work I'll try that one.  The problem is the 3-hour compile until
the error shows up.  I'm still unclear why the ebuild postinst / qmerge does
not work - it doesn't seem to put everything in place like it should (still
have broken libs, etc.).

... HH

On 10/28/06, Hemmann, Volker Armin <volker.armin.hemmann@tu-clausthal.de>
wrote:
>
> On Saturday 28 October 2006 07:02, Duncan wrote:
>
> > You /could/ try turning sandbox off (in FEATURES).  That's a bit
> dangerous
> > by itself, but if you turn userpriv on at the same time, it should be
> > fairly safe.
>
> NO!
>
> Just no!
>
> Never ever turn of sandbox. Without sandbox, files can end everywhere in
> your
> installation, destroying stuff, make apps segfault randomly - and the
> worst,
> portage does not know about them.
>
> Never ever turn of sandbox. And never tell others to do so.
> btw
> *  sys-devel/gcc
>       Latest version available: 4.1.1-r1
>       Latest version installed: 4.1.1-r1
>
> and I have sandbox enabled. So it is not a sandbox problem. Something else
> is
> broken on his system.
> --
> gentoo-amd64@gentoo.org mailing list
>
>


-- 
Harry Holt, PMP

[-- Attachment #2: Type: text/html, Size: 1711 bytes --]

  parent reply	other threads:[~2006-10-28 22:56 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 [this message]
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
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=7c8072a00610281554r5cead30ake9f071d01e20620@mail.gmail.com \
    --to=harryholt@gmail.com \
    --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