InetSocketAddress w/ connect fails

Sat Jun 21 10:14:00 GMT 2003

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am Freitag, 20. Juni 2003 15:06 schrieb Mohan Embar:
> Hi People,
>> > > Is this build from Mohan based on GCC 3.3 or on GCC 3.4 ? I
> > > fixed this bug lately in CVS trunk branch (future GCC 3.4). I
> > > think the original author never tested using the Socket
> > > constructor with no arguments.
> > >
> > > I would like to fix this GCC 3.3 branch. Should I write a patch
> > > for this ? Does somebody knows the status of this branch ?
> >
> >I do.
> >
> > > I cant find anything on the website.
> >
> >gcj policy is to fix bugs in mainline and on the branch. We won't
> >apply new features to the branch.
>> While we're on this topic: I'm currently throwing the MingW 3.4
> networking code around. I know that I can look into Mauve, but in
> the short term, if anyone wants to send me some of their pet,
> preferably-one-file, deterministic, non-interactive networking
> tests, I can try to run them against my upcoming 3.4 patch.
> Ideally, such a test would be accompanied by diffable, reproducible
> output from a run against the JRE.
>> Any volunteers?

Well I have collection of little apps that I edit daily for different 
usages. Not really convenient.
Currently I'm trying again to get Mauve working on my system.
It works now when I build it alone (not in the libgcj tree) but some 
testcases fail that should not fail .....
Mauve is definitely the way to go. We should add some more tests to 
it.
Michael
- -- 
Homepage: http://www.worldforge.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+9DDaWSOgCCdjSDsRApgdAKCcGiHnMhtNkgPArMsnDO3gDSxjxgCfXTYL
JWqEK4jojuevBALty38woiY=
=Q1v+
-----END PGP SIGNATURE-----