Problems building libgcj...

Sat Apr 1 00:00:00 GMT 2000

>>>>> "Scott" == Scott Bambrough <scottb@netwinder.org> writes:

Scott> The problem seems to be the multilibbing. The include paths
Scott> for libffi are not correct on the compiler command line (they
Scott> need another ../) when building in soft-float/libjava. Hence
Scott> ffi.h cannot be found. I had a look at the makefiles, but I
Scott> was hoping someone here might be more familiar with the
Scott> Makefile so the fix could be made without me having to analyze
Scott> the Makefile.
Look for -I../ffi/include in Makefile.
Try changing it to -I$(MULTIBUILDTOP)/../ffi/include
If that works, tell me and I will check in the appropriate change.
Unfortunately nobody builds libgcj multilibbed on a regular basis...
Scott> 1) The version of Double.h generated by gcj.h has 5 static
Scott> jdouble constants at the end of the class. Only the first two
Scott> get initialized with values (on x86 and ARM). Is this correct?
Yes. As I recall we don't have a real way to print infinity (or NaN)
in a way that C++ would like.
Scott> 2) I had to modify the sources in the compilers gcc/java
Scott> directory to get the above file generated correctly. ARM sets
Scott> FLOAT_WORDS_BIG_ENDIAN to 1, and I had to tweak it in a couple
Scott> of places. Should I submit the patches for this here, or on
Scott> gcc-patches? I have a copyright assignment on file for gcc.
Scott> These changes for the compiler should be covered by that
Scott> copyright assignment right?
What files did you have to change?
Anyway, all gcc patches should be sent to gcc-patches.
If they are patches for gcc/java, mention "java" in the subject (or
else we might skip them by mistake).
I imagine your changes will be covered by your existing assignment,
but it depends on exactly what you said in that assignment.
Scott> 3) I had a look at the copyright assignment for libgcj. Is it
Scott> affected by RedHat's purchase of Cygnus?
I'm not positive. We're currently trying to merge libgcj and
Classpath under a different license, under the ownership of the FSF.
If this works out then things will change.
If you're planning to sign papers for libgcj I can find out the real
answer. If you're just curious, I won't.
Tom