Cross-compiling IcedTea7

[Thierry Reding]

Hi,

I've been trying to get IcedTea 7 to cross-compile, without much success. So
I went and gave OpenJDK a try and had some more luck. My plan now is to try
and take some of the insight from that and give IcedTea another try.

One of the problems with IcedTea is that it runs two iterations of the build,
the bootstrap stage as well as the final stage. Am I correct in assuming that
when cross-compiling the bootstrap stage should actually be built for the
architecture of the build host, and the final stage should then use that
bootstrap to build OpenJDK for the target architecture (or host architecture
in autoconf speak)? Currently both stages are built for one architecture,
which obviously will not work for a cross-compile.

One general question is how much of the changes that actually modify code in
OpenJDK can go upstream and what needs to go into IcedTea patches. Preparing
patches against an OpenJDK tree and applying them in the IcedTea build also
turns out not to be an optimal workflow. What is the usual practice?

Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
Url : http://mail.openjdk.java.net/pipermail/distro-pkg-dev/attachments/20100601/1d9657c9/attachment.bin