Re: GCC 4.1 in experimental / GCC for etch

2006-02-21 Thread Aurelien Jarno
[I have done s/ports/hppa/ in the Cc: list] Randolph Chung a écrit : For hppa, the glibc builds well with gcc 4.0, but create problem with python/perl. It still has to be investigated. Can you explain what the problems are (or at least the symptoms) so that we can look into them? Are there an

Re: GCC 4.1 in experimental / GCC for etch

2006-02-21 Thread Randolph Chung
> For hppa, the glibc builds well with gcc 4.0, but create problem with > python/perl. It still has to be investigated. Can you explain what the problems are (or at least the symptoms) so that we can look into them? Are there any bugs filed on this? thanks randolph -- Randolph Chung Debian GNU/L

Re: GCC 4.1 in experimental / GCC for etch

2006-02-21 Thread Ludovic Brenta
Matthias Klose <[EMAIL PROTECTED]> writes: > Still open points are > > - GNAT maintainance. Supposed to be based on 4.1. The GNAT maintainer > isn't a DD yet (after more than a year of GNAT maintainance in > Debian I'm loosing trust in our NM process). I'm that person. I started GNAT maintena

howz going

2006-02-21 Thread Shawn M. Stephan, VI
Hows it been going? We guar#ant#ee 100% t0p-qua1ity of a11 products.=20 Convenience 0f ordering from H0MmeE or office at time that suits you. L0vvest prce on brAnNnD name and gen_er#!c drvg= sss. copy the address below and

Bug#345821: marked as done (libstdc++6: Documentation bug in ext/stdio_filebuf.h)

2006-02-21 Thread Debian Bug Tracking System
Your message dated Tue, 21 Feb 2006 18:12:15 + with message-id <[EMAIL PROTECTED]> and subject line Close has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Re: GCC 4.1 in experimental / GCC for etch

2006-02-21 Thread Moritz Muehlenhoff
Matthias Klose wrote: > - Once the 4.1 packages are migrated to testing, make 4.1 the default > compiler for i386, amd64, powerpc. GCC 4.1 has lightweight protective measures against stack overflows. Is this something that must be explicitly activated by maintainers through compiler flags or wil

Re: GCC 4.1 in experimental / GCC for etch

2006-02-21 Thread Wouter Verhelst
On Tue, Feb 21, 2006 at 11:34:55AM +0100, Aurelien Jarno wrote: > For m68k, the glibc does not build, gcc 4.0 segfault on system.c. It > looks like gcc 4.1 fixes the problem, but the resulting glibc has not > been tested. Many m68k ICEs are fixed by GCC 4.1. I intend to switch over quickstep (th

Re: GCC 4.1 in experimental / GCC for etch

2006-02-21 Thread Robert Millan
On Tue, Feb 21, 2006 at 11:34:55AM +0100, Aurelien Jarno wrote: > >- Once the 4.1 packages are migrated to testing, make 4.1 the default > > compiler for i386, amd64, powerpc. These are the architectures, > > which are considred primary (linux) architectures by GCC upstream. > > For the other De

Re: GCC 4.1 in experimental / GCC for etch

2006-02-21 Thread Matthias Klose
Aurelien Jarno writes: > The GCC website seems to be down currently, could you please tell us > when the release are expected? as usually: when its ready. maybe in February. > > - Stop building compiler packages from the GCC 3.3 source; the only > > packages built will be libstdc++5 (and libgc

Re: GCC 4.1 in experimental / GCC for etch

2006-02-21 Thread Aurelien Jarno
Hi! Matthias Klose a écrit : The GCC (GNU compiler collection) 4.1 release candidate 1 can be found in experimental. "Porters", please make sure that the package is built and uploaded (if it's not built by the experimental buildd). Please check that the symbols exported in the 4.1 libraries are