This is the mail archive of the java-patches@gcc.gnu.org mailing list for the Java project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: 3.3.1 GCJ Cross compiler configuration issues



David Daney Wrote:

Peter Blemel wrote:


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.

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.


Hrm... That's not what I saw hapenning, which is how I wound up down that road. I'd go back and build again to check it out, but one build is an all day process.


Which brings me to another issue ;-) For an embedded system with no display and no network support it just takes up space to build awt / swing / etc classes. These groups of classes are tacked onto the end of 'ordinary_java_source_files'. Is it advisable to make a change such as

@NATIVE_TRUE@awt_SOURCES = $(awt_java_source_files)
java_source_files = ... $(awt_SOURCES)

?

Which brings me to another point. When building from a 'stock' GCC distribution everything (including .java files) are recompiled many times (ca, le, nof, und). Is there a particular reason that the .class files need to be built so many times?

Thanks and Regards,
Peter

_________________________________________________________________
Is your PC infected? Get a FREE online computer virus scan from McAfee® Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]