libjava configure error

Tue Aug 17 17:38:00 GMT 2004

Bryan Smant writes:
 > On Tue, 2004年08月17日 at 04:30, Andrew Haley wrote:
 > > Tom Tromey writes:
 > > > >>>>> "Bryan" == Bryan Smant <bryan@stg.com> writes:
 > > > 
 > > > Bryan> I am trying to build a cross compiler tool chain targeting eCos
 > > > Bryan> running on an ARM7 processor. When I compile libjava with the
 > > > Bryan> --with-ecos option, I get the following error message:
 > > > 
 > > > The eCos support has bit-rotted over the years. Also, it was never
 > > > truly complete, for instance we had a vague plan to let eCos'
 > > > configurability influence the native parts of libgcj, but that was
 > > > never implemented.
 > > > 
 > > > Bryan> ../../../../src/gcc-3.3.4/libjava/java/io/natFileEcos.cc: File not found
 > > > 
 > > > Bryan> Has anyone out there actually built libjava for eCos successfully? Is
 > > > Bryan> there a work around, or will I have to write my own version of the file?
 > > 
 > > I've done it, and it did work. However, I never got eCos's thread
 > > support working, and support for files was very rudimentary.
 > 
 > Thanks for the information. Do you know what is would take to implement
 > the threading support for eCos? I eventually need to get threads,
 > sockets, and the javax.comm API for serial ports working. I know that
 > the serial stuff is not included, and I am working on a port for that.
 > Are sockets supported for eCos?
OS functions are concentrated in a few files, and making an eCos
version should be easy enough. If I had to do it I'd probably
allocate a small number of weeks, given a working eCos environment.
On the other hand, I may be the only person in the world who knows
both gcj and eCos! :-)
Sockets is a matter of writing an eCos version of natInetAddress,
natNetworkInterface, gnu/java/net/PlainSocketImpl, and
gnu/java/net/PlainDatagramSocketImpl. There are Windows and GNU/Linux
versions in libjava/java/net. However, eCos claims to have a "POSIX
compatible API" so it's possible that you could use the POSIX versions
we use with GNU/Linux.
eCos has both native threads and, I believe, POSIX threads. Again,
you might be able to reuse the POSIX threads stuff we use with
GNU/Linux, but I wouldn't bank on it. Maybe better to use eCos native
threads.
You'd want to be able to attach the eCos debug output stream to
System.err.
I'm not familiar with javax.comm.
Andrew.