Dalibor Topic wrote:
Hi Dan,

--- Dan Kegel <[EMAIL PROTECTED]> wrote:

I'm trying to deploy kaffe-1.0.7 in a
cross-compiling environment.
Cool. Just out of pure interest, what platform are you
cross-compiling to?
ppc405, ppc750, and sh4, all running linux-2.4.17, more or less.
I *can* run Blackdown JRE 1.3.1 on ppc750, but it takes
up rather too much memory, and it doesn't help me on the
other platforms.  Hence my interest in Kaffe.

The first step was to update to autoconf2.5x...
Dalibor Topic had already checked in a configure.in
updated to autoconf2.5x.
Yeah, that was a byproduct of my attempts to merge in
javax.sound from tritonus.org.
It's so nice somebody's actually pulling together
goodies from all the open source java efforts into kaffe!

Seems like we did pretty much the same thing. I left
out the AC_PREREQ since no features of 2.52 are used
which don't exist in earlier versions, so I figured it
would be pointless to bump up the requirements. I
separated the libs into several calls as I am no fan
of extended lines where they can be avoided ;) and it
still worked under 2.13.
That all sounds sensible.

The build machinery could use some work to ease
cross-compiling, go ahead if you'd like to improve it.
Thanks, I'll have a go at it.

First thing I noticed is that the libtool included in kaffe
doesn't seem to support the 'make install DESTDIR=...'.
I'm trying libtool cvs now while waiting for the next release
of libtool.   Oddly, it didn't link until I applied this patch:

--- kaffe-1.0.7/kaffe/kaffe/Makefile.am.orig    Thu Dec 26 17:02:30 2002
+++ kaffe-1.0.7/kaffe/kaffe/Makefile.am Thu Dec 26 16:49:02 2002
@@ -22,7 +22,7 @@
 LIBKAFFEVM = ../kaffevm/libkaffevm.la $(libxprof)

 kaffe_bin_LDFLAGS = $(KVMBINFLAGS) -export-dynamic
-kaffe_bin_LDADD = $(DLOPEN_JAVA_LIBS) $(LIBKAFFEVM) $(KAFFE_LIBS)
+kaffe_bin_LDADD = $(DLOPEN_JAVA_LIBS) $(LIBKAFFEVM) $(KAFFE_LIBS) @LIBLTDL@
 kaffe_bin_DEPENDENCIES = $(LIBKAFFEVM) $(JAVA_LIBS)

 ### Rules to generate the version-info header file

as per http://sources.redhat.com/autobook/autobook/autobook_167.html#SEC167

I thought that would have been needed even for libtool-1.4.3.
Is that something you should do in your tree, too, perhaps?

I'm still quite uncomfortable with libtool.  This is my third or
fourth run-in with it in a cross-development environment.
I usually end up ripping it out in frustration, but this time
I'm trying out cvs libtool on the off chance it's improved enough
to handle cross-compiling now.

Thanks,
Dan

--
Dan Kegel
Linux User #78045
http://www.kegel.com


_______________________________________________
kaffe mailing list
[EMAIL PROTECTED]
http://kaffe.org/cgi-bin/mailman/listinfo/kaffe

Reply via email to