Re: Mono 5.2 patch and DotNet Core 2 update
On Thursday, 11 January 2018 21:48:27 Russell Haley wrote: > David. I assume MSBuild and Roslyn are in > progress? I haven't touched MSBuild and Roslyn. I want to get mono and linux-dotnet into Ports first. Speaking of mono: - I've updated the patch on Phabricator - distinfo has been fixed - all dependent ports have been bumped - I've moved the '/usr/share/.mono' directory to '$PREFIX/share/mono' We have 7 tests failing. Briefly: 1) Looks like a false negative? 2-3) Needs to be investigates, possibly a false negative. 4-7) FreeBSD uses different zoneinfo names, needs to be patched (i.e. false negative). Will anyone be able to look into these? Regards David 1) CreateSubKey_Name_MaxLength (MonoTests.Microsoft.Win32.RegistryKeyTest.CreateSubKey_Name_MaxLength) System.ArgumentException : Cannot delete a subkey tree because the subkey does not exist. at Microsoft.Win32.RegistryKey.DeleteSubKeyTree (System.String subkey, System.Boolean throwOnMissingSubKey) [0x00024] in /home/dbn/ports/ports/lang/mono/work/mono-mono-5.2.0.215/mcs/class/corlib/Microsoft.Win32/RegistryKey.cs:631 at Microsoft.Win32.RegistryKey.DeleteSubKeyTree (System.String subkey) [0x0] in /home/dbn/ports/ports/lang/mono/work/mono-mono-5.2.0.215/mcs/class/corlib/Microsoft.Win32/RegistryKey.cs:612 at (wrapper remoting-invoke-with-check) Microsoft.Win32.RegistryKey:DeleteSubKeyTree (string) at MonoTests.Microsoft.Win32.RegistryKeyTest.CreateSubKey_Name_MaxLength () [0x0004e] in /home/dbn/ports/ports/lang/mono/work/mono-mono-5.2.0.215/mcs/class/corlib/Test/Microsoft.Win32/RegistryKeyTest.cs:610 at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke (System.Reflection.MonoMethod,object,object[],System.Exception&) at System.Reflection.MonoMethod.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00032] in /home/dbn/ports/ports/lang/mono/work/mono-mono-5.2.0.215/mcs/class/corlib/System.Reflection/MonoMethod.cs:305 2) DeleteSubKey_Name_MaxLength (MonoTests.Microsoft.Win32.RegistryKeyTest.DeleteSubKey_Name_MaxLength) System.IO.PathTooLongException : Path is too long. Path: /home/dbn/ports/ports/lang/mono/work/.mono/registry/CurrentUser/software/aa at System.IO.Directory.CreateDirectoriesInternal (System.String path) [0x0005f] in /home/dbn/ports/ports/lang/mono/work/mono-mono-5.2.0.215/mcs/class/corlib/System.IO/Directory.cs:121 at System.IO.Directory.CreateDirectory (System.String path) [0x0008f] in /home/dbn/ports/ports/lang/mono/work/mono-mono-5.2.0.215/mcs/class/corlib/System.IO/Directory.cs:85 at Microsoft.Win32.KeyHandler..ctor (Microsoft.Win32.RegistryKey rkey, System.String basedir, System.Boolean is_volatile) [0x00038] in /home/dbn/ports/ports/lang/mono/work/mono-mono-5.2.0.215/mcs/class/corlib/Microsoft.Win32/UnixRegistryApi.cs:152 at Microsoft.Win32.KeyHandler.Ensure (Microsoft.Win32.RegistryKey rkey, System.String extra, System.Boolean writable, System.Boolean is_volatile) [0x00036] in /home/dbn/ports/ports/lang/mono/work/mono-mono-5.2.0.215/mcs/class/corlib/Microsoft.Win32/UnixRegistryApi.cs:249 at Microsoft.Win32.UnixRegistryApi.CreateSubKey (Microsoft.Win32.RegistryKey rkey, System.String keyname, System.Boolean writable, System.Boolean is_volatile) [0x0002c] in /home/dbn/ports/ports/lang/mono/work/mono-mono-5.2.0.215/mcs/class/corlib/Microsoft.Win32/UnixRegistryApi.cs:1011 at Microsoft.Win32.UnixRegistryApi.CreateSubKey (Microsoft.Win32.RegistryKey rkey, System.String keyname, System.Boolean writable) [0x0] in /home/dbn/ports/ports/lang/mono/work/mono-mono-5.2.0.215/mcs/class/corlib/Microsoft.Win32/UnixRegistryApi.cs:999 at Microsoft.Win32.UnixRegistryApi.CreateSubKey (Microsoft.Win32.RegistryKey rkey, System.String keyname) [0x0] in /home/dbn/ports/ports/lang/mono/work/mono-mono-5.2.0.215/mcs/class/corlib/Microsoft.Win32/UnixRegistryApi.cs:852 at Microsoft.Win32.RegistryKey.CreateSubKey (System.String subkey) [0x00027] in /home/dbn/ports/ports/lang/mono/work/mono-mono-5.2.0.215/mcs/class/corlib/Microsoft.Win32/RegistryKey.cs:515 at (wrapper remoting-invoke-with-check) Microsoft.Win32.RegistryKey:CreateSubKey (string) at MonoTests.Microsoft.Win32.RegistryKeyTest.DeleteSubKey_Name_MaxLength () [0x0001e] in /home/dbn/ports/ports/lang/mono/work/mono-mono-5.2.0.215/mcs/class/corlib/Test/Microsoft.Win32/RegistryKeyTest.cs:1029 at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke (System.Reflection.MonoMethod,object,object[],System.Exception&) at System.Reflection.MonoMethod.Invoke (System.Obje
Re: Mono 5.2 patch and DotNet Core 2 update
On Thu, Jan 11, 2018 at 10:45 AM, David Naylor wrote: > On Wednesday, 10 January 2018 08:55:45 Russell Haley wrote: >> Hi David, >> >> I've successfully built mono based on a modified version of your patch >> from here: https://reviews.freebsd.org/D13752 >> >> I'm getting size and checksum errors for the file >> dotnet-roslyn-322bd5b_GH0.tar.gz. This shouldn't be an issue: I >> changed the size of the file in distinfo from 22058493 to the actual >> size I received of 22058637 in order to make it build. My expectation >> is that I should then run make checksum to fix the distinfo file >> correctly. I run sudo make checksum and the target goes into an >> infinite loop downloading the file, deciding it doesn't match the >> checksum and then downloading it again. WTH? >> >> I am unsure how to proceed. The porters handbook is quite explicit >> that this is the way forward: >> https://www.freebsd.org/doc/en/books/porters-handbook/porting-checksum.html >> >> I have attached what I think is the svn diff that include both your >> patch and my update. The distinfo file should still be incorrect. I >> haven't tested it. I have to get to work . :P >> >> I have cc'd the ports list as well in this conversation. Any input >> from all parties would be grand. > > Thank you for the review - I see you commented on the review. I'll try and > finish the port over the weekend. > > FYI, I have uploaded another two reviews. These combined get the CentOS > version of .NET Core running on FreeBSD :-). > > Regards I'm running the mono tests now. This is awesome: https://reviews.freebsd.org/D13870 Adding dotnet core support via Linux emulation means we can natively build dotnet core 2 via the instructions the instructions here: https://github.com/dotnet/corefx/wiki/Building-.NET-Core--2.x-on-FreeBSD Currently we need an external platform to build the managed system. This is pretty cool, David. I assume MSBuild and Roslyn are in progress? Russ ___ freebsd-mono@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-mono To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org"
Re: Mono 5.2 patch and DotNet Core 2 update
On Thu, Jan 11, 2018 at 10:45 AM, David Naylor wrote: > On Wednesday, 10 January 2018 08:55:45 Russell Haley wrote: >> Hi David, >> >> I've successfully built mono based on a modified version of your patch >> from here: https://reviews.freebsd.org/D13752 >> >> I'm getting size and checksum errors for the file >> dotnet-roslyn-322bd5b_GH0.tar.gz. This shouldn't be an issue: I >> changed the size of the file in distinfo from 22058493 to the actual >> size I received of 22058637 in order to make it build. My expectation >> is that I should then run make checksum to fix the distinfo file >> correctly. I run sudo make checksum and the target goes into an >> infinite loop downloading the file, deciding it doesn't match the >> checksum and then downloading it again. WTH? >> >> I am unsure how to proceed. The porters handbook is quite explicit >> that this is the way forward: >> https://www.freebsd.org/doc/en/books/porters-handbook/porting-checksum.html >> >> I have attached what I think is the svn diff that include both your >> patch and my update. The distinfo file should still be incorrect. I >> haven't tested it. I have to get to work . :P >> >> I have cc'd the ports list as well in this conversation. Any input >> from all parties would be grand. > > Thank you for the review - I see you commented on the review. I'll try and > finish the port over the weekend. > > FYI, I have uploaded another two reviews. These combined get the CentOS > version of .NET Core running on FreeBSD :-). > > Regards Once I get a nice pattern set up for checking these things it should go much more smoothly. Russ ___ freebsd-mono@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-mono To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org"
Re: Mono 5.2 patch and DotNet Core 2 update
On Wednesday, 10 January 2018 08:55:45 Russell Haley wrote: > Hi David, > > I've successfully built mono based on a modified version of your patch > from here: https://reviews.freebsd.org/D13752 > > I'm getting size and checksum errors for the file > dotnet-roslyn-322bd5b_GH0.tar.gz. This shouldn't be an issue: I > changed the size of the file in distinfo from 22058493 to the actual > size I received of 22058637 in order to make it build. My expectation > is that I should then run make checksum to fix the distinfo file > correctly. I run sudo make checksum and the target goes into an > infinite loop downloading the file, deciding it doesn't match the > checksum and then downloading it again. WTH? > > I am unsure how to proceed. The porters handbook is quite explicit > that this is the way forward: > https://www.freebsd.org/doc/en/books/porters-handbook/porting-checksum.html > > I have attached what I think is the svn diff that include both your > patch and my update. The distinfo file should still be incorrect. I > haven't tested it. I have to get to work . :P > > I have cc'd the ports list as well in this conversation. Any input > from all parties would be grand. Thank you for the review - I see you commented on the review. I'll try and finish the port over the weekend. FYI, I have uploaded another two reviews. These combined get the CentOS version of .NET Core running on FreeBSD :-). Regards signature.asc Description: This is a digitally signed message part.
Re: Mono 5.2 patch and DotNet Core 2 update
On Wed, Jan 10, 2018 at 10:50 AM, Steven Hartland wrote: > You want make makesum not make checksum to rebuild the distinfo file Ugh. So...embarassing. The worst part is I did the same thing in reverse when I was checking the targets for Lua53 the other day and spent the better part of an hour not understanding the problem. I quandary why the target isn't called distinfo? Thanks Steven! Russ > On Wed, 10 Jan 2018 at 19:43, Romain Tartière wrote: >> >> On Wed, Jan 10, 2018 at 08:55:45AM -0800, Russell Haley wrote: >> > I'm getting size and checksum errors for the file >> > dotnet-roslyn-322bd5b_GH0.tar.gz. This shouldn't be an issue: I >> > changed the size of the file in distinfo from 22058493 to the actual >> > size I received of 22058637 in order to make it build. My expectation >> > is that I should then run make checksum to fix the distinfo file >> > correctly. I run sudo make checksum and the target goes into an >> > infinite loop downloading the file, deciding it doesn't match the >> > checksum and then downloading it again. WTH? >> >> Since there are checksums, the ports systems must be checking them when >> downloading… and since the checksum does not match, the download is >> assumed to have failed… I guess you can solve this chicken-and-egg >> problem, vy simply removing the existing distinfo file. >> >> The actual files checksums will then be written to distinfo. You can >> `svn diff` to confirm only the expected files have been touched ;-) >> >> Regards, >> Romain >> >> -- >> Romain Tartière http://people.FreeBSD.org/~romain/ >> pgp: 8234 9A78 E7C0 B807 0B59 80FF BA4D 1D95 5112 336F (ID: 0x5112336F) >> (plain text =non-HTML= PGP/GPG encrypted/signed e-mail much appreciated) ___ freebsd-mono@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-mono To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org"
Re: Mono 5.2 patch and DotNet Core 2 update
You want make makesum not make checksum to rebuild the distinfo file On Wed, 10 Jan 2018 at 19:43, Romain Tartière wrote: > On Wed, Jan 10, 2018 at 08:55:45AM -0800, Russell Haley wrote: > > I'm getting size and checksum errors for the file > > dotnet-roslyn-322bd5b_GH0.tar.gz. This shouldn't be an issue: I > > changed the size of the file in distinfo from 22058493 to the actual > > size I received of 22058637 in order to make it build. My expectation > > is that I should then run make checksum to fix the distinfo file > > correctly. I run sudo make checksum and the target goes into an > > infinite loop downloading the file, deciding it doesn't match the > > checksum and then downloading it again. WTH? > > Since there are checksums, the ports systems must be checking them when > downloading… and since the checksum does not match, the download is > assumed to have failed… I guess you can solve this chicken-and-egg > problem, vy simply removing the existing distinfo file. > > The actual files checksums will then be written to distinfo. You can > `svn diff` to confirm only the expected files have been touched ;-) > > Regards, > Romain > > -- > Romain Tartière http://people.FreeBSD.org/~romain/ > pgp: 8234 9A78 E7C0 B807 0B59 80FF BA4D 1D95 5112 336F (ID: 0x5112336F) > (plain text =non-HTML= PGP/GPG encrypted/signed e-mail much appreciated) > ___ freebsd-mono@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-mono To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org"
Re: Mono 5.2 patch and DotNet Core 2 update
On Wed, Jan 10, 2018 at 08:55:45AM -0800, Russell Haley wrote: > I'm getting size and checksum errors for the file > dotnet-roslyn-322bd5b_GH0.tar.gz. This shouldn't be an issue: I > changed the size of the file in distinfo from 22058493 to the actual > size I received of 22058637 in order to make it build. My expectation > is that I should then run make checksum to fix the distinfo file > correctly. I run sudo make checksum and the target goes into an > infinite loop downloading the file, deciding it doesn't match the > checksum and then downloading it again. WTH? Since there are checksums, the ports systems must be checking them when downloading… and since the checksum does not match, the download is assumed to have failed… I guess you can solve this chicken-and-egg problem, vy simply removing the existing distinfo file. The actual files checksums will then be written to distinfo. You can `svn diff` to confirm only the expected files have been touched ;-) Regards, Romain -- Romain Tartière http://people.FreeBSD.org/~romain/ pgp: 8234 9A78 E7C0 B807 0B59 80FF BA4D 1D95 5112 336F (ID: 0x5112336F) (plain text =non-HTML= PGP/GPG encrypted/signed e-mail much appreciated) signature.asc Description: PGP signature
Re: Mono 5.2 patch and DotNet Core 2 update
On Wednesday, 3 January 2018 21:46:39 Russell Haley wrote: > On Wed, Jan 3, 2018 at 11:41 AM, David Naylor wrote: > > On Tuesday, 2 January 2018 22:17:19 Aaron Havens wrote: > >> On Sun, Dec 31, 2017 at 12:31 AM, Russell Haley > >> wrote: > >> > On Thu, Dec 28, 2017 at 9:50 PM, Russell Haley > >> > wrote: > >> > > DotNet Core 2 > >> > > > >> > > Tomas from MS has been building out the Core Framework (corefx) and > >> > > has an "Frankensteins Monster" SDK ready for testing. I have been > >> > > working on getting the Common Language Runtime (coreclr) test suite > >> > > to > >> > > build to validate the system. The working instructions are being > >> > > generated as we go. I've been building the managed parts on Windows, > >> > > while Tomas has been using GNU/Linux for a build platform. I'm hoping > >> > > my work will start to coalesce with Tomas' soon and we can see some > >> > > progress. > > > > Excellent to hear. Any idea as to when FreeBSD will be self-hosting? > > Not sure. If only we knew someone with a Roslyn compiler, msbuild, and > a working Framework on FreeBSD? Hmmm Hmmm, what are you implying ;-). I must admit, I never tried to compile DotNet Core with mono. Do we know if that could work? Also, I had limited success getting DotNet Core to run under our linux emulation (it is, however, quite convenient that we and MS support CentOS). Regards signature.asc Description: This is a digitally signed message part.
Re: Mono 5.2 patch and DotNet Core 2 update
On Wed, Jan 3, 2018 at 11:41 AM, David Naylor wrote: > On Tuesday, 2 January 2018 22:17:19 Aaron Havens wrote: >> On Sun, Dec 31, 2017 at 12:31 AM, Russell Haley >> wrote: >> > On Thu, Dec 28, 2017 at 9:50 PM, Russell Haley >> > wrote: >> > > Hey Guys, >> > > >> > > Merry Christmas! Hope this finds you all well. While free time for me >> > > has been at a premium, I have managed to finally get my hands on a >> > > laptop and cram 16 Gb of ram and a nice big SSD in it. That means I >> > > now have room for lots of VMs. I have a GhostBSD image (FreeBSD 11.1) >> > > and will bring up a TrueOS which is a revision oThe answers to questions >> > > about using Lua are intrinsically answered in the way the book is >> > > written.f CURRENT. Yay for >> > > Virtual Box! > > And happy new year :-) > >> > > Mono 5.2 >> > > >> > > I've created a svn ports repo to mess with and tried out the Mono 5.2 >> > > patch from David. While I ultimately succeeded, the D12440.diff patch >> > > had one error. The chunk was in a RUN_DEPENDS (inconsiquential to the >> > > build) but I patched it manually and ran it. I then found blank patch >> > > files for patch-mono_metadata_socket-io.c, >> > > patch-mono_utils_mono-compiler.h and patch-mono_utils_w32handle.c >> > > (there may have been more, I wasn't careful enough when I was deleting >> > > them). > > Please check the updated patch in (https://reviews.freebsd.org/D13751), I > might need to refresh it for changes in the ports tree. > >> > > After some difficulty with the tarball downloads tThe answers to >> > > questions about using Lua are intrinsically answered in the way the book >> > > is written.iming out, the build >> > > completed successfully! I'll be checking MonoDevelop as well shortly. >> > > I'm hoping David can chime in and we can finish this off? > > Other than things I have overlooked I think we have a ship-able patch. There > are some more things to do, but I don't think show stoppers. It needs to be verifiable, that's all I really meant. >> > So I've had some more time to play with this and the shear breadth of >> > Davids work is staggering. I've suggested in the review that it be >> > broken up into pieces so that it can be digested. Some of this work is >> > important to the DotNet core work; David has a port for msbuild and >> > Rosyln that are really exciting. >> > >> > If David is able to chop the reviews up, is there anyone available to help >> > test? > > I've split the review into 5 sections, 2 with reviews ready: > > - https://reviews.freebsd.org/D13751: ancillary ports > - https://reviews.freebsd.org/D13752: mono (and USES=mono) > - msbuild (depends on mono) > - fsharp (depends on msbuild) > - monodevelop (depends on msbuild) > > I suggest you focus on mono, I'll bang out the ancillary ports (hopefully > tomorrow). Great work. Thanks and I'm on it. >> > Russ >> >> I am willing to help test. Just may need some guidance on where to start >> and what is needed. > > I suggest you try build mono (https://reviews.freebsd.org/D13752). You can > test by: > - running the unit tests (i.e. `make test`) > - run your favourite mono apps > - try some random mono apps in the ports collection > >> > > DotNet Core 2 >> > > >> > > Tomas from MS has been building out the Core Framework (corefx) and >> > > has an "Frankensteins Monster" SDK ready for testing. I have been >> > > working on getting the Common Language Runtime (coreclr) test suite to >> > > build to validate the system. The working instructions are being >> > > generated as we go. I've been building the managed parts on Windows, >> > > while Tomas has been using GNU/Linux for a build platform. I'm hoping >> > > my work will start to coalesce with Tomas' soon and we can see some >> > > progress. > > Excellent to hear. Any idea as to when FreeBSD will be self-hosting? Not sure. If only we knew someone with a Roslyn compiler, msbuild, and a working Framework on FreeBSD? Hmmm > Regards > > David ___ freebsd-mono@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-mono To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org"
Re: Mono 5.2 patch and DotNet Core 2 update
On Tuesday, 2 January 2018 22:17:19 Aaron Havens wrote: > On Sun, Dec 31, 2017 at 12:31 AM, Russell Haley > wrote: > > On Thu, Dec 28, 2017 at 9:50 PM, Russell Haley > > wrote: > > > Hey Guys, > > > > > > Merry Christmas! Hope this finds you all well. While free time for me > > > has been at a premium, I have managed to finally get my hands on a > > > laptop and cram 16 Gb of ram and a nice big SSD in it. That means I > > > now have room for lots of VMs. I have a GhostBSD image (FreeBSD 11.1) > > > and will bring up a TrueOS which is a revision of CURRENT. Yay for > > > Virtual Box! And happy new year :-) > > > Mono 5.2 > > > > > > I've created a svn ports repo to mess with and tried out the Mono 5.2 > > > patch from David. While I ultimately succeeded, the D12440.diff patch > > > had one error. The chunk was in a RUN_DEPENDS (inconsiquential to the > > > build) but I patched it manually and ran it. I then found blank patch > > > files for patch-mono_metadata_socket-io.c, > > > patch-mono_utils_mono-compiler.h and patch-mono_utils_w32handle.c > > > (there may have been more, I wasn't careful enough when I was deleting > > > them). Please check the updated patch in (https://reviews.freebsd.org/D13751), I might need to refresh it for changes in the ports tree. > > > After some difficulty with the tarball downloads timing out, the build > > > completed successfully! I'll be checking MonoDevelop as well shortly. > > > I'm hoping David can chime in and we can finish this off? Other than things I have overlooked I think we have a ship-able patch. There are some more things to do, but I don't think show stoppers. > > So I've had some more time to play with this and the shear breadth of > > Davids work is staggering. I've suggested in the review that it be > > broken up into pieces so that it can be digested. Some of this work is > > important to the DotNet core work; David has a port for msbuild and > > Rosyln that are really exciting. > > > > If David is able to chop the reviews up, is there anyone available to help > > test? I've split the review into 5 sections, 2 with reviews ready: - https://reviews.freebsd.org/D13751: ancillary ports - https://reviews.freebsd.org/D13752: mono (and USES=mono) - msbuild (depends on mono) - fsharp (depends on msbuild) - monodevelop (depends on msbuild) I suggest you focus on mono, I'll bang out the ancillary ports (hopefully tomorrow). > > Russ > > I am willing to help test. Just may need some guidance on where to start > and what is needed. I suggest you try build mono (https://reviews.freebsd.org/D13752). You can test by: - running the unit tests (i.e. `make test`) - run your favourite mono apps - try some random mono apps in the ports collection > > > DotNet Core 2 > > > > > > Tomas from MS has been building out the Core Framework (corefx) and > > > has an "Frankensteins Monster" SDK ready for testing. I have been > > > working on getting the Common Language Runtime (coreclr) test suite to > > > build to validate the system. The working instructions are being > > > generated as we go. I've been building the managed parts on Windows, > > > while Tomas has been using GNU/Linux for a build platform. I'm hoping > > > my work will start to coalesce with Tomas' soon and we can see some > > > progress. Excellent to hear. Any idea as to when FreeBSD will be self-hosting? Regards David signature.asc Description: This is a digitally signed message part.
Re: Mono 5.2 patch and DotNet Core 2 update
On Sun, Dec 31, 2017 at 12:31 AM, Russell Haley wrote: > On Thu, Dec 28, 2017 at 9:50 PM, Russell Haley > wrote: > > Hey Guys, > > > > Merry Christmas! Hope this finds you all well. While free time for me > > has been at a premium, I have managed to finally get my hands on a > > laptop and cram 16 Gb of ram and a nice big SSD in it. That means I > > now have room for lots of VMs. I have a GhostBSD image (FreeBSD 11.1) > > and will bring up a TrueOS which is a revision of CURRENT. Yay for > > Virtual Box! > > > > Mono 5.2 > > > > I've created a svn ports repo to mess with and tried out the Mono 5.2 > > patch from David. While I ultimately succeeded, the D12440.diff patch > > had one error. The chunk was in a RUN_DEPENDS (inconsiquential to the > > build) but I patched it manually and ran it. I then found blank patch > > files for patch-mono_metadata_socket-io.c, > > patch-mono_utils_mono-compiler.h and patch-mono_utils_w32handle.c > > (there may have been more, I wasn't careful enough when I was deleting > > them). > > > > After some difficulty with the tarball downloads timing out, the build > > completed successfully! I'll be checking MonoDevelop as well shortly. > > I'm hoping David can chime in and we can finish this off? > > So I've had some more time to play with this and the shear breadth of > Davids work is staggering. I've suggested in the review that it be > broken up into pieces so that it can be digested. Some of this work is > important to the DotNet core work; David has a port for msbuild and > Rosyln that are really exciting. > > If David is able to chop the reviews up, is there anyone available to help > test? > > Russ > I am willing to help test. Just may need some guidance on where to start and what is needed. Aaron > > DotNet Core 2 > > > > Tomas from MS has been building out the Core Framework (corefx) and > > has an "Frankensteins Monster" SDK ready for testing. I have been > > working on getting the Common Language Runtime (coreclr) test suite to > > build to validate the system. The working instructions are being > > generated as we go. I've been building the managed parts on Windows, > > while Tomas has been using GNU/Linux for a build platform. I'm hoping > > my work will start to coalesce with Tomas' soon and we can see some > > progress. > > > > Tomas, can you add anything? > > > > Anyway, hope springs eternal in the new year. > > > > Cheers, > > Russ > ___ > freebsd-mono@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-mono > To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org" > ___ freebsd-mono@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-mono To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org"
Re: Mono 5.2 patch and DotNet Core 2 update
On Thu, Dec 28, 2017 at 9:50 PM, Russell Haley wrote: > Hey Guys, > > Merry Christmas! Hope this finds you all well. While free time for me > has been at a premium, I have managed to finally get my hands on a > laptop and cram 16 Gb of ram and a nice big SSD in it. That means I > now have room for lots of VMs. I have a GhostBSD image (FreeBSD 11.1) > and will bring up a TrueOS which is a revision of CURRENT. Yay for > Virtual Box! > > Mono 5.2 > > I've created a svn ports repo to mess with and tried out the Mono 5.2 > patch from David. While I ultimately succeeded, the D12440.diff patch > had one error. The chunk was in a RUN_DEPENDS (inconsiquential to the > build) but I patched it manually and ran it. I then found blank patch > files for patch-mono_metadata_socket-io.c, > patch-mono_utils_mono-compiler.h and patch-mono_utils_w32handle.c > (there may have been more, I wasn't careful enough when I was deleting > them). > > After some difficulty with the tarball downloads timing out, the build > completed successfully! I'll be checking MonoDevelop as well shortly. > I'm hoping David can chime in and we can finish this off? So I've had some more time to play with this and the shear breadth of Davids work is staggering. I've suggested in the review that it be broken up into pieces so that it can be digested. Some of this work is important to the DotNet core work; David has a port for msbuild and Rosyln that are really exciting. If David is able to chop the reviews up, is there anyone available to help test? Russ > DotNet Core 2 > > Tomas from MS has been building out the Core Framework (corefx) and > has an "Frankensteins Monster" SDK ready for testing. I have been > working on getting the Common Language Runtime (coreclr) test suite to > build to validate the system. The working instructions are being > generated as we go. I've been building the managed parts on Windows, > while Tomas has been using GNU/Linux for a build platform. I'm hoping > my work will start to coalesce with Tomas' soon and we can see some > progress. > > Tomas, can you add anything? > > Anyway, hope springs eternal in the new year. > > Cheers, > Russ ___ freebsd-mono@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-mono To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org"
Mono 5.2 patch and DotNet Core 2 update
Hey Guys, Merry Christmas! Hope this finds you all well. While free time for me has been at a premium, I have managed to finally get my hands on a laptop and cram 16 Gb of ram and a nice big SSD in it. That means I now have room for lots of VMs. I have a GhostBSD image (FreeBSD 11.1) and will bring up a TrueOS which is a revision of CURRENT. Yay for Virtual Box! Mono 5.2 I've created a svn ports repo to mess with and tried out the Mono 5.2 patch from David. While I ultimately succeeded, the D12440.diff patch had one error. The chunk was in a RUN_DEPENDS (inconsiquential to the build) but I patched it manually and ran it. I then found blank patch files for patch-mono_metadata_socket-io.c, patch-mono_utils_mono-compiler.h and patch-mono_utils_w32handle.c (there may have been more, I wasn't careful enough when I was deleting them). After some difficulty with the tarball downloads timing out, the build completed successfully! I'll be checking MonoDevelop as well shortly. I'm hoping David can chime in and we can finish this off? DotNet Core 2 Tomas from MS has been building out the Core Framework (corefx) and has an "Frankensteins Monster" SDK ready for testing. I have been working on getting the Common Language Runtime (coreclr) test suite to build to validate the system. The working instructions are being generated as we go. I've been building the managed parts on Windows, while Tomas has been using GNU/Linux for a build platform. I'm hoping my work will start to coalesce with Tomas' soon and we can see some progress. Tomas, can you add anything? Anyway, hope springs eternal in the new year. Cheers, Russ ___ freebsd-mono@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-mono To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org"
