Re: [Mono-dev] [Mono-list] How to run full mono test suites
I run this to test the C# code. cd mcs/class/corlib make run-test PROFILE=net_4_5 On Tue, Sep 2, 2014 at 8:16 PM, Liwei Peng liwei.p...@microsoft.com wrote: I didn’t see the ‘make test’ rule under the root source directory. Where do you run it? *From:* mar...@my2cents.co.uk [mailto:mar...@my2cents.co.uk] *On Behalf Of *Martin Thwaites *Sent:* Tuesday, September 2, 2014 5:07 PM *To:* Liwei Peng *Cc:* mono-l...@lists.ximian.com; mono-devel-list *Subject:* Re: [Mono-dev] How to run full mono test suites Does a simple make test not run all the tests? Or are you looking for something else? On 2 Sep 2014 22:59, Liwei Peng liwei.p...@microsoft.com wrote: Hi Mono, I am evaluating mono on a Linux machine (Ubuntu). I’d like to run the full test suites published on this website: https://wrench.mono-project.com/Wrench/ While this link http://www.mono-project.com/community/contributing/test-suite/ has some general description on the test framework, my question is: is there existing script or document that I can use to run the full test suites? So that I don’t need to spend time to check each class library or runtime tests individually? Thanks, Liwei ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-list maillist - mono-l...@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] [Mono-list] How to run full mono test suites
On Tue, Sep 2, 2014 at 8:45 PM, Liwei Peng liwei.p...@microsoft.com wrote: Thanks Michael. That’s one library. When I checked here https://wrench.mono-project.com/Wrench/ViewLane.aspx?lane_id=14host_id=10revision_id=74118, there are many libraries like below. I am wondering whether there is a quick way to run all of them *From:* Michael Franz [mailto:mvfr...@gmail.com] *Sent:* Tuesday, September 2, 2014 5:18 PM *To:* Liwei Peng *Cc:* Martin Thwaites; mono-l...@lists.ximian.com; mono-devel-list *Subject:* Re: [Mono-list] [Mono-dev] How to run full mono test suites I run this to test the C# code. cd mcs/class/corlib make run-test PROFILE=net_4_5 On Tue, Sep 2, 2014 at 8:16 PM, Liwei Peng liwei.p...@microsoft.com wrote: I didn’t see the ‘make test’ rule under the root source directory. Where do you run it? *From:* mar...@my2cents.co.uk [mailto:mar...@my2cents.co.uk] *On Behalf Of *Martin Thwaites *Sent:* Tuesday, September 2, 2014 5:07 PM *To:* Liwei Peng *Cc:* mono-l...@lists.ximian.com; mono-devel-list *Subject:* Re: [Mono-dev] How to run full mono test suites Does a simple make test not run all the tests? Or are you looking for something else? On 2 Sep 2014 22:59, Liwei Peng liwei.p...@microsoft.com wrote: Hi Mono, I am evaluating mono on a Linux machine (Ubuntu). I’d like to run the full test suites published on this website: https://wrench.mono-project.com/Wrench/ While this link http://www.mono-project.com/community/contributing/test-suite/ has some general description on the test framework, my question is: is there existing script or document that I can use to run the full test suites? So that I don’t need to spend time to check each class library or runtime tests individually? Thanks, Liwei ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-list maillist - mono-l...@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list I think it is 'make check' ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-list] [Mono-dev] How to run full mono test suites
I run this to test the C# code. cd mcs/class/corlib make run-test PROFILE=net_4_5 On Tue, Sep 2, 2014 at 8:16 PM, Liwei Peng liwei.p...@microsoft.com wrote: I didn’t see the ‘make test’ rule under the root source directory. Where do you run it? *From:* mar...@my2cents.co.uk [mailto:mar...@my2cents.co.uk] *On Behalf Of *Martin Thwaites *Sent:* Tuesday, September 2, 2014 5:07 PM *To:* Liwei Peng *Cc:* mono-list@lists.ximian.com; mono-devel-list *Subject:* Re: [Mono-dev] How to run full mono test suites Does a simple make test not run all the tests? Or are you looking for something else? On 2 Sep 2014 22:59, Liwei Peng liwei.p...@microsoft.com wrote: Hi Mono, I am evaluating mono on a Linux machine (Ubuntu). I’d like to run the full test suites published on this website: https://wrench.mono-project.com/Wrench/ While this link http://www.mono-project.com/community/contributing/test-suite/ has some general description on the test framework, my question is: is there existing script or document that I can use to run the full test suites? So that I don’t need to spend time to check each class library or runtime tests individually? Thanks, Liwei ___ Mono-devel-list mailing list mono-devel-l...@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ 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
Re: [Mono-dev] Repeat builds of core assemblies
On Tue, Apr 22, 2014 at 3:53 PM, Miguel de Icaza mig...@xamarin.com wrote: Hey guys, I was looking at making the MSBuild system work, and during the process I have encountered a few problems that we have in our existing build system that are problematic. The problem is that System, System.XML and System.Configuration are each defined in terms of the other assemblies. So we gradually bring up each one of those assemblies up by first compiling a stub System, which we use to build System.XML and System.Configuration. Then we rebuild System, this time referencing System.XML and System.Configuration so we can take a dependency on them, and so on. snip Is this a Microsoft circular dependency or a Mono implementation issue? Michael ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Recent xbuild fixes causing issues with finding mcs
On Mon, Feb 17, 2014 at 12:22 PM, Michael Hutchinson m.j.hutchin...@gmail.com wrote: TBH this seems like a runtime bug, it should not rely on itself being in PATH. Should I file a bug against the runtime? What is the best way to describe this issue? ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Recent xbuild fixes causing issues with finding mcs
On Sun, Feb 16, 2014 at 7:34 AM, Andrés G. Aragoneses kno...@gmail.comwrote: On 16/02/14 10:15, Michael Hutchinson wrote: ... which automatically executes exe files using Mono. Are you sure that statement applies to all distros? I read somewhere some time ago that the only distro so far that implemented the ability to run .exe files automatically by calling mono under the hood was Debian (and derivatives), by installing some system hook by default when mono packages are installed. Maybe Michael Franz is not using Debian? Or maybe that hook doesn't work for him because he's using a custom mono install (instead of debian packages)? I am using CentOS 6.5 with a locally built Mono installation. I have read about how you can modify the kernel to understand launching Mono applications - http://www.mono-project.com/Guide:Running_Mono_Applications - this was probably after I ran into this problem. If this has become a requirement to use Mono for development it should probably be documented somewhere. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] NUnit shadow copy and multiple users issue
On Sun, Feb 16, 2014 at 12:34 AM, Michael Franz mvfr...@gmail.com wrote: Hi, I have been setting up my development environment on CentOS 6.5 and have had some great success. My latest issue is temp directories and shadow copies while running nunit. The issue is documented here and fixed in NUnit 3.0 https://bugs.launchpad.net/nunit-3.0/+bug/719187 . Is there any plan to upgrade the Mono version of NUnit? I might be wrong, but I have only been able to get the version of NUnit that is embedded in Mono to work for me. Is there a way that I can upgrade my local copy and have it still work? Or, is the best way to resolve this issue is to create a patch for the shadow copy logic for the Mono version of NUnit? Michael After looking into a fix for this, it seems that the easiest fix is to change the nunit-console-exe.config files (I found 4) and one App.config. I am not sure which ones actually need to be changed as I don't fully understand the build and install process. It actually took a lot of searching to find all of them. # modified: mcs/nunit24/ConsoleRunner/nunit-console-exe/App.config # modified: mcs/nunit24/ConsoleRunner/nunit-console-exe/nunit-console.exe.config # modified: mcs/nunit24/ConsoleRunner/nunit-console-exe/nunit-console.exe.config.net_2_0 # modified: mcs/nunit24/ConsoleRunner/nunit-console-exe/nunit-console.exe.config.net_3_5 # modified: mcs/tools/linker/Tests/Libs/nunit-console.exe.config The patch for all is the same, it creates a user specific temp directory for running unit tests. This works for my setup, as I run multiple users on the same machine. I am sure there are better ways to resolve this issue, this just seem like the easiest. -add key=shadowfiles.path value=%temp%\nunit20\ShadowCopyCache / +add key=shadowfiles.path value=%temp%\nunit20-%USERNAME%\ShadowCopyCache / What is the best way to proceed? I also looked to raise a bug for this in the Mono bug database, but not sure what component the NUnit code is under. Thoughts? Michael ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Recent xbuild fixes causing issues with finding mcs
Hi, I see there have been a few changes to xbuild since February 10th, 2014. February 10th is the last time I was able to build my local C# project using mono head. This is a simple project that I have just started and am planing to build on both mono and .NET. The issue seems to be that xbuild has changed how it finds mcs. /opt/local/JenkinsBuilds/bin/mcs - /opt/local/JenkinsBuilds/lib/mono/4.5/mcs.exe - see below. My locally build mono install is in /opt/local/JenkinsBuilds and my builds are all run via Jenkins. The build process is: - use premake5 to generate Visual Studio 2012 project files (note I am using .net 4.5 specific features) - use xbuild to build - use mono version of nunit to test The working build out put was like this: + /opt/local/JenkinsBuilds/bin/xbuild QTS.sln XBuild Engine Version 12.0 Mono, Version 3.2.7.0 Copyright (C) 2005-2013 Various Mono authors Build started 2/10/2014 9:56:00 PM. __ Project /var/lib/jenkins/jobs/CI/workspace/QTS.sln (default target(s)): Target ValidateSolutionConfiguration: Building solution configuration Debug|Any CPU. Target Build: Project /var/lib/jenkins/jobs/CI/workspace/QTS/QTS.csproj (default target(s)): Target PrepareForBuild: Configuration: Debug Platform: AnyCPU Target GenerateSatelliteAssemblies: No input files were specified for target GenerateSatelliteAssemblies, skipping. Target GenerateTargetFrameworkMonikerAttribute: Skipping target GenerateTargetFrameworkMonikerAttribute because its outputs are up-to-date. Target CoreCompile: Tool */opt/local/JenkinsBuilds/bin/mcs* execution started with arguments: /noconfig /debug:full /debug+ /optimize- /out:obj/Debug/QTS.dll Properties/AssemblyInfo.cs Utilities/Measurements/PerformanceStatistics.cs /target:library /define:DEBUG;TRACE /platform:AnyCPU /reference:/opt/local/JenkinsBuilds/lib/mono/4.5/System.dll /reference:/opt/local/JenkinsBuilds/lib/mono/4.5/System.Core.dll /warn:4 The broken build is now producing: + /opt/local/JenkinsBuilds/bin/xbuild QTS.sln XBuild Engine Version 12.0 Mono, Version 3.2.7.0 Copyright (C) 2005-2013 Various Mono authors Build started 2/15/2014 8:50:52 AM. __ Project /var/lib/jenkins/jobs/CI/workspace/QTS.sln (default target(s)): Target ValidateSolutionConfiguration: Building solution configuration Debug|Any CPU. Target Build: Project /var/lib/jenkins/jobs/CI/workspace/QTS/QTS.csproj (default target(s)): Target PrepareForBuild: Configuration: Debug Platform: AnyCPU Created directory bin/Debug/ Created directory obj/Debug/ Target CopyFilesMarkedCopyLocal: Copying file from '/opt/local/JenkinsBuilds/lib/mono/4.5/mscorlib.dll' to '/var/lib/jenkins/jobs/CI/workspace/QTS/bin/Debug/mscorlib.dll' Copying file from '/opt/local/JenkinsBuilds/lib/mono/4.5/mscorlib.dll.mdb' to '/var/lib/jenkins/jobs/CI/workspace/QTS/bin/Debug/mscorlib.dll.mdb' Target GenerateSatelliteAssemblies: No input files were specified for target GenerateSatelliteAssemblies, skipping. Target CoreCompile: Tool /opt/local/JenkinsBuilds/lib/mono/4.5/mcs.exe execution started with arguments: /noconfig /debug:full /debug+ /optimize- /out:obj/Debug/QTS.dll Properties/AssemblyInfo.cs Utilities/Math.cs Utilities/Measurements/PerformanceStatistics.cs obj/Debug/.NETFramework,Version=v4.5.AssemblyAttribute.cs /target:library /define:DEBUG;TRACE /nostdlib /platform:AnyCPU /reference:/opt/local/JenkinsBuilds/lib/mono/4.5/System.dll /reference:/opt/local/JenkinsBuilds/lib/mono/4.5/System.Core.dll /reference:/opt/local/JenkinsBuilds/lib/mono/4.5/mscorlib.dll /warn:4 /opt/local/JenkinsBuilds/lib/mono/4.5/Microsoft.CSharp.targets: error : Error executing tool '/opt/local/JenkinsBuilds/lib/mono/4.5/mcs.exe': I checked the commit logs, and it looks like there are commits that would affect this behavior. Now, it might be that I was doing something wrong from the start and now I need to fix the process, but it seems like a simple process. e753ca2 Michael Hutchinson [xbuild] Fix dependency in C# targets c197478 Michael Hutchinson [xbuild] Fix 2.0 tests to handle mcs sdk argument 693176c Michael Hutchinson [xbuild] Fix Tooltask.ToolPath behaviour to match .NET df52831 Michael Hutchinson [xbuild] Make ToolLocationHelper work better for 2.0/3.5 a55c588 Michael Hutchinson [xbuild] Fix typo that broke 2.0/3.5 targets
Re: [Mono-dev] Recent xbuild fixes causing issues with finding mcs
On Sat, Feb 15, 2014 at 9:46 AM, Michael Franz mvfr...@gmail.com wrote: Hi, I see there have been a few changes to xbuild since February 10th, 2014. February 10th is the last time I was able to build my local C# project using mono head. This is a simple project that I have just started and am planing to build on both mono and .NET. The issue seems to be that xbuild has changed how it finds mcs. /opt/local/JenkinsBuilds/bin/mcs - /opt/local/JenkinsBuilds/lib/mono/4.5/mcs.exe - see below. My locally build mono install is in /opt/local/JenkinsBuilds and my builds are all run via Jenkins. The build process is: - use premake5 to generate Visual Studio 2012 project files (note I am using .net 4.5 specific features) - use xbuild to build - use mono version of nunit to test The working build out put was like this: + /opt/local/JenkinsBuilds/bin/xbuild QTS.sln XBuild Engine Version 12.0 Mono, Version 3.2.7.0 Copyright (C) 2005-2013 Various Mono authors Build started 2/10/2014 9:56:00 PM. __ Project /var/lib/jenkins/jobs/CI/workspace/QTS.sln (default target(s)): Target ValidateSolutionConfiguration: Building solution configuration Debug|Any CPU. Target Build: Project /var/lib/jenkins/jobs/CI/workspace/QTS/QTS.csproj (default target(s)): Target PrepareForBuild: Configuration: Debug Platform: AnyCPU Target GenerateSatelliteAssemblies: No input files were specified for target GenerateSatelliteAssemblies, skipping. Target GenerateTargetFrameworkMonikerAttribute: Skipping target GenerateTargetFrameworkMonikerAttribute because its outputs are up-to-date. Target CoreCompile: Tool */opt/local/JenkinsBuilds/bin/mcs* execution started with arguments: /noconfig /debug:full /debug+ /optimize- /out:obj/Debug/QTS.dll Properties/AssemblyInfo.cs Utilities/Measurements/PerformanceStatistics.cs /target:library /define:DEBUG;TRACE /platform:AnyCPU /reference:/opt/local/JenkinsBuilds/lib/mono/4.5/System.dll /reference:/opt/local/JenkinsBuilds/lib/mono/4.5/System.Core.dll /warn:4 The broken build is now producing: + /opt/local/JenkinsBuilds/bin/xbuild QTS.sln XBuild Engine Version 12.0 Mono, Version 3.2.7.0 Copyright (C) 2005-2013 Various Mono authors Build started 2/15/2014 8:50:52 AM. __ Project /var/lib/jenkins/jobs/CI/workspace/QTS.sln (default target(s)): Target ValidateSolutionConfiguration: Building solution configuration Debug|Any CPU. Target Build: Project /var/lib/jenkins/jobs/CI/workspace/QTS/QTS.csproj (default target(s)): Target PrepareForBuild: Configuration: Debug Platform: AnyCPU Created directory bin/Debug/ Created directory obj/Debug/ Target CopyFilesMarkedCopyLocal: Copying file from '/opt/local/JenkinsBuilds/lib/mono/4.5/mscorlib.dll' to '/var/lib/jenkins/jobs/CI/workspace/QTS/bin/Debug/mscorlib.dll' Copying file from '/opt/local/JenkinsBuilds/lib/mono/4.5/mscorlib.dll.mdb' to '/var/lib/jenkins/jobs/CI/workspace/QTS/bin/Debug/mscorlib.dll.mdb' Target GenerateSatelliteAssemblies: No input files were specified for target GenerateSatelliteAssemblies, skipping. Target CoreCompile: Tool /opt/local/JenkinsBuilds/lib/mono/4.5/mcs.exe execution started with arguments: /noconfig /debug:full /debug+ /optimize- /out:obj/Debug/QTS.dll Properties/AssemblyInfo.cs Utilities/Math.cs Utilities/Measurements/PerformanceStatistics.cs obj/Debug/.NETFramework,Version=v4.5.AssemblyAttribute.cs /target:library /define:DEBUG;TRACE /nostdlib /platform:AnyCPU /reference:/opt/local/JenkinsBuilds/lib/mono/4.5/System.dll /reference:/opt/local/JenkinsBuilds/lib/mono/4.5/System.Core.dll /reference:/opt/local/JenkinsBuilds/lib/mono/4.5/mscorlib.dll /warn:4 /opt/local/JenkinsBuilds/lib/mono/4.5/Microsoft.CSharp.targets: error : Error executing tool '/opt/local/JenkinsBuilds/lib/mono/4.5/mcs.exe': I checked the commit logs, and it looks like there are commits that would affect this behavior. Now, it might be that I was doing something wrong from the start and now I need to fix the process, but it seems like a simple process. e753ca2 Michael Hutchinson [xbuild] Fix dependency in C# targets c197478 Michael Hutchinson [xbuild] Fix 2.0 tests to handle mcs sdk argument 693176c Michael Hutchinson [xbuild] Fix Tooltask.ToolPath behaviour to match .NET df52831 Michael Hutchinson
Re: [Mono-dev] Recent xbuild fixes causing issues with finding mcs
On Sat, Feb 15, 2014 at 10:02 PM, Michael Hutchinson m.j.hutchin...@gmail.com wrote: AFAIK something's wrong with the installation if $prefix/lib/mono/4.5/mcs.exe is missing. What does your $prefix/bin/mcs point to? It points to a binary that does not run on its own. bash-4.1$ ./lib/mono/4.5/mcs.exe --version bash: ./lib/mono/4.5/mcs.exe: cannot execute binary file but, if I run it with mono it will work. bash-4.1$ bin/mono ./lib/mono/4.5/mcs.exe --version Mono C# compiler version 3.2.7.0 Prior to the change, it was the mcs wrapper that was being executed, after the change, it is trying to run the .NET binary directly. The contents of mcs is: #!/bin/sh exec /opt/local/JenkinsBuilds/bin/mono $MONO_OPTIONS /opt/local/JenkinsBuilds/lib/mono/4.5/mcs.exe $@ On 15 February 2014 10:51, Michael Franz mvfr...@gmail.com wrote: On Sat, Feb 15, 2014 at 9:46 AM, Michael Franz mvfr...@gmail.com wrote: Hi, I see there have been a few changes to xbuild since February 10th, 2014. February 10th is the last time I was able to build my local C# project using mono head. This is a simple project that I have just started and am planing to build on both mono and .NET. The issue seems to be that xbuild has changed how it finds mcs. /opt/local/JenkinsBuilds/bin/mcs - /opt/local/JenkinsBuilds/lib/mono/4.5/mcs.exe - see below. My locally build mono install is in /opt/local/JenkinsBuilds and my builds are all run via Jenkins. The build process is: - use premake5 to generate Visual Studio 2012 project files (note I am using .net 4.5 specific features) - use xbuild to build - use mono version of nunit to test The working build out put was like this: + /opt/local/JenkinsBuilds/bin/xbuild QTS.sln XBuild Engine Version 12.0 Mono, Version 3.2.7.0 Copyright (C) 2005-2013 Various Mono authors Build started 2/10/2014 9:56:00 PM. __ Project /var/lib/jenkins/jobs/CI/workspace/QTS.sln (default target(s)): Target ValidateSolutionConfiguration: Building solution configuration Debug|Any CPU. Target Build: Project /var/lib/jenkins/jobs/CI/workspace/QTS/QTS.csproj (default target(s)): Target PrepareForBuild: Configuration: Debug Platform: AnyCPU Target GenerateSatelliteAssemblies: No input files were specified for target GenerateSatelliteAssemblies, skipping. Target GenerateTargetFrameworkMonikerAttribute: Skipping target GenerateTargetFrameworkMonikerAttribute because its outputs are up-to-date. Target CoreCompile: Tool /opt/local/JenkinsBuilds/bin/mcs execution started with arguments: /noconfig /debug:full /debug+ /optimize- /out:obj/Debug/QTS.dll Properties/AssemblyInfo.cs Utilities/Measurements/PerformanceStatistics.cs /target:library /define:DEBUG;TRACE /platform:AnyCPU /reference:/opt/local/JenkinsBuilds/lib/mono/4.5/System.dll /reference:/opt/local/JenkinsBuilds/lib/mono/4.5/System.Core.dll /warn:4 The broken build is now producing: + /opt/local/JenkinsBuilds/bin/xbuild QTS.sln XBuild Engine Version 12.0 Mono, Version 3.2.7.0 Copyright (C) 2005-2013 Various Mono authors Build started 2/15/2014 8:50:52 AM. __ Project /var/lib/jenkins/jobs/CI/workspace/QTS.sln (default target(s)): Target ValidateSolutionConfiguration: Building solution configuration Debug|Any CPU. Target Build: Project /var/lib/jenkins/jobs/CI/workspace/QTS/QTS.csproj (default target(s)): Target PrepareForBuild: Configuration: Debug Platform: AnyCPU Created directory bin/Debug/ Created directory obj/Debug/ Target CopyFilesMarkedCopyLocal: Copying file from '/opt/local/JenkinsBuilds/lib/mono/4.5/mscorlib.dll' to '/var/lib/jenkins/jobs/CI/workspace/QTS/bin/Debug/mscorlib.dll' Copying file from '/opt/local/JenkinsBuilds/lib/mono/4.5/mscorlib.dll.mdb' to '/var/lib/jenkins/jobs/CI/workspace/QTS/bin/Debug/mscorlib.dll.mdb' Target GenerateSatelliteAssemblies: No input files were specified for target GenerateSatelliteAssemblies, skipping. Target CoreCompile: Tool /opt/local/JenkinsBuilds/lib/mono/4.5/mcs.exe execution started with arguments: /noconfig /debug:full /debug+ /optimize- /out:obj/Debug/QTS.dll Properties/AssemblyInfo.cs Utilities/Math.cs Utilities/Measurements/PerformanceStatistics.cs obj/Debug/.NETFramework,Version=v4.5.AssemblyAttribute.cs
[Mono-dev] NUnit shadow copy and multiple users issue
Hi, I have been setting up my development environment on CentOS 6.5 and have had some great success. My latest issue is temp directories and shadow copies while running nunit. The issue is documented here and fixed in NUnit 3.0 https://bugs.launchpad.net/nunit-3.0/+bug/719187 . Is there any plan to upgrade the Mono version of NUnit? I might be wrong, but I have only been able to get the version of NUnit that is embedded in Mono to work for me. Is there a way that I can upgrade my local copy and have it still work? Or, is the best way to resolve this issue is to create a patch for the shadow copy logic for the Mono version of NUnit? Michael ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Cross Compiling to Windows
Hi, I have been trying to cross compile mono on centos 6.5 for windows using the instructions here http://www.mono-project.com/Cross-compiling_Mono_for_Windows . These instructions do not look like they have been updated in a while. Does this process for using MinGW to cross compile Mono for Windows still work? After installing a bunch of the mingw packages and running: ./build-mingw32.sh -m i686-pc-mingw32 I am getting compilation errors on atomic.h missing references. Would I be running into the same issues as the native compilation issues? (compiling on windows using cygwin/mingw) Thoughts? Michael ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Can't build the master branch from git
My daily builds started to fail a few days ago, but seem to be back up and
working now. I build with a similar command on Centos 6.5 .
./autogen.sh --prefix=/opt/local/JenkinsBuilds
make get-monolite-latest
make EXTERNAL_MCS=${PWD}/mcs/class/lib/monolite/gmcs.exe
On Fri, Feb 7, 2014 at 1:42 PM, Brandon Perry bperry.volat...@gmail.comwrote:
I recently documented compiling the 3.2.6 on CentOS.
Not sure if your issue is ubuntu related, but perhaps this will help:
http://volatile-minds.blogspot.com/2014/01/mono-326-on-centos-65.html
On Fri, Feb 7, 2014 at 12:02 PM, initram martin.midtga...@gmail.comwrote:
I am unable to build the souce code I have pulled form git. I have tried
both
using both the repository version of mono and monolite to compile and I
fail
in the same way.
The last lines of my failed build can be seen below (using monolite):
Making all in runtime
make[2]: Entering directory `/home/initram/monoSource/monoInitram/runtime'
if test -w /home/initram/monoSource/monoInitram/mcs; then :; else chmod -R
+w /home/initram/monoSource/monoInitram/mcs; fi
cd /home/initram/monoSource/monoInitram/mcs make --no-print-directory
-s
NO_DIR_CHECK=1 PROFILES='net_2_0 net_3_5 net_4_0 net_4_5 xbuild_12 '
CC='gcc' all-profiles
Bootstrap compiler: Mono C# compiler version 3.2.7.0
MCS [net_2_0] mscorlib.dll
Stacktrace:
Native stacktrace:
Segmentation fault (core dumped)
make[8]: *** [../../class/lib/net_2_0/tmp/mscorlib.dll] Error 139
make[7]: *** [do-all] Error 2
make[6]: *** [all-recursive] Error 1
make[5]: *** [all-recursive] Error 1
make[4]: *** [profile-do--net_2_0--all] Error 2
make[3]: *** [profiles-do--all] Error 2
make[2]: *** [all-local] Error 2
make[2]: Leaving directory `/home/initram/monoSource/monoInitram/runtime'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/initram/monoSource/monoInitram'
make: *** [all] Error 2
I am running Lubuntu in a virtual machine.
my process of building is the following:
$ cd ~/monoSource/monoInitram
$ ./autogen.sh --prefix=/opt/monoInitram
$ make EXTERNAL_MCS=${PWD}/mcs/class/lib/monolite/basic.exe
Where do I go from here?
I would really like to know that my changes compile and pass all test
using
head of master.
--
View this message in context:
http://mono.1490590.n4.nabble.com/Can-t-build-the-master-branch-from-git-tp4661864.html
Sent from the Mono - Dev mailing list archive at Nabble.com.
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
--
http://volatile-minds.blogspot.com -- blog
http://www.volatileminds.net -- website
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Afallon: open source WPF implementation
Jonathan, On Thu, Jun 13, 2013 at 4:31 PM, Jonathan Lima greenbo...@gmail.com wrote: Would I have licensing problems using Micro Framework code? I want to use any opensource license that I could use it on commercial projects(MIT probably). @Stephen I'm organizing the code as it is splitted across some projects, soon I'll put it into a git repo. Have you made enough progress on this to post the repo URL? Michael ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Mono 3.2.1 OS X Build on Mountain Lion with threads failure [libmonoruntime_la-threads.lo] Error 1
Rodrigo, I see the page is updated, I cannot tell the difference between the 32 bit build and the 64 bit build instructions. I don't think the 64 bit instructions needed to be changed. If the --build is specified for the 64 bit, it should be x86_64-apple-darwin11.2.0 . Michael On Thu, Aug 8, 2013 at 11:50 AM, Rodrigo Kumpera kump...@gmail.com wrote: The build instructions have been updated. On Wed, Aug 7, 2013 at 9:37 PM, Michael Franz mvfr...@gmail.com wrote: Zoltan, Your suggestion worked! Thank you! How do we get the OS X build instructions updated? This is the page I was working from. http://mono-project.com/Compiling_Mono_on_OSX Michael On Wed, Aug 7, 2013 at 3:54 AM, Zoltan Varga var...@gmail.com wrote: Hi, Instead of CFLAGS=-m32, try configure --build=i386-apple-darwin11.2.0 or something. Zoltan On Wed, Aug 7, 2013 at 4:13 AM, Michael Franz mvfr...@gmail.com wrote: Hi, I download the latest tar file (mono-3.2.1.tar.bz2http://download.mono-project.com/sources/mono/mono-3.2.1.tar.bz2) and followed the OS X build instructions. The 32 bit build is failing, similar to this old thread http://mono.1490590.n4.nabble.com/mono-io-layer-mono-mutex-h-Errors-in-Current-Master-td3515845.html#a3515916. The 64 bit build works just fine. How do I get more details of the exact error? $ CC='cc -m32' ./configure --prefix=DIR --enable-nls=no $ make Making all in metadata CC libmonoruntime_la-threads.lo make[3]: *** [libmonoruntime_la-threads.lo] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 I have tried 'make V=1', but that just seems to give me the information about the command used to build and not the details on the problem. My system detail ares: mono-3.2.1$ uname -a Darwin MacMini.local 12.4.0 Darwin Kernel Version 12.4.0: Wed May 1 17:57:12 PDT 2013; root:xnu-2050.24.15~1/RELEASE_X86_64 x86_64 mono-3.2.1$ gcc --version i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.11.00) Any help is appreciated. Michael ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Mono 3.2.1 OS X Build on Mountain Lion with threads failure [libmonoruntime_la-threads.lo] Error 1
Zoltan, Your suggestion worked! Thank you! How do we get the OS X build instructions updated? This is the page I was working from. http://mono-project.com/Compiling_Mono_on_OSX Michael On Wed, Aug 7, 2013 at 3:54 AM, Zoltan Varga var...@gmail.com wrote: Hi, Instead of CFLAGS=-m32, try configure --build=i386-apple-darwin11.2.0 or something. Zoltan On Wed, Aug 7, 2013 at 4:13 AM, Michael Franz mvfr...@gmail.com wrote: Hi, I download the latest tar file (mono-3.2.1.tar.bz2http://download.mono-project.com/sources/mono/mono-3.2.1.tar.bz2) and followed the OS X build instructions. The 32 bit build is failing, similar to this old thread http://mono.1490590.n4.nabble.com/mono-io-layer-mono-mutex-h-Errors-in-Current-Master-td3515845.html#a3515916. The 64 bit build works just fine. How do I get more details of the exact error? $ CC='cc -m32' ./configure --prefix=DIR --enable-nls=no $ make Making all in metadata CC libmonoruntime_la-threads.lo make[3]: *** [libmonoruntime_la-threads.lo] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 I have tried 'make V=1', but that just seems to give me the information about the command used to build and not the details on the problem. My system detail ares: mono-3.2.1$ uname -a Darwin MacMini.local 12.4.0 Darwin Kernel Version 12.4.0: Wed May 1 17:57:12 PDT 2013; root:xnu-2050.24.15~1/RELEASE_X86_64 x86_64 mono-3.2.1$ gcc --version i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.11.00) Any help is appreciated. Michael ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Mono 3.2.1 OS X Build on Mountain Lion with threads failure [libmonoruntime_la-threads.lo] Error 1
Hi, I download the latest tar file (mono-3.2.1.tar.bz2http://download.mono-project.com/sources/mono/mono-3.2.1.tar.bz2) and followed the OS X build instructions. The 32 bit build is failing, similar to this old thread http://mono.1490590.n4.nabble.com/mono-io-layer-mono-mutex-h-Errors-in-Current-Master-td3515845.html#a3515916. The 64 bit build works just fine. How do I get more details of the exact error? $ CC='cc -m32' ./configure --prefix=DIR --enable-nls=no $ make Making all in metadata CC libmonoruntime_la-threads.lo make[3]: *** [libmonoruntime_la-threads.lo] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 I have tried 'make V=1', but that just seems to give me the information about the command used to build and not the details on the problem. My system detail ares: mono-3.2.1$ uname -a Darwin MacMini.local 12.4.0 Darwin Kernel Version 12.4.0: Wed May 1 17:57:12 PDT 2013; root:xnu-2050.24.15~1/RELEASE_X86_64 x86_64 mono-3.2.1$ gcc --version i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.11.00) Any help is appreciated. Michael ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-list] Microsoft.Build.Engine Tests Failing
Hi, Update to from svn (I also did clean checkouts) for mono/mcs/libgdiplus. The build works fine, however when I try to run the tests in mcs/class/Microsoft.Build.Engine using make run-test-local make run-test-local PROFILE=net_2_0 I get the following error: Runtime Environment - OS Version: OSX 9.5.0.0 CLR Version: 2.0.50727.1433 ( Mono 2.3 ) Unhandled Exception: System.ArgumentOutOfRangeException: Index is less than 0 or more than or equal to the list count. Parameter name: index 0 at System.Collections.ArrayList.ThrowNewArgumentOutOfRangeException (System.String name, System.Object actual, System.String message) [0x0] in /Users/mfranz/developer/mono-no-macports/mcs/class/corlib/System.Collections/ArrayList.cs:3258 at System.Collections.ArrayList.get_Item (Int32 index) [0x00013] in /Users/mfranz/developer/mono-no-macports/mcs/class/corlib/System.Collections/ArrayList.cs:2649 at System.Diagnostics.ProcessModuleCollection.get_Item (Int32 index) [0x0] in /Users/mfranz/developer/mono-no-macports/mcs/class/System/System.Diagnostics/ProcessModuleCollection.cs:63 at System.Diagnostics.Process.get_MainModule () [0x0] in /Users/mfranz/developer/mono-no-macports/mcs/class/System/System.Diagnostics/Process.cs:232 at (wrapper remoting-invoke-with-check) System.Diagnostics.Process:get_MainModule () at NUnit.Util.DomainManager.CreateDomain (NUnit.Core.TestPackage package) [0x0019f] in /Users/mfranz/developer/mono-no-macports/mcs/nunit24/ClientUtilities/util/Services/DomainManager.cs:105 at NUnit.Util.TestDomain.Load (NUnit.Core.TestPackage package) [0x00011] in /Users/mfranz/developer/mono-no-macports/mcs/nunit24/ClientUtilities/util/TestDomain.cs:52 make: *** [run-test-lib] Error 1 Since this is starting with NUnit, I assume this has todo with the upgrade of the NUnit version. Michael ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] NUnit Version - Upgrade soon?
OK, I thought I read somewhere that there were patches to NUnit that were mono specific. Is it ok to submit patches to mono that depend on the latest version of NUnit? Michael On Tue, Nov 18, 2008 at 3:25 PM, Miguel de Icaza [EMAIL PROTECTED] wrote: Hello, What changes to NUnit were specific to Mono? Is there a list of these features? You are confused; There are no changes, you should just not depend on Mono's built-in and private copy of NUnit to write your NUnit test cases. You should get the latest NUnit. On Sun, Nov 16, 2008 at 10:54 PM, Miguel de Icaza [EMAIL PROTECTED] wrote: Hello, I use NUnit for work and have been using the latest version for months. I wrote some test for Mono and found out that the version that Mono is using does not support some of the asserts I am using (IsEmpty). Is there any plan to upgrade the version of NUnit that is used with the Mono build/test? The NUnit that ships with Mono should be considered Mono's own copy of NUnit and not a public version of it. We should probably make packages of the latest version of NUnit, encourage the NUnit developer to maintain those and encourage developers to use the public NUnit as opposed to the private copy that Mono ships. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] NUnit Version - Upgrade soon?
What changes to NUnit were specific to Mono? Is there a list of these features? On Sun, Nov 16, 2008 at 10:54 PM, Miguel de Icaza [EMAIL PROTECTED] wrote: Hello, I use NUnit for work and have been using the latest version for months. I wrote some test for Mono and found out that the version that Mono is using does not support some of the asserts I am using (IsEmpty). Is there any plan to upgrade the version of NUnit that is used with the Mono build/test? The NUnit that ships with Mono should be considered Mono's own copy of NUnit and not a public version of it. We should probably make packages of the latest version of NUnit, encourage the NUnit developer to maintain those and encourage developers to use the public NUnit as opposed to the private copy that Mono ships. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] NUnit Version - Upgrade soon?
Hi, I use NUnit for work and have been using the latest version for months. I wrote some test for Mono and found out that the version that Mono is using does not support some of the asserts I am using (IsEmpty). Is there any plan to upgrade the version of NUnit that is used with the Mono build/test? Thanks Michael ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] NUnit Tests for ToolLocationHelper
Hi, Here are two tests for ToolLocationHelper. I would have written tests for the entire class but I have not been able to figure out what the results should be. I have also attached the patches to that will allow ToolLocationHelper to pass the tests and adding the class to the build tests. Let me know if I did not create these correctly. Thanks Michael ToolLocationHelperTest.cs Description: Binary data ToolLocationHelper.patch Description: Binary data sources.patch Description: Binary data ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-dev] ToolLocationHelper - NUnit Tests
Hi, I have put together some NUnit tests for ToolLocationHelper and have a few questions that need to be clarified. 1. When mono is installed, is there a differentiation between the runtime and the SDK? Some methods return different results depending on which runtimes and SDKs are actually installed. Example are GetPathToDotNetFrameworkFile depends on which runtimes are installed and GetPathToDotNetFrameworkSdkFile depends on which SDK is installed. 2. Is Mono expected to return the same values for all methods regardless of the platform it is running on? An example is GetDotNetFrameworkRootRegistryKey, on windows it returns 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework'. Would Microsoft be replaced with Novell? Should the correct value be HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Mono? I created the test based on running the unimplemented method on windows and determining what the output should be. I also consulted the MSDN documentation to get a better idea of what to expect. In most cases running the tests provided more information. Thanks Michael ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
