This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: what i learned making a gcj cross-compile environment fortarget=i386-cygwin
- To: Tom Tromey <tromey at redhat dot com>
- Subject: Re: what i learned making a gcj cross-compile environment fortarget=i386-cygwin
- From: Jeff Sturm <jsturm at one-point dot com>
- Date: Fri, 27 Apr 2001 14:23:10 -0400 (EDT)
- cc: alk at pobox dot com, java at gcc dot gnu dot org
On 27 Apr 2001, Tom Tromey wrote:
> I haven't built a Linux-x-Cygwin toolchain in a long, long time (three
> years at least). I don't remember it being such a problem, but I had
> a unified tree and I didn't try to build libgcj.
Cygwin used to provide their unified tree as a tarball for download. It
was easy to build.
> I imagine at the current moment it is easier to try to build natively on
> Cygwin than it is to do a cross, especially for libgcj.
I'd guess you've never watched libtool run under bash.exe... it is _slow_.
> I haven't built any libgcj cross in a couple years, and even then it was
> to a relatively simple target (a MIPS port using newlib), not to another
> host.
I kind of suspected crosses aren't getting tested, in part because
AC_CHECK_SIZEOF has crept into libjava/configure.
I gave up building anything natively on win32. Cross builds are the way
to go.
Jeff