Re: [kaffe] Build failure of CVS head for i386/NetBSD

2007-02-03 Thread Dalibor Topic

Ito Kazumitsu wrote:

I cannot wait for the next occasion of resynchronization with GNU
Classpath, and mannually copied some files from GNU Classpath.



Thank you very much for doing that, and fixing the issues that the last 
merge brought to light.


cheers,
dalibor topic

___
kaffe mailing list
kaffe@kaffe.org
http://kaffe.org/cgi-bin/mailman/listinfo/kaffe


Re: [kaffe] Build failure of CVS head for i386/NetBSD

2007-01-20 Thread Ito Kazumitsu
Hi,

From: Kiyo Inaba [EMAIL PROTECTED]
Subject: [kaffe] Build failure of CVS head for i386/NetBSD
Date: Mon, 15 Jan 2007 14:58:58 +0900 (JST)

 But for cpnet.c, this patch omit one feature which is originally provided.
 I have no idea (except with private signal handler) how to add NOPIPE
 flag for send, if it is not provided by the OS...
 
 Any better idea which really fix the cpnet.c's problem?

Maybe Kaffe VM takes care of SIGPIPE, and we do not have to use a
special option. Such is the patch I made in GNU Classpath.

I cannot wait for the next occasion of resynchronization with GNU
Classpath, and mannually copied some files from GNU Classpath.

___
kaffe mailing list
kaffe@kaffe.org
http://kaffe.org/cgi-bin/mailman/listinfo/kaffe


Re: [kaffe] Build failure of CVS head for i386/NetBSD

2007-01-15 Thread Ito Kazumitsu
Hi,

From: Kiyo Inaba [EMAIL PROTECTED]
Subject: [kaffe] Build failure of CVS head for i386/NetBSD
Date: Mon, 15 Jan 2007 14:58:58 +0900 (JST)

 As Kaz suggested, I modified as attached patch and the build get success.
 But for cpnet.c, this patch omit one feature which is originally provided.
 I have no idea (except with private signal handler) how to add NOPIPE
 flag for send, if it is not provided by the OS...
 
 It looks like this 'patch' also solve m68k/NetBSD configure problem.
 
 Any better idea which really fix the cpnet.c's problem?

I think cpnet.c needs further review.  It will not work properly
on FreeBSD 5.4-RELEASE, either.

#if defined (HAVE_MSG_NOSIGNAL)
#define SOCKET_NOSIGNAL MSG_NOSIGNAL
#elif defined (HAVE_SO_NOSIGPIPE)
#define SOCKET_NOSIGNAL SO_NOSIGPIPE
#else
#error No suitable flag found to ommit a SIGPIPE on signal errors with send().
#endif

ret = send(fd, data, len, SOCKET_NOSIGNAL);

FreeBSD 5.4-RELEASE:
  HAVE_MSG_NOSIGNAL false
  HAVE_SO_NOSIGPIPE true   0x0800

SO_NOSIGPIPE (0x0800) is set to SOCKET_NOSIGNAL and is used as an option
to send.  But SO_NOSIGPIPE is a socket level option which should be used
with setsockopt.  0x0800 used as an option to send will not have any
effect, or may have some unexpected effects.

Anyway, this is a GNU Classpath issue.  I will report a bug about this
to GNU Classpath.

___
kaffe mailing list
kaffe@kaffe.org
http://kaffe.org/cgi-bin/mailman/listinfo/kaffe