freebsd-ports/lang/mono/pkg-message
Romain Tartière 5c80951022 - Update lang/mono to 2.6.4;
- Update a bunch of C# ports as well (audio/taglib-sharp, deskutils/tomboy,
  devel/mono-tools, devel/monodevelop, devel/monodevelop-boo,
  devel/monodevelop-database, devel/monodevelop-java, devel/monodevelop-vala,
  graphics/f-spot, lang/boo [1], lang/mono-basic, mail/gmime24, gmime24-sharp,
  multimedia/banshee, multimedia/banshee-mirage, multimedia/moonlight,
  www/mod_mono, www/webkit-sharp, www/xsp, x11-toolkits/gnome-desktop-sharp20,
  x11-toolkits/gtk-sharp20, x11-toolkits/libgdiplus).

PR:		ports/143657 [1]
Submitted by:	glewis [1]
2010-06-01 12:41:30 +00:00

34 lines
1.6 KiB
Plaintext

************************************************************************
If you have build/runtime errors with Mono and Gtk# apps please try the
following first:
* Build Mono and gtk+ (x11-toolkits/gtk20) without CPUTYPE and with the
default FreeBSD CFLAGS ('-O2 -fno-strict-aliasing -pipe') as Mono has
been known to expose compiler bugs.
* Try building and running Mono with the GENERIC kernel.
- Mono requires SYSVSHM, SYSVMSG, and SYSVSEM which are part of the
GENERIC kernel.
- Removing kernel options or changing defaults to use experimental
options can adversely affect Mono's ability to build and run.
* Remove leftover semaphores / increase semaphore limits.
- Close apps which use Mono and run `ipcs -sbt`. Remove the
semaphores with MODE "--rw-------" and NSEMS "8" using ipcrm (1)
- _OR_ simply reboot which is the safest method.
- On multi-user systems the semaphore limits may need to be increased
from the defaults. The following should comfortably support 30 users.
# echo "kern.ipc.semmni=40" >> /boot/loader.conf
# echo "kern.ipc.semmns=300" >> /boot/loader.conf
* If you are in a jailed environment, ensure System V IPC are enabled.
You can rely on the security.jail.sysvipc_allowed sysctl to check
this status. The following enables this feature on the host system:
# echo "jail_sysvipc_allow=\"YES\"" >> /etc/rc.conf
* Some process information are acceded through /proc (e.g. when using
NUnit) and procfs(5) has to be mounted for these features to work:
# echo "proc /proc procfs rw 0 0" >> /etc/fstab
************************************************************************