RMI problem

Fri May 27 14:21:00 GMT 2005

yep, this comes from the static linking Win GCJ4 does.
To avoid this you should try to include references to classes that are
loaded with classforname mechanism.
i.e.
class rmiTest{
//force the linker to include this class in your app
 java.rmi.server.RemoteStub _fakestub;
// your code.....
}
On 5/26/05, Andrew Haley <aph@redhat.com> wrote:
> Amir Bukhari writes:
> >
> > I am using GCJ 4.0 build for MinGW for Windows.
>> Ah, Windows. There are problems with gcj for Windows, because it
> doesn't support building DLLs, and you really need functional shared
> library semantics to make this sort of stuff work in general.
>> There are some hacks that the Windows people use to make this work,
> and perhaps if one of them is listening they could shout out.
>> Andrew.
>