This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: Compile errors in libgcj while building cross-compiler for MinGW
- From: Ranjit Mathew <rmathew at hotmail dot com>
- To: java at gcc dot gnu dot org
- Date: Wed, 08 Jan 2003 10:27:30 +0530
- Subject: Re: Compile errors in libgcj while building cross-compiler for MinGW
- References: <atqino$hgl$1@main.gmane.org> <augnvh$v3n$1@main.gmane.org> <87y967t82r.fsf@fleche.redhat.com> <86bs2s97ud.fsf@nowhere.com>
Adam Megacz wrote:
Ranjit> Am I the only one left here who plays with the mingw32 target?
Maybe. There seems to be a fair amount of interest in this target but
not many people to work on it. Bummer.
I'll be back on it soon enough. But I really need Bryce to devote
about ten minutes to helping me with the otable stuff first.
Yay! Am I happy or what! :-) Welcome back.
To accommodate this limitation, I propose defining macros
"_Jv_platform_getsockerr()" and "_Jv_platform_setsockerr()"
I would greatly prefer to simply break off the Win32 socket stuff into
Win32SocketImpl.java, just like we do with filesystem stuff. The
Win32 sockets stuff superficially appears to be BSD-compatible, but
it's not.
Trying to cram it into the same file by using tricky #define's and
#ifdef's is just asking for trouble, and it will only get harder as we
start implementing more sophisticated stuff like IPv6 and multicast.
And while we are at it and at the risk of being clobbered for
raising this issue yet again, I would sincerely suggest that we
move to WinSock 2 in toto - I'm really uncomfortable about mixing
functions linked in from both wsock32 and ws2_32 in the same
program... Besides, it would affect only a *very small* population
of truly vanilla Win95 installations and even then is easily
corrected.
Sincerely Yours,
Ranjit.
--
Ranjit Mathew Email: rmathew AT hotmail DOT com
Bangalore, INDIA. Web: http://ranjitmathew.tripod.com/