Ito Kazumitsu kaz at maczuka.gcd.org
Thu Aug 26 07:15:45 PDT 2004


Now on my FreeBSD 5.1-RELEASE machine, regression test for
SoTimeout.java fails.  I think the following may be the
cause of this failure.

Now that kaffe/kaffe/kaffevm/systems/unix-pthreads/syscalls.c has been
changed as follows:

RCS file: /cvs/kaffe/kaffe/kaffe/kaffevm/systems/unix-pthreads/syscalls.c,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- kaffe/kaffe/kaffevm/systems/unix-pthreads/syscalls.c        2004/07/29 14:24
+++ kaffe/kaffe/kaffevm/systems/unix-pthreads/syscalls.c        2004/08/19 09:51
@@ -469,7 +469,7 @@
                int timeout, int* out)
        /* absolute time at which time out is reached */
-#if defined(SO_RCVTIMEO) && !defined(__FreeBSD__)
+#if defined(SO_RCVTIMEO) && !defined(HAVE_BROKEN_SO_RCVTIMEO)
        int ret;
        struct timeval old_tv;
        struct timeval new_tv;

then configure on FreeBSD should define HAVE_BROKEN_SO_RCVTIMEO.

But actually it says:

checking whether setsockopt(SO_RCVTIMEO) is broken... no

And HAVE_BROKEN_SO_RCVTIMEO is not defined.

More information about the kaffe mailing list