From owner-freebsd-mono@freebsd.org Fri Aug 21 05:47:29 2015 Return-Path: Delivered-To: freebsd-mono@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D0B629BF0A9 for ; Fri, 21 Aug 2015 05:47:29 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id B2F30998 for ; Fri, 21 Aug 2015 05:47:29 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id AFF119BF0A8; Fri, 21 Aug 2015 05:47:29 +0000 (UTC) Delivered-To: mono@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AF79C9BF0A7 for ; Fri, 21 Aug 2015 05:47:29 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 85985997 for ; Fri, 21 Aug 2015 05:47:29 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: by pawq9 with SMTP id q9so44792364paw.3 for ; Thu, 20 Aug 2015 22:47:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=Ky72ueSj/YkMIlSDqstGgHSCI6OG02bs/FP7w6hD/s0=; b=UmQMRjSyftBFTvGUuT4GX3MPBO57Xv2MDqk/yawdwUXYXAPb4OXsFmVPatseHgWuqO bD6kG4NYuVUMigx6T/w9AqZcKSEN2LoU6lGHxZ8NMQzR8ov51FPmcDTd6fDYmJavgFzl 3vsUHqDyhWDUONV2+Rg+l+wVMGsT1V6jQ8nX46IKO3AZUrOuOvaEDo0C/fvUx+NY9R2/ SYtjWrLXnX/fuFHafCJMhxnDqQO98iO3ksrTuWNeyz0bXPqeUu9OgkudIt73VtR3zuLv G6eLAYRwKvTznHgUL6vK9e0p1hfxHECJJmQNayC8IXMD3Y9vC3ksViDgbbKOkD7FANlZ 8WVg== MIME-Version: 1.0 X-Received: by 10.66.66.202 with SMTP id h10mr13727619pat.145.1440136049078; Thu, 20 Aug 2015 22:47:29 -0700 (PDT) Received: by 10.66.162.8 with HTTP; Thu, 20 Aug 2015 22:47:29 -0700 (PDT) Date: Thu, 20 Aug 2015 22:47:29 -0700 Message-ID: Subject: MonoDevelop 5.10 for FreeBSD 10.1 From: Russell Haley To: mono@freebsd.org, Ivan Radovanovic Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-mono@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Mono and C# applications on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Aug 2015 05:47:29 -0000 Hi Guys, So I have been able to build MonoDevelop 5.10 from Git using the current ports version of mono. I have one item that I will submit as a pull request to Xamarian on Github. The following is a list of all the outstanding items I think we have control over: 1) mono - There is a bug in KqueueWatcher class (KqueueEvents.cs) that causes MonoDevelop to crash. It can be mitigated with a env variable *setenv MONO_MANAGED_WATCHER true* Ivan Radovanovic is working on a fix. - During the mono installation, we need to run the following command: *mozroots --import --syn*c Otherwise the MonoDevelop build fails on the restore-packages target. I suggested it in the MonoDevelop build but the repository owner indicated the mono build is the place to perform mozroots 2) MonoDevelop build - The following is in their MonoDevelop/main/scripts/configure.sh: *DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )" * It's bash specific so it fails. Perhaps we should just include this *env SHELL=/usr/local/bin/bash* in our ports make file? - These were my dependancies over and above what I had. I didn't have a clean instance so there is most likely others. I think these are all addressed in the ports Makefile: cd /usr/ports/textproc/p5-XML-LibXML/ && make install clean cd /usr/ports/x11-toolkits/gtk-sharp20/ && make install clean cd /usr/ports/x11-toolkits/gnome-sharp20/ && make install clean -> had to run REinstall for this one??? gnome-sharp20 was interesting becuase I had to run a make re-install after the MonoDevelop build. wierd. Any ideas why? 3) Running - As stated above until Kqueuewatcher is fixed, we need to *setenv MONO_MANAGED_WATCHER true* I put it in my monodevelop run script - Are we running an old version of gtk-sharp? When starting monodevelop we get hundreds of these messages: * ERROR [2015-08-20 22:21:29Z]: GLib-Critical: Source ID 1858 was not found when attempting to remove itStack trace: at GLib.Source.g_source_remove(UInt32 ) at GLib.Source.Remove(UInt32 tag) at GLib.Timeout+TimeoutProxy.Dispose(Boolean disposing) at GLib.Timeout+TimeoutProxy.Finalize()* There seems to be updated here: https://github.com/mono/gtk-sharp/commit/7ea0c4afaf405df2dfc5a42e098e9023ecc1c51c PC-BSD just updated itself so I'll see if packages is already updated - MonoDevelop thinks it's running on Linux. This is the output when it starts: * mono /usr/local/lib/monodevelop/bin/MonoDevelop.exe --no-redirect INFO [2015-08-10 22:29:49Z]: Starting MonoDevelop 5.10 INFO [2015-08-10 22:29:49Z]: Running on Mono 4.0.1 (tarball Tue Aug 4 06:03:31 UTC 2015) (64-bit)* *************************************************************** * INFO [2015-08-10 22:29:49Z]: Operating System: Linux* **************************************************************** * FreeBSD Prescott 10.1-RELEASE-p26 FreeBSD 10.1-RELEASE-p26 #0: Tue Jul 28 22:55:17 UTC 2015 root@amd64-builder.pcbsd.org:/usr/obj/usr/src/sys/GENERIC amd64 INFO [2015-08-10 22:29:49Z]: Using GTK+ 2.24.27 INFO [2015-08-10 22:29:49Z]: Add-in loaded: MonoDevelop.Core INFO [2015-08-10 22:29:49Z]: Add-in loaded: MonoDevelop.Ide WARNING [2015-08-10 22:29:49Z]: No proxy credential provider was found INFO [2015-08-10 22:29:49Z]: Initializing Runtime Mono 4.0.1 Starting MonoDevelop* Booo! where do I change that??? I think that's it? 5.10 isn't released yet so if we jump on this now, we could be current at least for a little bit? What is the etiquette for updating the Mono and MonoDevelop ports? It would be nice if I could leave this to someone that knew what they were doing, but I am willing to take it on if needs be. I would be willing to support a 3 month port update cycle for one year. Thanks, Russ