Fw: Mono 4.2

[Alan Valentine]

Thank you,

I also had to add the below line to my mono Makefile in order to stop it
failing compilation with this
error/usr/ports/lang/mono/work/mono-4.2.1/eglib/src/gunicode.c:223:
undefined reference to `locale_charset'

LDFLAGS+= -L${LOCALBASE}/lib -lcharset

then I hit this staging error


   1. ng/mono/work/mono-4.2.1'
   2. ====> Compressing man pages (compress-man)
   3. ===>  Installing for mono-4.2.1.91
   4. ===>  Checking if mono already installed
   5. ===>   Registering installation for mono-4.2.1.91
   6. pkg-static: Unable to access file
   /usr/ports/lang/mono/work/stage/usr/local/lib/libmono-profiler-cov.a: No
   such file or directory
   7. pkg-static: Unable to access file
   /usr/ports/lang/mono/work/stage/usr/local/lib/libmono-profiler-cov.so: No
   such file or directory
   8. pkg-static: Unable to access file
   /usr/ports/lang/mono/work/stage/usr/local/lib/libmono-profiler-cov.so.0: No
   such file or directory
   9. pkg-static: Unable to access file
   /usr/ports/lang/mono/work/stage/usr/local/lib/libmono-profiler-cov.so.0.0.0:
   No such file or directory
   10. pkg-static: Unable to access file
   /usr/ports/lang/mono/work/stage/usr/local/lib/mono/4.5/symbolicate.exe: No
   such file or directory
   11. pkg-static: Unable to access file
   /usr/ports/lang/mono/work/stage/usr/local/lib/mono/4.5/symbolicate.exe.mdb:
   No such file or directory
   12. *** [fake-pkg] Error code 74
   13.
   14. Stop in /usr/ports/lang/mono.


Then an hour later I found that in the last few hours, the mono port has
had an official update :D ......



On Tue, Nov 24, 2015 at 3:37 AM Russell Haley <russ.haley at gmail.com> wrote:

> Below are the instructions to do a manual upgrade to 4.2 by adjusting the
> current port files. There was some talk about creating a patch but I think
> we are waiting on the next mono release.
>
> Hope that helps.
>
> Russ
>
> Sent from my BlackBerry 10 smartphone on the Koodo network.
>   Original Message
> From: Chris McVittie <chris at greenflump.com>
> Sent: Friday, November 6, 2015 2:04 PM
> To: freebsd-mono at freebsd.org
> Subject: Re: Mono 4.2
>
> Hi,
>
> So I had a first hack at this...
>
> Using the existing port
> rm -rf files
> edit Makefile
> PORTVERSION= 4.2.1.91
> WRKSRC= ${WRKDIR}/mono-4.2.1
> make makesum
> make install
> make makeplist
> make clean && make install
>
> All seems to "just work." I'm suspicious that this is too easy?
>
> ```
> root at bsd-1:/usr/ports/lang/mono # mono --version
> Mono JIT compiler version 4.2.1 (Stable 4.2.1.91/8862921 Fri Nov 6
> 21:13:46
> UTC 2015)
> Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors.
> www.mono-project.com
> TLS: __thread
> SIGSEGV: altstack
> Notification: kqueue
> Architecture: amd64
> Disabled: none
> Misc: softdebug
> LLVM: supported, not enabled.
> GC: sgen
> ```
> Is there anything else I should check?
>
> Thanks,
> Chris
>
>
>
> On Tue, Oct 27, 2015 at 8:15 PM Chris McVittie <chris at greenflump.com>
> wrote:
>
> > Hi,
> > I was wondering if there was a plan for supporting mono 4.2? There are
> > lots of useful fixes and features around the threadpool that would be
> good
> > to have access to.
> >
> > (I'm completely new here, and while willing to help, suspect my help
> won't
> > be useful!)
> >
> > Thanks,
> > Chris
> >
> _______________________________________________
> freebsd-mono at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-mono
> To unsubscribe, send any mail to "freebsd-mono-unsubscribe at freebsd.org"
>