Re: [Mono-dev] Building mono-core

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] Autoconf 2.64

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] Autoconf 2.64

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 NuGet

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

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] Building mono-core

to:mono-devel-list@lists.dot.net>> Subject: Re: [Mono-dev] Building mono-core Ahh, sorry, you're talking about the mono-core.spec :D Yes, replacing .pdb there should work. I guess we can take that improvement as well? On 2 Feb 2018, at 17:41, Alexander Köplinger via Mono-devel-list <m

Re: [Mono-dev] Building mono-core

Hey Neale, would you mind opening a pull request on GitHub with the BTLS changes for s390x? Could you please list which pdb's it complains about? - Alex On 1 Feb 2018, at 21:44, Neale Ferguson > wrote: Hi, I found the 5.8 src rpm (thanks

Re: [Mono-dev] Unable to Build Mono

Hmm, it might be that compiling with net_4_x.sln is broken at the moment (it is a work in progress, our recommended approach for building Mono are the Makefiles). On 1 Feb 2018, at 01:49, Vishnu Kalapur > wrote: Hi Axel, Sorry to bother

Re: [Mono-dev] Unable to Build Mono

We rely on newer C#7 features that don't work with the C# compiler included in VS2015, you'll need to upgrade to VS2017 (Community edition is fine). - Alex On 31 Jan 2018, at 23:19, Vishnu Kalapur > wrote: Hi Alex, Thank you for the

Re: [Mono-dev] Building linker

Hmm, it's building with xbuild. Did you override this since according to the Makefile it should use msbuild. xbuild references /usr/lib/cli/nunit.framework-2.6.3/nunit.framework.dll instead of NUnit from the nuget package when building Mono.Linker.Tests.dll, maybe that's the issue. On 30 Jan

Re: [Mono-dev] Building linker

Can you post a full build log? Did you modify 3.6.1 to 3.8.0 everywhere? It looks like the test dll wasn't built. For real world use the readme here has examples: https://github.com/mono/linker/blob/master/linker/README On 30 Jan 2018, at 19:18, Neale Ferguson

Re: [Mono-dev] Building linker

We just run "check" in monobuild in CI, that seems to work. On 30 Jan 2018, at 18:52, Neale Ferguson > wrote: I got a clean build in mono build (check failed though). I also ran bootstrap & build in core build. Again, all clean. How do I test

Re: [Mono-dev] Building linker

Could you please try with a more recent Mono, e.g. 5.4.1 ? We build it in CI and it's green there. - Alex On 29 Jan 2018, at 22:10, Neale Ferguson > wrote: Hi, I am trying to build the linker from master and after installing the NUnit

Re: [Mono-dev] Build error

Is this using system mcs or monolite? Actually @Marek I think we'll need to bump corlib version when a new mcs is required in monolite (i.e. due to new features used in corefx), could this be the issue here? - Alex On 4 Jan 2018, at 18:42, Neale Ferguson

Re: [Mono-dev] MoMA

I'm not aware of any active efforts to resurrect MoMA (i.e. the data it relies on is still outdated). /cc Marek please correct me if I'm wrong :) - Alex On 21 Dec 2017, at 03:31, Neale Ferguson > wrote: I replaced the hint with a pointer to

Re: [Mono-dev] Compatibility

.NET 4.7 didn't add a lot of new APIs (https://github.com/Microsoft/dotnet/blob/master/releases/net47/dotnet47-api-changes.md), most notably was ValueTuple so I added that to the page, thanks. Generally the C# version is now more decoupled from the .NET version, so a new C# release doesn't

Re: [Mono-dev] w32process-unix

Yep, this was caused by https://github.com/mono/mono/pull/5759, can you please send a pull request with the fix? - Alex On 14 Nov 2017, at 06:10, Neale Ferguson > wrote: Hi, Build fails on s390x (big-endian) due to error in w32process-unix.c:

Re: [Mono-dev] Sync of mono Cert Store

When Mono is installed from our packages (specifically the ca-certificates-mono package*), we're adding a hook into /etc/ca-certificates/update.d/ which runs cert-sync automatically whenever the system certificates are updated by the update-ca-certificates command. This is the same approach

Re: [Mono-dev] Bundled mono Certificate Store

We had a discussion related to this recently in the mkbundle context: https://www.mail-archive.com/mono-devel-list@lists.dot.net/msg00529.html At the moment it seems there's no supported way of changing the path, other than changing the source. - Alex On 13 Jul 2017, at 17:52, Rick Tillery

Re: [Mono-dev] How to find out what framework runtimes installed

In general, you shouldn't need to care about the .NET Framework profile your app is compiled against when running it on (newer) Mono. Today*, we only ship a single set of assemblies which implement the BCL (mscorlib, System.*) so your app always runs on those no matter what profile it was

Re: [Mono-dev] Building Mono 5.0.0.100 failed on Raspberry Pi

It seems there's a misunderstanding: the Raspbian repository should work on ARMv6 devices, it is there for these cases. What I meant is that specifically the _Debian_ repository doesn't support ARMv6 because of how Debian defines the armhf architecture. Can you show me a log of the error you

Re: [Mono-dev] Building Mono 5.0.0.100 failed on Raspberry Pi

You can temporarily revert back to building Mono with mcs instead of csc by passing --with-csc=mcs to autogen.sh/configure (this is broken in latest gist so please try it on the tarball release). Anyway, this looks like a bug so would be good to get a bug report on https://bugzilla.xamarin.com

Re: [Mono-dev] dlopen(libSystem.Data.dll, 9): image not found

Yep, it does indeed come from referencesource: https://github.com/mono/mono/blob/d01c819b05550d430d3c1bf0cc6842a2e8a47a0d/mcs/class/referencesource/System.Data/System/Data/Common/System.Data_BID.cs#L70 This should be harmless as I don't think any code on Mono reaches this (otherwise you'd get a

Re: [Mono-dev] dlopen(libSystem.Data.dll, 9): image not found

That's weird, System.Data.dll is a .NET Framework / BCL assembly so P/Invoking into it doesn't make sense. - Alex > On 01 Mar 2017, at 15:54, Jonathan Mitchell wrote: > > While fixing a Dll import issue on MacOS I noticed the following: > > Mono: DllImport error loading

Re: [Mono-dev] Internal runtime documentation with Doxygen

On 07 Feb 2017, at 22:04, Oskar Berggren <oskar.bergg...@gmail.com<mailto:oskar.bergg...@gmail.com>> wrote: 2017-02-07 16:38 GMT+00:00 Alexander Köplinger via Mono-devel-list <mono-devel-list@lists.dot.net<mailto:mono-devel-list@lists.dot.net>>: Hey Jon/community, This i

Re: [Mono-dev] Internal runtime documentation with Doxygen

Hey Jon/community, This is now available as http://www.mono-project.com/api/ ! - Alex On 07 Feb 2017, at 01:26, Jon Purdy via Mono-devel-list > wrote: We’ve recently added initial support for building Doxygen

Re: [Mono-dev] __MonoCS__ no longer defined?

No, this shouldn't work as far as I'm aware since you're still only setting an msbuild property with /p which doesn't get passed down into the compiler invocation. Try "xbuild /v:diag" to get a verbose log and search for the line where csc is invoked to see what exactly gets defined - Alex >

Re: [Mono-dev] __MonoCS__ no longer defined?

__MonoCS__ is a define in C# source, not an msbuild property (which the /p sets). You need to add __MonoCS__ to in your csproj. - Alex > On 04 Jan 2017, at 23:13, Greg Young wrote: > > Also it appears > > ➜ shitbird xbuild /p:__MonoCS__="true" >

Re: [Mono-dev] Build Errors

Hi Greg, that can sometimes happen due to dependency tracking not being 100% perfect for Mono.Security. Do rm -rf mcs/class/lib so you don't have any left over assemblies from earlier builds and build again. - Alex > On 06 Dec 2016, at 14:08, Greg Young wrote: > >