We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
gcc-3.3 | 1:3.3.6ds1-18 | source
libstdc++5 | 1:3.3.6-18 | amd64, i386, powerpc
Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in
LAST_UPDATED: Obtained from SVN: branches/gcc-4_3-branch revision 150451
Native configuration is arm-unknown-linux-gnueabi
=== libgomp tests ===
Running target unix
=== libgomp Summary ===
# of expected passes1749
# of unsupported tests 7
On Sun, Aug 16, 2009 at 04:00:34PM +0200, Bill Allombert wrote:
> Package: gcc-4.4
> Version: 4.4.1-2
> Severity: important
>
> Hello Debian GCC Maintainers,
>
> Compiling the file linked below (on amd64)
> http://people.debian.org/~ballombe/misc/gcc44bug.i.gz
> with
> gcc-4.4 -c -O2 -Wall -fno-s
FYI: The status of the cloog-ppl source package
in Debian's testing distribution has changed.
Previous version: 0.15-1
Current version: 0.15-2
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will receive
Package: libcloog-ppl-dev
Version: 0.15-2
Severity: normal
In config.log for GCC 4.5, I see the following:
configure:5356: checking for correct version of CLooG
configure:5378: gcc -c -g -O2 conftest.c >&5
In file included from conftest.c:12:
/usr/include/cloog/cloog.h:47:30: error: polylib/
Package: gcc-4.4
Version: 4.4.1-2
Severity: important
Hello Debian GCC Maintainers,
Compiling the file linked below (on amd64)
http://people.debian.org/~ballombe/misc/gcc44bug.i.gz
with
gcc-4.4 -c -O2 -Wall -fno-strict-aliasing -o base3.o gcc44bug.i
cause gcc to eat all available memory and die.
Heya,
As announced on dda [RT1], we want to get an impression when releasing
Squeeze is feasible. We have proposed a (quite ambitious) freeze in December
2009, and some developers have noted that their planned changes wouldn't be
possible in this time frame. So, to find out when releasing would wo
Package: lib32mudflap0
Version: 4.4.1-1
Severity: normal
I got this today after running aptitude dist-upgrade (after returning from a 2
week holiday):
Writing extended state information... Done
E: Couldn't configure pre-depend libc6-i386 for lib32mudflap0, probably a
dependency cycle.
A package
Matthias Klose wrote:
> On 29.04.2009 04:49, Florian Weimer wrote:
>> * Florian Weimer:
>>
>>> I've asked the FSF for a clarification (the second time, the first
>>> clarification resulted in the Java bytecode exception). Until we know
>>> for sure how to interpret the exception, it's probably bes
9 matches
Mail list logo
