[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-amd64
Subject:    Re: [gentoo-amd64] Re: gcc 4.1.1 access violation
From:       "Harry Holt" <harryholt () gmail ! com>
Date:       2007-02-09 21:06:10
Message-ID: 7c8072a00702091306n6ea22009reabcba2b7fd145ec () mail ! gmail ! com
[Download RAW message or body]

Yikes!  This is still happening with gcc-4.1.1-r3.  Everything else works
fine.  I haven't had any problems with installing and updating.  Today I did
a emerge --update --deep --newuse system.  I noticed GCC at the bottom of
the list, but figured maybe it was an anomaly before.  Still no go.

I'm going to continue to just manually install the files from the sandbox
image, which oddly enough works just fine.  I seem to be the only person
having this problem!

... HH

On 10/30/06, Francesco Talamona <ti.liame@email.it> wrote:
>
> 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
>
>


-- 
Harry Holt, PMP

[Attachment #3 (text/html)]

Yikes!&nbsp; This is still happening with gcc-4.1.1-r3.&nbsp; Everything else works \
fine.&nbsp; I haven&#39;t had any problems with installing and updating.&nbsp; Today \
I did a emerge --update --deep --newuse system.&nbsp; I noticed GCC at the bottom of \
the list, but figured maybe it was an anomaly before.&nbsp; Still no go. \
<br><br>I&#39;m going to continue to just manually install the files from the sandbox \
image, which oddly enough works just fine.&nbsp; I seem to be the only person having \
this problem!<br><br>... HH<br><br><div><span class="gmail_quote"> On 10/30/06, <b \
class="gmail_sendername">Francesco Talamona</b> &lt;<a \
href="mailto:ti.liame@email.it">ti.liame@email.it</a>&gt; wrote:</span><blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt \
0pt 0.8ex; padding-left: 1ex;"> On Monday 30 October 2006 20:19, Hemmann, Volker \
Armin wrote:<br>&gt; you have experienced it. You just don&#39;t see it. Somewhere in \
your<br>&gt; filesystem are files, that should not be there. Files, that \
portage<br>&gt; does not know about and that won&#39;t be removed, when the package \
gets <br>&gt; uninstalled.<br>I ran findcruft some months ago, and it found some \
cruft around, but<br>nothing really dangerous. Of course was impossible to track back \
every<br>mud spot...<br><br>&gt; If a package does not build with sandbox, it is \
broken. Open a bug. <br>Anyway, I just followed your advice and unset \
&quot;-sandbox&quot; fom my<br>FEATURES. I really don&#39;t need it \
(anymore).<br><br>If anything tries to escape its sandbox should be considered \
potentially<br>dangerous, lesson learned. \
<br><br>Thanks<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Francesco<br>--<br>Linux \
Version 2.6.18-gentoo-r1, Compiled #1 PREEMPT Wed Oct 18 22:52:55<br>CEST 2006<br>One \
1.8GHz AMD Athlon 64 Processor, 2GB RAM, 3607.13 Bogomips Total<br>aemaeth<br>--<br> \
<a href="mailto:gentoo-amd64@gentoo.org">gentoo-amd64@gentoo.org</a> mailing \
list<br><br></blockquote></div><br><br clear="all"><br>-- <br>Harry Holt, PMP


-- 
gentoo-amd64@gentoo.org mailing list


[prev in list] [next in list] [prev in thread] [next in thread]