Re: [Mono-dev] Building a Mono RPM

2013-08-27 Thread Rafael Teixeira
It just sounds strange that you are trying to build an RPM package on a system based on DEB packaging, in Ubuntu it would be easier to package a .deb package to target Debian-based distros like Debian/Ubuntu/Mint/etc... or switch to Fedora as your distro for building and packaging if you are

Re: [Mono-dev] Request for status of Entity framework on Mono

2013-08-27 Thread Mitchell Jonathan
Hi I have done some experimenting with the latest MS Entity 6 beta and the Devart SQLite data provider. I was able to query quite a substantial pre-existing data set when running on Mono. So it is doable. Jonathan On 19 Aug 2013, at 00:17, Martin Thwaites monofo...@my2cents.co.uk wrote:

[Mono-dev] Small issues with the Windows msvc builds, and how I got around them

2013-08-27 Thread Alex Forster
Referring to commit 29c42bf0dc— just a few tips on how I got the -sgen configurations to compile in 32bit release mode with Visual Studio 2012. First issue— msvcrt apparently doesn’t implement _strtoull(). According to this Connect article[1], the functionality exists as _strtoui64(). So, as

Re: [Mono-dev] Building a Mono RPM

2013-08-27 Thread Chris Tacke
So as a bit of background, this is what I’m doing. I am building an embedded Linux platform running Wind River, which I believe is Fedora based. The tools for building the OS came on a Ubuntu VM. I am trying to build Mono (succeeded there), and then an installer for Mono so that I can

[Mono-dev] Entity Framework crash in System.Reflection.AssemblyName.ReferenceMatchesDefinition

2013-08-27 Thread mlgo
Has anyone figured this out yet?. Either this is going to have to be implemented or the Entity Framwork needs to avoid calling it. There is a stacktrace at the bottom of this message. System.Reflection.AssemblyName.ReferenceMatchesDefinition is not implemented. I guess developers have been

[Mono-dev] A possible implementation for AssemblyName.ReferenceMatchesDefinition

2013-08-27 Thread mlgo
According to http://msdn.microsoft.com/en-us/library/system.reflection.assemblyname.referencematchesdefinition.aspx The following is what is expected to be returned from ReferenceMatchesDefinition. Returns a value indicating whether two assembly names are the same. The comparison is based on

Re: [Mono-dev] SGEN support when cross compiling

2013-08-27 Thread Rodrigo Kumpera
All this means is that the managed allocators won't be used. On Mon, Aug 26, 2013 at 8:07 PM, Bassam Tabbara bas...@symform.com wrote: I tried that and I run into the following error when I run mono: sgen is not supported when using --with-tls=pthread Looking at the code here:

Re: [Mono-dev] SGEN support when cross compiling

2013-08-27 Thread Bassam Tabbara
Should it be a warning then? The runtime aborts after this error. The only workaround I've found so far is: https://github.com/symform/mono/commit/fe5c582a1a2d241f368c86081b3cb7ea53994f51 And sgen is running well now with a cross compiled mono. From: Rodrigo Kumpera

Re: [Mono-dev] A possible implementation for AssemblyName.ReferenceMatchesDefinition

2013-08-27 Thread Stifu
If I'm not mistaken, the last 2 tests are redundant. You're basically doing the same test twice. So I guess this could be simplified to something like: public static bool ReferenceMatchesDefinition (AssemblyName reference, AssemblyName definition) {

Re: [Mono-dev] Building a Mono RPM

2013-08-27 Thread Chris Tacke
Well that seems to have been a huge waste of time. I built up a Fedora 18 machine, installed all of the packages necessary for building, pulled the source for mono, did a configure, make and a make install. All went fine. I then tried to use rpmbuild and again, I get the following error (just

Re: [Mono-dev] Small issues with the Windows msvc builds, and how I got around them

2013-08-27 Thread Jean-Michel.Perraud
Hi Alex, Thanks for the information; I sometimes need to dive into the C code to get it to compile under MSVC and your heads up is a time saver. You may want to fork+branch and do a pull request if you think these fixes are not temporary hacks. profiler-cov is a .vcxproj file, and AFAIK not

Re: [Mono-dev] A possible implementation for AssemblyName.ReferenceMatchesDefinition

2013-08-27 Thread Daniel Lo Nigro
You may want to ignore culture and case in your comparison: return reference.Name.Equals(definition.Name, StringComparison.InvariantCultureIgnoreCase) On Wed, Aug 28, 2013 at 1:29 AM, mlgo mlint...@sinenomine.net wrote: According to

Re: [Mono-dev] A possible implementation for AssemblyName.ReferenceMatchesDefinition

2013-08-27 Thread mlgo
Right. Thanks. I hadn't thought about that. I keep suspecting that the documentation is not right though. That in fact what needs to be done is determine if the names actually refer to the same dll. Hopefully someone can reply to this who knows more about the internals of this. Otherwise I need

Re: [Mono-dev] A possible implementation for AssemblyName.ReferenceMatchesDefinition

2013-08-27 Thread Daniel Lo Nigro
It looks like the behaviour may have changed between .NET versions... The MSDN page for .NET Framework 3.5 onwards (including 4.5) states: Returns a value indicating whether two assembly names are the same. The comparison is based on the simple assembly names. return value - true if the simple