This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: 3.3.1 GCJ Cross compiler configuration issues
- From: David Daney <ddaney at avtrex dot com>
- To: Peter Blemel <pblemel at hotmail dot com>
- Cc: java-patches at gcc dot gnu dot org
- Date: Wed, 07 Apr 2004 10:46:00 -0700
- Subject: Re: 3.3.1 GCJ Cross compiler configuration issues
- References: <BAY2-F119jnzi95HfqR0004e136@hotmail.com>
Peter Blemel wrote:
Hello World!
I've been porting gcj and libgcj/libjava as a cross compiler for a
powerpc embedded sysem (running a proprietary RTOS). There are a
couple of configuration issues that I humbly suggest could be changed
in the configuration. I am looking for concurrence before I make an
attempt at submitting a patch. Granted I'm a couple of builds
behind, but 3.3.1 is what the rest of the team is using so I'm working
with it too.
o The libjava/configure.host script sets up the build based on the
host configuration (as you'd expect, given it's name). The "problem"
is that it's really configuring the library for the target, not the host.
Given that, the case statements case "${host}" ... need to be case
"${target}".
I thought the same thing, until my misconceptions were kindly corrected
by others on the list.
I kind of forget the argument, but for cross compiler library (like
libgcj) builds, the ${host} variable magically has the value of the
cross target. So everything works.
Libraries are hosted, tools that contribute the the generation of code
are targeted.
David Daney.