Bug#151886: [Gcl-devel] Re: gcl/maxima on hppa

2002-10-09 Thread Camm Maguire
Greetings! I'm pleased to announce that gcl/maxima is now supported in hppa, the last of the 11 Debian architectures. The issues were/are with gcc on this platform, and were masked somewhat by my not setting up gcl's internal compile flags correctly. 1) When compiling with -g, the final link fai

Bug#151886: [Gcl-devel] Re: gcl/maxima on hppa

2002-10-09 Thread Randolph Chung
> 1) When compiling with -g, the final link fails, and explicitly asks >for recompilation with -ffunction-sections. This works, and >produces a maxima passing all tests. known problem with gcc-3.0.x > 2) Any optimization at all breaks the build. I have a gdb >session/backtrace showi

Bug#151886: [Gcl-devel] Re: gcl/maxima on hppa

2002-10-09 Thread Camm Maguire
Greetings! An update: 1) Optimization, even at -O, still fails with gcc-3.2. I get a maxima, but it crashes on one of the tests. -ffunction-sections still in. 2) I cannot seem to get gcl's stratified garbage collection option to work on hppa. This basically mprotects the core pages as

Bug#164009: gcj-3.2: gcj-wrapper-3.2 omits input files starting with .

2002-10-09 Thread Adam C Powell IV
Package: gcj-3.2 Version: 1:3.2.1-0pre3 Severity: important Greetings, javac ./hello.java fails because the script only allows a-zA-Z_/ as initial characters in input files. This seems to fix it: diff -u /usr/bin/gcj-wrapper-3.2 ./gcj-wrapper-3.2 --- /usr/bin/gcj-wrapper-3.22002-09-19 16:36:

Bug#159838: c/7853: gcc reports multiple symbol definitions on the wrong line

2002-10-09 Thread ljrittle
Synopsis: gcc reports multiple symbol definitions on the wrong line State-Changed-From-To: open->closed State-Changed-By: ljrittle State-Changed-When: Wed Oct 9 15:31:26 2002 State-Changed-Why: Fixed on mainline according to Peter Schmid. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20aud

bison 1.50-1

2002-10-09 Thread Jack Howarth
Matthias, You might want to do a test build of gcc-3.2.1 against the new bison 1.50-1. I have found that this new bison breaks the binutils build. Not sure yet if this is a bison bug or a flaw in the binutils build process. Hopefully not that may packages will be bit by this. Regressing to biso

Bug#159838: c/7853: gcc reports multiple symbol definitions on the wrong line

2002-10-09 Thread ljrittle
Synopsis: gcc reports multiple symbol definitions on the wrong line State-Changed-From-To: closed->open State-Changed-By: ljrittle State-Changed-When: Wed Oct 9 18:25:47 2002 State-Changed-Why: Undo, not fixed yet. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr