Gentoo Archives: gentoo-amd64

From: Harry Holt <harryholt@×××××.com>
To: gentoo-amd64@l.g.o
Subject: Re: [gentoo-amd64] Re: gcc 4.1.1 access violation
Date: Sun, 29 Oct 2006 03:43:42
Message-Id: 7c8072a00610282041m4bd470e7idc4c08522895c68@mail.gmail.com
In Reply to: Re: [gentoo-amd64] Re: gcc 4.1.1 access violation by Harry Holt
1 Hmmm... Same error with 4.1.1-r1, so... sandbox issue? Why would the
2 install try to mess with crt1.o? It's not on the list of files for GCC.
3
4
5 On 10/28/06, Harry Holt <harryholt@×××××.com> wrote:
6 >
7 > Well, I'm trying with gcc 4.1.1, not 4.1.1-r1 (it's masked), but if I
8 > can't get this to work I'll try that one. The problem is the 3-hour compile
9 > until the error shows up. I'm still unclear why the ebuild postinst /
10 > qmerge does not work - it doesn't seem to put everything in place like it
11 > should (still have broken libs, etc.).
12 >
13 > ... HH
14 >
15 > On 10/28/06, Hemmann, Volker Armin <volker.armin.hemmann@××××××××××××.de>
16 > wrote:
17 > >
18 > > On Saturday 28 October 2006 07:02, Duncan wrote:
19 > >
20 > > > You /could/ try turning sandbox off (in FEATURES). That's a bit
21 > > dangerous
22 > > > by itself, but if you turn userpriv on at the same time, it should be
23 > > > fairly safe.
24 > >
25 > > NO!
26 > >
27 > > Just no!
28 > >
29 > > Never ever turn of sandbox. Without sandbox, files can end everywhere in
30 > > your
31 > > installation, destroying stuff, make apps segfault randomly - and the
32 > > worst,
33 > > portage does not know about them.
34 > >
35 > > Never ever turn of sandbox. And never tell others to do so.
36 > > btw
37 > > * sys-devel/gcc
38 > > Latest version available: 4.1.1-r1
39 > > Latest version installed: 4.1.1-r1
40 > >
41 > > and I have sandbox enabled. So it is not a sandbox problem. Something
42 > > else is
43 > > broken on his system.
44 > > --
45 > > gentoo-amd64@g.o mailing list
46 > >
47 > >
48 >
49 >
50 > --
51 > Harry Holt, PMP
52
53
54
55
56 --
57 Harry Holt, PMP

Replies