Date: Tue, 24 Nov 2015 14:58:07 -0800 From: Russell Haley <russ.haley@gmail.com> To: freebsd-mono@freebsd.org Subject: Fwd: Mono 4.2 Message-ID: <CABx9NuSz9BH=c4AFM55a7KBg1CMMeM=xEJqWmhNEX8Y6S_T2Dw@mail.gmail.com> In-Reply-To: <CABx9NuTMesGdv4tD3HtinpAW6PMc%2BAjb92-crGs_TaJzO%2B=9yQ@mail.gmail.com> References: <CAH4WUysZ4ox9O6VFHBexmuwiWMOv95CNWUJXg=FXTA7c3mzRFg@mail.gmail.com> <CAH4WUytzCgeNr_=hU-X0uxesf3-h0GG0Zgjtp14f1LmeVib5bw@mail.gmail.com> <20151124033725.4386898.31704.933@gmail.com> <CAPOOb0cegBGMeGg94A5Gw%2BiKxwEPD=o1qYfp4p4J7ahqhoNxTw@mail.gmail.com> <20151124222851.4386897.3166.972@gmail.com> <CAPOOb0dBJYYNgcztyGTedcdYKORt6qj_YNCSscskb=O%2Byz=gTg@mail.gmail.com> <CABx9NuTMesGdv4tD3HtinpAW6PMc%2BAjb92-crGs_TaJzO%2B=9yQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
---------- Forwarded message ---------- From: Russell Haley <russ.haley@gmail.com> Date: Tue, Nov 24, 2015 at 2:57 PM Subject: Re: Mono 4.2 To: Alan Valentine <alval@alval.net> Hmmm...perhaps there is a sysctl you need to adjust? https://www.freebsd.org/doc/handbook/jails-tuning.html. sysctl | grep jail = ? So precluding jail issues, if the description is correct, the NotSupported error is in a mono wrapper around native functions. I have run into similar issues around DirectoryWatchers trying to use kqueue and wrappers around native "internal" commands for copying/moving files. And like the error you are seeing, someone thought they had already patched the kqueue issue and it has subsequently broken again. I would be interested in seeing the change list between 4.0.3 and 4.0.4 that supposedly fixes this. I'm super busy right now so I don't have time to drill in, but it looks like you have all the debug information here to resolve the issue if you felt like fixing mono! lolz. Good Luck!!! Russ On Tue, Nov 24, 2015 at 2:36 PM, Alan Valentine <alval@alval.net> wrote: > I use mono because Sonarr needs it for freebsd > > update functionality broken in sonarr, and they've been saying its a bug > in older version of mono, hence why I needed the update. > > https://github.com/Sonarr/Sonarr/issues/705 > > still doesn't fix the problem though! > > Anyway , I guess that's one for the sonarr guys, unless you know of any > flag that might need passing to a jail in order to stop a mono error like > the below? > > > 1. System.NotSupportedException: This system does not support > EnumProcesses > 2. at (wrapper managed-to-native) > System.Diagnostics.Process:GetProcesses_internal () > 3. at System.Diagnostics.Process.GetProcesses () [0x00000] in > /usr/ports/lang/mono/work/mono-4.2.1/mcs/class/System/System.Diagnosti= cs/Process.cs:861 > 4. at NzbDrone.Common.Processes.ProcessProvider.GetProcessById > (Int32 id) [0x00023] in > m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Common\Processes\Proc= essProvider.cs:75 > 5. at NzbDrone.Common.Processes.ProcessProvider.Exists (Int32 > processId) [0x00000] in > m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Common\Processes\Proc= essProvider.cs:58 > 6. at NzbDrone.Update.UpdateEngine.InstallUpdateService.Verify > (System.String targetFolder, Int32 processId) [0x0005c] in > m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Update\UpdateEngine\I= nstallUpdateService.cs:67 > 7. at NzbDrone.Update.UpdateEngine.InstallUpdateService.Start > (System.String installationFolder, Int32 processId) [0x00000] in > m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Update\UpdateEngine\I= nstallUpdateService.cs:79 > 8. at NzbDrone.Update.UpdateApp.Start (System.String[] args) > [0x00020] in > m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Update\UpdateApp.cs:5= 9 > 9. at NzbDrone.Update.UpdateApp.Main (System.String[] args) > [0x00042] in > m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Update\UpdateApp.cs:4= 3 > > > On Tue, Nov 24, 2015 at 10:28 PM, Russell Haley <russ.haley@gmail.com> > wrote: > >> For your sanity, I had to iterative-ly remove files from the plist file >> in order to finish the build/install. =E2=80=8E It looks like the same i= ssue. The >> official port should work without issue. >> >> Russ >> >> Sent from my BlackBerry 10 smartphone on the Koodo network. >> *From: *Alan Valentine >> *Sent: *Tuesday, November 24, 2015 2:03 PM >> *To: *Russell Haley >> *Cc: *mono@freebsd.org >> *Subject: *Re: Fw: Mono 4.2 >> >> 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+=3D -L${LOCALBASE}/lib -lcharset >> >> then I hit this staging error >> >> >> 1. ng/mono/work/mono-4.2.1' >> 2. =3D=3D=3D=3D> Compressing man pages (compress-man) >> 3. =3D=3D=3D> Installing for mono-4.2.1.91 >> 4. =3D=3D=3D> Checking if mono already installed >> 5. =3D=3D=3D> 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.ex= e: 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.ex= e.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@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@greenflump.com> >>> Sent: Friday, November 6, 2015 2:04 PM >>> To: freebsd-mono@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=3D 4.2.1.91 >>> WRKSRC=3D ${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@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@greenflump.com> >>> wrote: >>> >>> > Hi, >>> > I was wondering if there was a plan for supporting mono 4.2? There ar= e >>> > 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@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-mono >>> To unsubscribe, send any mail to "freebsd-mono-unsubscribe@freebsd.org" >>> >> >> >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CABx9NuSz9BH=c4AFM55a7KBg1CMMeM=xEJqWmhNEX8Y6S_T2Dw>