On Tue, May 11, 2004 at 12:20:16AM +0200, Matthias Klose wrote:
> John Goerzen writes:
> > On Mon, May 10, 2004 at 10:41:02PM +0200, Frederik Schueler wrote:
> > > I have some questions:
> > >
> > > 1. when does the gcc maintainer team plan to release 3.4 to un
On Mon, May 10, 2004 at 05:06:05PM -0400, Stephen Frost wrote:
> * John Goerzen ([EMAIL PROTECTED]) wrote:
> > On Mon, May 10, 2004 at 10:41:02PM +0200, Frederik Schueler wrote:
> > > 3. is pure64 going to be included in sarge?
> >
> > No.
>
> Honestly, I&#
On Mon, May 10, 2004 at 10:41:02PM +0200, Frederik Schueler wrote:
> I have some questions:
>
> 1. when does the gcc maintainer team plan to release 3.4 to unstable?
>
> 2. will gcc-3.4 be included in sarge?
Highly doubtful.
> 3. is pure64 going to be included in sarge?
No.
>gcc-3.4 will
it to unstable on alioth?
>
> As I understand it, from the amd64 side we really don't want to get
> ahead of unstable because it makes things much more difficult later to
> get things into the archive if we actually get space on the mirrors...
> I'm not 100% sure though, John Goerzen knows more about that.
>
> Stephen
Package: gcc-3.3
Version: 1:3.3.2-4
Severity: normal
The -mcpu and -march options seem to only describe ARM on 3.3.1 and
Sparc on 3.2.1. This is an x86 machine, however.
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux wile 2.4.22 #2 Wed Nov 26 10:41:26 CS
Package: libstdc++2.10-glibc2.2
Version: 1:2.95.4-14
Severity: grave
When I upgrade from -7, I get problems like this all over:
# python2.2
python2.2: error while loading shared libraries: libstdc++-libc6.2-2.so.3:
cannot open shared object file: No such file or directory
Even things like apt-ge
6 matches
Mail list logo
