I have another suggestion:
Remove MSG_NOSIGNAL from all sources and do "signal(SIGPIPE, SIG_IGN);" at the very start of "mono" and "mint". >From some previous discussion it turned out that MSG_NOSIGNAL is not avaialble in some systems (not only freebsd) and signal() is widely supported. If you insist on having MSG_NOSIGNAL, I suggest adding test for it to configure.in instead of #ifdef __FreeBSD__ What do you think about it ? Jarek On Tue, 28 May 2002, Aidan Skinner wrote: > mono/io-layer/deamon-messages.c uses MSG_NOSIGNAL in it's socket code, > which isn't defined in FreeBSD. > > there's previous discussion of it at: > http://lists.ximian.com/archives/public/mono-list/2002-May/005608.html > > A patch is attached to #define it to 0 on FreeBSD. > > I've also created a FreeBSD port of mono and submitted it to the > project (which includes the attached patch to make it build), its' > currently using the 24-May-02 snapshot, but I'll try to keep that > updated as and when. > > I'm working on getting the testsuite to run, and will post results > when I have them. > > - Aidan > -- > [EMAIL PROTECTED] http://www.velvet.net/~aidan/ aim:aidans42 > finger for pgp key fingerprint |Unix Programmer/Admin actively seeking work > 01AA 1594 2DB0 09E3 B850 |CV at http://www.velvet.net/~aidan/cv.txt > C2D0 9A2C 4CC9 3EC4 75E1 |Gis a job, go on, I can do that, go on, gis it. > _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
