Re: Moving ARM g77 to g77-3.0

2002-02-27 Thread Matthias Klose
Philip Blundell writes: > On Wed, 2002-02-27 at 19:27, Matthias Klose wrote: > > Philip Blundell writes: > > > On Wed, 2002-02-27 at 17:04, Adam C Powell IV wrote: > > > > 3.0 fixes this problem, but then maintainers must hand-build using > > > > g77-3.0, which is not a viable long-term solution.

Re: Moving ARM g77 to g77-3.0

2002-02-27 Thread Philip Blundell
On Wed, 2002-02-27 at 19:27, Matthias Klose wrote: > Philip Blundell writes: > > On Wed, 2002-02-27 at 17:04, Adam C Powell IV wrote: > > > 3.0 fixes this problem, but then maintainers must hand-build using > > > g77-3.0, which is not a viable long-term solution. I know some arches > > > have 3.

Re: Moving ARM g77 to g77-3.0

2002-02-27 Thread Matthias Klose
Philip Blundell writes: > On Wed, 2002-02-27 at 17:04, Adam C Powell IV wrote: > > 3.0 fixes this problem, but then maintainers must hand-build using > > g77-3.0, which is not a viable long-term solution. I know some arches > > have 3.0 as their default compiler. So, what are the criteria, and

Re: Moving ARM g77 to g77-3.0

2002-02-27 Thread Philip Blundell
On Wed, 2002-02-27 at 17:04, Adam C Powell IV wrote: > 3.0 fixes this problem, but then maintainers must hand-build using > g77-3.0, which is not a viable long-term solution. I know some arches > have 3.0 as their default compiler. So, what are the criteria, and > what's the procedure, for cha

Moving ARM g77 to g77-3.0

2002-02-27 Thread Adam C Powell IV
Greetings, g77-2.95 has a nasty bug on ARM which prevents linking of any FORTRAN libs (#90363). Our current status is that all packages with binaries which link to FORTRAN libs fail to build! This bug is not likely to be fixed. 3.0 fixes this problem, but then maintainers must hand-build usin

Bug#135943: r-recommended_1.4.1-1 fails to autobuild on m68k

2002-02-27 Thread Dirk Eddelbuettel
On Wed, Feb 27, 2002 at 04:16:36PM +, Phil Blundell wrote: > On Wed, 2002-02-27 at 13:03, Dirk Eddelbuettel wrote: > > On Wed, Feb 27, 2002 at 12:29:15PM +, Phil Blundell wrote: > > > On Wed, 2002-02-27 at 02:40, Dirk Eddelbuettel wrote: > > > > gcc -I/usr/lib/R/include -fPIC -g -O2 -c

warning on valid escape sequence in C string & invalid result.

2002-02-27 Thread cwryu
>Submitter-Id: net >Originator:Changwoo Ryu >Organization: >Confidential: no >Synopsis: warning on valid escape sequence in C string & invalid result. >Severity: serious >Priority: low >Category: c >Class: wrong-code >Release: 3.0.4 (Debian testing/unstabl

warning on valid escape sequence in C string & invalid result.

2002-02-27 Thread cwryu
>Submitter-Id: net >Originator:Changwoo Ryu >Organization: >Confidential: no >Synopsis: warning on valid escape sequence in C string & invalid result. >Severity: serious >Priority: low >Category: c >Class: wrong-code >Release: 3.0.4 (Debian testing/unstabl

Bug#135943: r-recommended_1.4.1-1 fails to autobuild on m68k

2002-02-27 Thread Phil Blundell
On Wed, 2002-02-27 at 13:03, Dirk Eddelbuettel wrote: > On Wed, Feb 27, 2002 at 12:29:15PM +, Phil Blundell wrote: > > On Wed, 2002-02-27 at 02:40, Dirk Eddelbuettel wrote: > > > gcc -I/usr/lib/R/include -fPIC -g -O2 -c coxfit2.c -o coxfit2.o > > > coxfit2.c: In function `coxfit2': > > > c

Bug#135943: r-recommended_1.4.1-1 fails to autobuild on m68k

2002-02-27 Thread Dirk Eddelbuettel
On Wed, Feb 27, 2002 at 12:29:15PM +, Phil Blundell wrote: > On Wed, 2002-02-27 at 02:40, Dirk Eddelbuettel wrote: > > gcc -I/usr/lib/R/include -fPIC -g -O2 -c coxfit2.c -o coxfit2.o > > coxfit2.c: In function `coxfit2': > > coxfit2.c:352: Internal compiler error: > > coxfit2.c:352: intern

Bug#135943: Processed: Re: Bug#135943: r-recommended_1.4.1-1 fails to autobuild on m68k

2002-02-27 Thread Dirk Eddelbuettel
On Wed, Feb 27, 2002 at 07:35:32AM +0100, Matthias Klose wrote: > Debian Bug Tracking System writes: > > Processing commands for [EMAIL PROTECTED]: > > > > > reassign 135943 gcc > > Bug#135943: r-recommended_1.4.1-1 fails to autobuild on m68k > > Bug reassigned from package `r-recommended' to `gcc

Bug#136045: marked as done (Unable to compile large source trees)

2002-02-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Feb 2002 13:33:38 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#136045: Unable to compile large source trees 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

Bug#135943: r-recommended_1.4.1-1 fails to autobuild on m68k

2002-02-27 Thread Phil Blundell
On Wed, 2002-02-27 at 02:40, Dirk Eddelbuettel wrote: > gcc -I/usr/lib/R/include -fPIC -g -O2 -c coxfit2.c -o coxfit2.o > coxfit2.c: In function `coxfit2': > coxfit2.c:352: Internal compiler error: > coxfit2.c:352: internal error--unrecognizable insn: > (insn 2883 243 245 (set (reg:DF 16 %fp0)

Bug#136045: Unable to compile large source trees

2002-02-27 Thread Thomas Viehweger
Package: g++-2.95 Hi, when I try to compile for example qt-x11 (with debian/rules binary-arch) after some time the build process stops with an error message like: g++ -D_REENTRANT -DQT_THREAD_SUPPORT -c -I/usr/X11R6/include -I/usr/src/qt-x11-2.3.1/include -I/usr/X11R6/include -pipe -fno-exceptions

Bug#135943: marked as done (gcc on m68k has internal error in coxfit2.c in survival in r-recommended)

2002-02-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Feb 2002 00:13:15 -0800 with message-id <[EMAIL PROTECTED]> and subject line Processed: Re: Bug#135943: r-recommended_1.4.1-1 fails to autobuild on m68k has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt wi

Bug#135943: Processed: Re: Bug#135943: r-recommended_1.4.1-1 fails to autobuild on m68k

2002-02-27 Thread Matthias Klose
Debian Bug Tracking System writes: > Processing commands for [EMAIL PROTECTED]: > > > reassign 135943 gcc > Bug#135943: r-recommended_1.4.1-1 fails to autobuild on m68k > Bug reassigned from package `r-recommended' to `gcc'. > > > retitle 135943 gcc on m68k has internal error in coxfit2.c in surv