Mono Changes:
- Series release: http://www.go-mono.com/archive/1.1.9/
- Patch release: http://www.go-mono.com/archive/1.1.9.1_0/
(No 1.1.9.2 release announcement.)
Port Changes:
- Add pkg-message to explain reasons for common build failures and
note the need to possibly increase the number of semaphores from
the default FreeBSD amounts.
- Add preliminary amd64 support [1,2] which has been disabled for
the time being due to lingering stability issues.
- Force the Mono build to only write within ${WRKDIR} and no longer
write to ~/.wapi which leads to...
- Add bsd.mono.mk which is a common makefile all Mono consumers will
depend on. Currently this file sets the location of the .wapi the
build process will write to. Since Mono does not cleanup the
semaphore created for a .wapi when the last Mono process exits
this file also handles the removal of the semaphore created during
port building so we do not exhaust the machine's semaphore limit.
Submitted by: Jean-Michel "tuo" Herve <jm.herve@gameproduction.org> [1]
Joe Lewis <joe@joe-lewis.com> [1]
Lou Kamenov on BSD# mailinglist [2]
Approved by: ahze (mentor)
Project by: BSD# <http://www.mono-project.com/Mono:FreeBSD>
Mono will using Gamin or FAM by default if it exists in the runtime. If either
doesn't exist then it will use KeventWatcher.cs. Add auto-check on Gamin and
FAM for dependency. Bump the PORTREVISION to have the fix of kqueue.
Rationale:
- KeventWatcher.cs is naive, it does not report changes made to
files within a monitored directory [1]
- KeventWatcher.cs is implemented in C#, it is therefore slower than
Gamin or FAM, which are implemented in C and C++, respectively
[1] this is a bug which should be reported to the vendor
Testing, using the attached WatchTest.cs:
With KeventWatcher.cs:
$ mono WatchTest.exe /somedir &
[1] 89857
$ touch /somedir/foo
OnCreatedEvent /somedir/foo
$ echo foo >> /somedir/foo
<nothing happens>
With Gamin:
$ mono WatchTest.exe /somedir &
[1] 89889
$ touch /somedir/foo
OnCreatedEvent /somedir/foo
$ echo foo >> /somedir/foo
OnChangedEvent /somedir/foo
Submitted by: jylefort
FreeBSD problems with Mono. As of Mono 1.1.7, Mono has made a tremendous leap
in stability on FreeBSD. Many C# apps now works much better with Mono 1.1.7.
BSD# - Project by: http://www.mono-project.com/Mono:FreeBSD
503000. Mono 1.0.1 and greater have been broken on earlier OSVERSION
versions. Warning, not all C# apps will not working, because FreeBSD still
need to work more on pthread issues. Few C# apps such as Blam, Muine, Tomboy
and etc work perfect.
PR: ports/74397 ports/74398
Submitted by: Tom McLaughlin <tmclaugh@sdf.lonestar.org>
Project by: BSD# - http://forge.novell.com/modules/xfmod/project/?bsd-sharp
Approved by: maintainer timeout (no contract for months)
- Libintl is not part of libc on FreeBSD
PR: ports/70318
Submitted by: Christopher Nehren <apeiron@comcast.net>
Approved by: maintainer timeout (14 days)
KSE signal fixes from 6/12/2004, Mono now works on both 4.X and -CURRENT
(well, all but two benchmarks build and run successfully on both 4.X and
-CURRENT).
Note: you may need to rm -r ~/.wapi before building if you've tried older
versions of Mono.
in the mono/tests/ subdirectory, and it no longer hangs or dies with weird
errors. (And, yes, I do have garbage collecting enabled).
I'll let the C# user community be my judge. There still may be some issues
since boehm-gc isn't fully functional in its multi-threaded state on FreeBSD.
