Re: [Mono-dev] Building mono-core

2018-02-02 Thread Neale Ferguson
I assume System.Reflection.Metadata.dll is still housed at Microsoft and the big-endian fix for it that enables Roslyn to run is still to surface? From: Jo Shields > Date: Friday, February 2, 2018 at 12:42 PM To: Alexander Köplinger

Re: [Mono-dev] Building mono-core

2018-02-02 Thread Alexander Köplinger via Mono-devel-list
Hm, that's a packaging question for Jo (added on CC). On 2 Feb 2018, at 18:03, Neale Ferguson > wrote: What’s the proposed fix for msbuild living in –devel and msbuild? Will msbuild contain all the Roslyn stuff that can be removed from -devel?

Re: [Mono-dev] Building mono-core

2018-02-02 Thread Jo Shields via Mono-devel-list
Relevant pull request: https://github.com/mono/mono/pull/5251 Mono is now the canonical home of Roslyn, and MSbuild uses the Mono-provided binaries, not its own. Sent from Outlook From: Alexander Köplinger Sent: 02 February 2018

[Mono-dev] nuget

2018-02-02 Thread Neale Ferguson
What’s the latest version of Nuget on the download site? I am still not seeing the 5.8 stuff for mono so am not sure what the latest nuget is. 2.12 is what shows at the moment. Neale ___ Mono-devel-list mailing list Mono-devel-list@lists.dot.net

[Mono-dev] Autoconf 2.64

2018-02-02 Thread Neale Ferguson
I noticed with a pull from master today that Autoconf 2.64 is now required. One of my builders (also used by Jenkins) is running SLES11SP3 which only has 2.63 Neale ___ Mono-devel-list mailing list Mono-devel-list@lists.dot.net

Re: [Mono-dev] Building mono-core

2018-02-02 Thread Neale Ferguson
Hey Neale, would you mind opening a pull request on GitHub with the BTLS changes for s390x? - Will do. I’ll checkout the latest copy and reapply Could you please list which pdb's it complains about? - All of them. No pdb files are created for the s390x build. What are they and how are the

Re: [Mono-dev] Building mono-core

2018-02-02 Thread Jo Shields via Mono-devel-list
Looks like corefx owns it. I don't see an open issue on GH about it though? Am I looking in the wrong place, Alex? Get Outlook for iOS From: Neale Ferguson Sent: Friday, February 2, 2018 12:49:45 PM To: Jo Shields;

Re: [Mono-dev] Building mono-core

2018-02-02 Thread Jo Shields via Mono-devel-list
I guess the question is "whose System.Reflection.Metadata is used, when, by whom?" i.e. where does the fix exist and not exist? Sent from Outlook From: Neale Ferguson Sent: 02 February 2018 14:17 To: Alexander

Re: [Mono-dev] Building NuGet

2018-02-02 Thread Neale Ferguson
Ah, tks. I think I was told this before and promptly forgot! We no longer build nuget ourselves but just get it from nuget.org: https://www.nuget.org/downloads (the Windows x86 Commandline name is a bit misleading, it works just fine on Unix). We package that .exe with

Re: [Mono-dev] Building mono-core

2018-02-02 Thread Alexander Köplinger via Mono-devel-list
Hmm, the question is if the System.Reflection.Metadata.dll wasn't updated in Roslyn yet or there's some other issue. Marek might now more about it. On 2 Feb 2018, at 20:17, Neale Ferguson > wrote: Did. Still throwing the “Not little endian”

Re: [Mono-dev] Building NuGet

2018-02-02 Thread Alexander Köplinger via Mono-devel-list
We no longer build nuget ourselves but just get it from nuget.org: https://www.nuget.org/downloads (the Windows x86 Commandline name is a bit misleading, it works just fine on Unix). We package that .exe with https://github.com/mono/linux-packaging-nuget/tree/centos On 2 Feb

Re: [Mono-dev] Building mono-core

2018-02-02 Thread Neale Ferguson
Did. Still throwing the “Not little endian” exception. If I remember correctly the issue was fixed in System.Reflection.Metadata.dll but Roslyn still needed to pick up the fixed version. That might have happened in the meantime, best to just try :)

[Mono-dev] Building NuGet

2018-02-02 Thread Neale Ferguson
Using the 2.12 src RPM to build NuGet fails on s390x as it is defaulting to csc. How do I override this? ___ Mono-devel-list mailing list Mono-devel-list@lists.dot.net http://lists.dot.net/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Autoconf 2.64

2018-02-02 Thread Alexander Köplinger via Mono-devel-list
Hmm, I'm not aware of any explicit bump in autoconf version, might be a mistake. In fact, it looks like we even commented the #AC_PREREQ([2.62]) in configure.ac :D Where do you get an error? On 2 Feb 2018, at 19:33, Neale Ferguson > wrote: I

Re: [Mono-dev] Building mono-core

2018-02-02 Thread Alexander Köplinger via Mono-devel-list
We're taking it from https://github.com/mono/roslyn-binaries/tree/master/Microsoft.Net.Compilers/Microsoft.Net.Compilers.2.6.0/tools which afaik is just straight from the roslyn nuget package. On 2 Feb 2018, at 20:53, Jo Shields > wrote: I

[Mono-dev] Failing Tests

2018-02-02 Thread Neale Ferguson
Running the tests on my s390x 5.8 build show numerous failures with messages like below. The confusing bit is that isn’t SIG37 used by GC? There also errors relating to SIG36 being received (which is also GC related). threadpool-exceptions2.exe ===

Re: [Mono-dev] Autoconf 2.64

2018-02-02 Thread Alexander Köplinger via Mono-devel-list
Ah, this is because of https://github.com/mono/mono/commit/4a995045915dbe45918787d158485dda26660e05, looks like the new m4 file has AC_PREREQ(2.64). I'll talk to the engineer who wrote it. On 2 Feb 2018, at 20:18, Neale Ferguson > wrote:

Re: [Mono-dev] Building mono-core

2018-02-02 Thread Alexander Köplinger via Mono-devel-list
If I remember correctly the issue was fixed in System.Reflection.Metadata.dll but Roslyn still needed to pick up the fixed version. That might have happened in the meantime, best to just try :) On 2 Feb 2018, at 19:03, Jo Shields > wrote:

Re: [Mono-dev] Autoconf 2.64

2018-02-02 Thread Neale Ferguson
Thanks Ah, this is because of https://github.com/mono/mono/commit/4a995045915dbe45918787d158485dda26660e05, looks like the new m4 file has AC_PREREQ(2.64). I'll talk to the engineer who wrote it. ___ Mono-devel-list mailing list

Re: [Mono-list] Repository problem

2018-02-02 Thread Alexander Köplinger via Mono-list
I added Jo in CC who is our Linux packaging expert. @Jo: should we direct users to the mono-devel list instead? - Alex > On 2 Feb 2018, at 10:30, Guy wrote: > > Hello list members, > > There's a problem with the repository for Debian Wheezy. I reported that > problem on

Re: [Mono-list] Repository problem

2018-02-02 Thread Jo Shields via Mono-list
Yeah. Or Gitter. As for the issue at hand, I don't see a problem? directhex@origin-download:/srv/www/mono/repo/debian/dists$ gpg --verify wheezy/snapshots/4.2.3/Release.gpg wheezy/snapshots/4.2.3/Release gpg: Signature made Mon 13 Jun 2016 10:26:19 AM UTC using RSA key ID D3D831EF