Hi Peter, I might be wrong but I *think* this is something to do with the current version of Mono on your machine. If it's of a certain vintage then it can't be used build the latest C# code that's part of Mono. I think you can either remove the current mono (or at least hide it) and let the build process sort it out, or upgrade in increments. e.g If you have 3.2.x now, don't try to go straight to 3.8, but do 3.4, 3.6 etc first.
Again, I could be wrong but this rings a bell. Good luck! Steve H On 12 Sep 2014, at 07:37, Peter Hagen <pe...@willow-media.nl> wrote: > Hi, > > I’m trying to build mono 3.8 from git, but I get an error: > > System.Security.AccessControl/SemaphoreSecurity.cs(136,35): warning CS0109: > The member > `System.Security.AccessControl.SemaphoreSecurity.PersistModifications(System.Runtime.InteropServices.SafeHandle)' > does not hide an inherited member. The new keyword is not required > Mono.Http/NtlmClient.cs(99,54): error CS1502: The best overloaded method > match for `Mono.Security.Protocol.Ntlm.Type3Message.Type3Message(byte[])' has > some invalid arguments > /usr/lib/mono/gac/Mono.Security/2.0.0.0__0738eb9f132ed756/Mono.Security.dll > (Location of the symbol related to previous error) > Mono.Http/NtlmClient.cs(99,54): error CS1503: Argument `#1' cannot convert > `Mono.Security.Protocol.Ntlm.Type2Message' expression to type `byte[]' > Compilation failed: 2 error(s), 1 warnings > > I just cloned the repository and switch to the mono-3.8-branch and started > building. Is this a known issue? > > Grz > > Peter Hagen > > _______________________________________________ > Mono-list maillist - Mono-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-list
_______________________________________________ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
