That's really bizarre. I built 0.8.9-2 exactly as before, using
autotools so the shared libs are built with -fPIC and static libs
without it automatically, etc.
The bug is not in illuminator, but somewhere else. Any ideas on how to
track this down? You say it appeared in libluminate3, which wou
Greetings,
I was looking through debian-gcc and debian-java for threads on gcc-3.4
inclusion in sarge, and came across "gcc-3.4 to [sic] unstable for
amd64" with a post from jgoerzen:
---
> 2. will gcc-3.4 be included in sarge?
Highly doubtful.
> 3. is pure64 going to be included in sarge?
No
Hello again,
The newest gcj-3.3 now compiles babel just fine (as mentioned when
closing Debian bug 209283). A new bug in kaffe's jar prevents the
archive from building. But when fastjar (from gcj) is used instead of
kaffe jar, it builds just fine, and kaffe's JVM runs it just fine; the
babel tes
On Wed, 2003-11-19 at 16:13, Falk Hueffner wrote:
> Adam C Powell IV <[EMAIL PROTECTED]> writes:
>
> > gcj-3.3 ICEs during at attempted build of babel 0.8.8. The compile
> > command is quite ugly:
> >
> > javac -g -d . -classpath
> > ../lib/java-getop
Package: gcj-3.3
Version: 3.3.2-4
Severity: normal
Greetings,
gcj-3.3 ICEs during at attempted build of babel 0.8.8. The compile
command is quite ugly:
javac -g -d . -classpath
../lib/java-getopt-1.0.7.jar:../lib/xerces-2.4.0.jar:../lib/jcert-1.0.1.jar:../lib/jnet-1.0.1.jar:../lib/external/jsse
Yup, that's the problem.
Babel is an SIDL compiler; SIDL is an IDL like CORBA. Babel is
implemented in Java, and needs to run in order to generate the stub
files for its runtime front ends in C, C++, F77, and python (equivalent
to, say, liborbit.a, etc.). So the babel shell script uses kaffe to
reopen 197090
reassign 197090 kaffe
retitle 197090 Assertion failure during babel run/build
thanks
Hello,
On Fri, 2003-10-10 at 04:45, Matthias Klose wrote:
> babel builds with current gcj-3.3, but the "javadoc-gjdoc" build dep
> doesn't exist anymore.
Unfortunately, though the babel.jar archive
On Fri, 2003-06-13 at 09:11, Tom Tromey wrote:
> > "Matthias" == Matthias Klose <[EMAIL PROTECTED]> writes:
>
> Matthias> This report is very vague. Should it be submitted to bugzilla
> anyway?
>
> Could you get more info first?
> Ideally the reporter could find out exactly what goes wrong.
Package: gcj-3.3
Version: 1:3.3-3
Severity: normal
Hello,
Okay, so this is kind of a vague bug at this point, but here's what I
know: with gcj-3.2 installed, babel compiles and runs just fine; with
gcj-3.3, it compiles but fails at runtime using kaffe.
Here's the runtime error:
/usr/bin/java -a
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:
reopen 136359
thanks
This is not fixed. That 3.0 works is good to know, but that is not the
default alpha fortran compiler. Feel free to note that this is fixed in
3.0, or retitle it to reflect that, but g77-2.95 still has this problem.
I am working on a fix for g77-2.95, and will report it wi
Matthias Klose wrote:
Adam C Powell IV writes:
reopen 136359
thanks
Thank you for your patience in this, I'm sorry to be such a pain in the
neck. But it still doesn't work, I'm still getting a SIGFPE in
f__cabs() from cabs.c in libg2c...
Okay, I think I see what's goi
Hello Matthias, Chris (et al.),
Christopher C. Chimelis wrote:
On Tue, 12 Mar 2002, Matthias Klose wrote:
please send a patch. I don't have access on an alpha and cannot easily
see the layout. Or maybe Chris could give it a try?
I can try, but am VERY tight on time this week and possibly next. Ad
reopen 136359
thanks
Thank you for your patience in this, I'm sorry to be such a pain in the
neck. But it still doesn't work, I'm still getting a SIGFPE in
f__cabs() from cabs.c in libg2c...
Okay, I think I see what's going on. In the alpha build log, there's
build-native/alpha-linux/libf2c a
reopen 136359
thanks
Hello,
Debian Bug Tracking System wrote:
Changes:
gcc-2.95 (2.95.4.ds9-3) unstable; urgency=medium
.
* Updated s390 patch fixing several internal compiler errors (Gerhard Tonn).
* New patch by Phil Blundell to fix scalapack build error on m68k.
Closes: #129573.
* New
Package: g77-2.95
Version: 1:2.95.4-2
Severity: important
Greetings,
The f__cabs() function in /usr/lib/gcc-lib/libg2c.a fails with SIGFPE
under certain conditions on alpha. This is because alpha math is not
ieee-compliant. Therefore, on alpha please use -mieee to build that
library -- or at l
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
Package: gcc-3.0
Version: 3.0.3-1
Severity: serious
Greetings,
gcc-3.0 3.0.3 does not build on ARM, and as a result, 3.0.2 does not
install. For details:
http://buildd.debian.org/build.php?arch=arm&pkg=gcc-3.0
Zeen,
--
-Adam P.
GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6
Philip Blundell wrote:
On Thu, 2002-01-17 at 16:28, Adam C Powell IV wrote:
/usr/lib/liblapack.so: undefined reference to `LC13'
It's a compiler bug. Try gcc-3.0, and/or file a bug report.
[This was while trying to build illuminator.] Okay... Unfortunately,
3.0.3 has never successf
19 matches
Mail list logo
