GCC segfault very often if LANG!=C

2003-03-28 Thread Benjamin Dauvergne
Hello, Could I suggest you to compile GCC with --disable-nls or without packaging certain translations like french because they causes bug in gcc/g++ when error messages must be printed. It's a known bug in the bug database of gcc[1]. Without that french user must force LANG=C only

Re: GCC segfault very often if LANG!=C

2003-03-28 Thread Martin v. Lwis
Benjamin Dauvergne [EMAIL PROTECTED] writes: Could I suggest you to compile GCC with --disable-nls or without packaging certain translations like french because they causes bug in gcc/g++ when error messages must be printed. It's a known bug in the bug database of gcc[1]. Without

Bug#185779: libstdc++/10257: libstdc++ breaks when NetBSD is build with -lc in LIB_SPEC shared

2003-03-28 Thread gcc-gnats
Thank you very much for your problem report. It has the internal identification `libstdc++/10257'. The individual assigned to look at your report is: unassigned. Category: libstdc++ Responsible:unassigned Synopsis: libstdc++ breaks when NetBSD is build with -lc in LIB_SPEC

Bug#186667: gcc-3.3_1:3.3ds2-0pre2(testing/ia64): FTBFS:

2003-03-28 Thread Bdale Garbee
Package: gcc-3.3 Version: 1:3.3ds2-0pre2 Severity: important This package fails on the ia64 autobuilder as shown below. Bdale | Automatic build of gcc-3.3_1:3.3ds2-0pre2 on caballero by sbuild/ia64 1.169 | Build started at 20030328-1558 [...] | stage1/xgcc -Bstage1/ -B/usr/ia64-linux/bin/ -c

Processed: Re: Bug#168310: Still broken?

2003-03-28 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: reopen 168310 Bug#168310: [PR c++/8598] xmmintrin.h broken for c++ Bug reopened, originator not changed. retitle 168310 [fixed in 3.3] [PR c++/8598] xmmintrin.h broken for c++ Bug#168310: [PR c++/8598] xmmintrin.h broken for c++ Changed Bug title.

Bug#168310: Still broken?

2003-03-28 Thread Matthias Klose
reopen 168310 retitle 168310 [fixed in 3.3] [PR c++/8598] xmmintrin.h broken for c++ thanks you are right. this won't be fixed for 3.2. Torgeir Strand Henriksen writes: I still get the error after upgrading to 3.2.3-0pre6.