List Info

Thread: gcc 4.1.1 access violation




gcc 4.1.1 access violation
user name
2006-10-30 19:19:28
On Monday 30 October 2006 19:57, Francesco Talamona wrote:
> On Saturday 28 October 2006 11:08, Hemmann, Volker
Armin 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.
>
> I'm running -sandbox since 09-June-2005, am I in such a
danger?
> Shouldn't I have experienced destructive issues in the
meantime?
> FEATURES="candy ccache buildpkg fixpackages
-sandbox"
>

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.

If a package does not build with sandbox, it is broken. Open
a bug.
-- 
gentoo-amd64gentoo.org mailing list

[1]

about | contact  Other archives ( Real Estate discussion Medical topics )