[Mono-devel-list] Build error on OSX

[Steve Mentzer]

Yes and No.

I haven't tried a snapshot since 10/30. The prior snapshot (10/28) worked
for me, with the exception of profiler and mini.

Neither profiler or mini seem to be able to compile.... regardless of
snapshot. This dates back to the introduction of mini to the heirarchy.

The prior version I was running (10/28) was working nicely. It appeared to
have a deadlock problem somewhere, as the test scaffold I was running, which
listened on a particular tcp port, accepted a connection, read *n* bytes of
data and saved it to a file would work for about 10 minutes and then hang.

So, most functions are more or less working, except for the fact that mini
and profiler won't compile, and the latest drops are dying when trying to
build interpreter.

If you would like, I would be more than happy to tarball up my *compiled*
mono dir and send it to you... :)

Thanks!

Steve


----- Original Message ----- 
From: "Bob Koss" <koss at objectmentor.com>
To: "Steve Mentzer" <steve at mudflapsoftware.com>; "Mike Flippin"
<webmaster at blindmindseye.com>
Cc: <mono-devel-list at lists.ximian.com>
Sent: Sunday, November 02, 2003 1:22 AM
Subject: Re: [Mono-devel-list] Build error on OSX


>
> Does anyone actually have a working installation of Mono on OS X?
>
>
> On 11/1/03 2:47 PM, "Steve Mentzer" <steve at mudflapsoftware.com> wrote:
>
> >
> > Prior versions of the OS/X dev tools failed to declare socklen_t. Of
> > course, the panther/xcode 7b85 release corrects this oversight, and as
> > the mono build scripts accounted for it, it now causes an error.
> >
> > basically, you will find the following lines in mono/io-layer/sockets.h
> >
> > #ifdef __APPLE__
> > typedef unsigned int socklen_t;
> > #endif
> >
> > make it look like this
> >
> > #ifdef __APPLE__
> > //typedef unsigned int socklen_t;
> > #endif
> >
> > Of course, the latest daily snapshot (10/30) failed to build
> > interpreter for me due to conflicting _locale_charset symbols during
> > link, but that is a different story...
> >
> >
> > On Nov 1, 2003, at 8:23 AM, Mike Flippin wrote:
> >
> >> In file included from ../../mono/io-layer/wapi.h:26,
> >>                 from atomic.c:15:
> >> ../../mono/io-layer/sockets.h:27: error: conflicting types for
> >> `socklen_t'
> >> /usr/include/sys/socket.h:79: error: previous declaration of
> >> `socklen_t'
> >> make[3]: *** [atomic.lo] Error 1
> >> make[2]: *** [all-recursive] Error 1
> >> make[1]: *** [all-recursive] Error 1
> >> make: *** [all] Error 2
> >>
> >> That's from the latest CVS source code from anoncvs. I'm using Panther
> >> with the XCode developer package (includes GCC 3.3). I also recall
> >> having this problem on Jaguar with the last two releases of GCC for
> >> OSX.
> >> _______________________________________________
> >> Mono-devel-list mailing list
> >> Mono-devel-list at lists.ximian.com
> >> http://lists.ximian.com/mailman/listinfo/mono-devel-list
> >>
> >
> >
> >
> > _______________________________________________
> > Mono-devel-list mailing list
> > Mono-devel-list at lists.ximian.com
> > http://lists.ximian.com/mailman/listinfo/mono-devel-list
>
> -- 
> Robert Koss, Ph.D.     | Training, Mentoring, Contract Development
> Senior Consultant      | Object Oriented Design, C++, Java
> www.objectmentor.com   | Extreme Programming
>
>
>