Use a more recent version of Mono

[GoogleCodeExporter]

The currently available version of Mono is ancient history, please upgrade it 
to properly support C#.

http://mono-project.com/DistroPackages/Ubuntu

Original issue reported on code.google.com by erma...@gmail.com on 10 Sep 2010 at 6:39

[GoogleCodeExporter]

Any progress on it?

Original comment by haz...@gmail.com on 13 Sep 2010 at 10:20

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Hazzik suggests here

http://ai-contest.com/forums/viewtopic.php?f=18&t=513&p=2865&hilit=linq#p2871

that you may also need to modify compile_anything.py to reference System.Core

-r:System.Core

Original comment by smremde on 13 Sep 2010 at 3:37

[GoogleCodeExporter]

Here are the instructions to enable updating to the newer Mono 2.4 branch from 
badgerports (http://badgerports.org/hardy.html)

Here's how to add the proper repository:
wget http://badgerports.org/directhex.ppa.asc -O - | sudo apt-key add -
sudo echo 'deb http://badgerports.org/ hardy main ' >> /etc/apt/sources.list

After that, it's just a matter of installing it from the repository:
sudo apt-get update
sudo apt-get install cli-common mono mono-basic mono-tools

Original comment by TheZeusJ...@gmail.com on 23 Sep 2010 at 1:00

[GoogleCodeExporter]

My C# code is not compiling, please upgrade! thanks! :D

Original comment by jimrog...@gmail.com on 25 Sep 2010 at 9:15

[GoogleCodeExporter]

 In schedule cycle old mono have memory leaking. It leads to:
==============
semget error: No space left on device.  Try deleting some semaphores with ipcs 
and ipcrm
or increase the maximum number of semaphore in the system.
==============
compilation error. If you are declaring C# support - support it well.

Original comment by gribko...@gmail.com on 30 Sep 2010 at 10:58

[GoogleCodeExporter]

I get a compiler crash when I use something like:
#if !ASDF
  // some code
#endif

which is perfectly valid C#.

Original comment by ben...@gmail.com on 30 Sep 2010 at 11:20

[GoogleCodeExporter]

Are the admins even monitoring this? It's the most starred issue and not even a 
comment or acknowledgement. Maybe someone should email the owner 
cameron.jp@gmail.com

Original comment by smremde on 30 Sep 2010 at 11:35

[GoogleCodeExporter]

Yeah this is crazy. The version of mono they have supports C# 2.0, which has no 
extension methods, no lambdas and no linq. These are all very common features 
these days.

Original comment by mattur...@gmail.com on 30 Sep 2010 at 12:29

[GoogleCodeExporter]

matturner:  not sure even about 2.0 spec - if i had infer type (var) or 
auto-properties ({get;set;}), helper-methods (this-arguments) in my code it 
failed due compilation error. Annoying!!! And lambdas... Ah, that 
lambdassss.... =) 

Original comment by gribko...@gmail.com on 30 Sep 2010 at 12:36

[GoogleCodeExporter]

Auto type inference was introduced in C# 3.0, as were auto-properties. 
This-argument helper methods are the extension methods I was talking about - 
also C# 3.0. As are anonymous types (var foo = new { bar = "baz", num = 42 };). 
If anyone wants co/conta-variant generic collections that's C# 4.0, but they're 
probably not used much.

Mono 2.0 (Oct '08) supports C# 3.0.

Original comment by mattur...@gmail.com on 30 Sep 2010 at 12:55

[GoogleCodeExporter]

My mistake. 3.0 is based on 2.0 runtime -  because of that fact i sometimes 
forget to make distinction between them. One can find all the features 
introduces in C#3 here: 
http://msdn.microsoft.com/en-US/library/ms364047(v=VS.80).aspx#cs3spec_topic6

And again (not to offtop): UPDATE MONO!

Original comment by gribko...@gmail.com on 30 Sep 2010 at 1:46

[GoogleCodeExporter]

up! date mono :)

Original comment by qui...@gmail.com on 1 Oct 2010 at 2:44

[GoogleCodeExporter]

Pleeeeaaaaaseeeeee!!!

Original comment by odnei.tr...@gmail.com on 5 Oct 2010 at 3:52

[GoogleCodeExporter]

No update yet? :(

Original comment by sala...@gmail.com on 14 Oct 2010 at 5:01

[GoogleCodeExporter]

Any update?

Original comment by apovl...@gmail.com on 15 Oct 2010 at 5:57

[GoogleCodeExporter]

This is the most watched issue (42 people are following it) and not a single 
response from organizers?! That's depressing.

Original comment by skal...@gmail.com on 15 Oct 2010 at 6:10

[GoogleCodeExporter]

Issue created 10. September :(

Original comment by apovl...@gmail.com on 15 Oct 2010 at 6:28

[GoogleCodeExporter]

I wrote a bot and would live to participate, but I can't since this version of 
mono is so outdated.

Original comment by jae...@gmail.com on 15 Oct 2010 at 7:00

[GoogleCodeExporter]

oh my god quit whining about 3.0 

just MAKE UPLOADING WORK this is ridiculous!!!

Original comment by themend...@gmail.com on 16 Oct 2010 at 6:06

[GoogleCodeExporter]

TheMendios, both problems will be solved with the same fix. Please do not work 
against the proper solution.  Also this is the issue for upgrading, if you only 
care about the uploading, then feel free to post in issue 185 (which 
coincidentally will be fixed when this was is fixed)

Original comment by nathanh...@gmail.com on 16 Oct 2010 at 9:12

[GoogleCodeExporter]

attempting to install as described in comment resulted in this error:
# apt-get install cli-common mono mono-basic mono-tools
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package mono is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package mono has no installation candidate

I'll probably try and look into this some later this evening but if someone 
knows the correct packages or what might have happened there it could speed it 
up.

Original comment by janzert on 25 Oct 2010 at 9:17

[GoogleCodeExporter]

enabling badgerports and then installing the currently used mono packages it 
has this error:

# apt-get install mono-common mono-gac mono-gmcs mono-jit mono-mcs mono-runtime 
mono-utils
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  mono-runtime: Conflicts: mono-common (< 2.4) but 1.2.6+dfsg-6ubuntu3.1 is to be installed
                Conflicts: mono-jit (< 2.4) but 1.2.6+dfsg-6ubuntu3.1 is to be installed
E: Broken packages

which I'm pretty sure is because badgerports doesn't include mono-runtime so it 
is going back to the main repository for it and then conflicting with the 
badgerports packages.

Original comment by janzert on 25 Oct 2010 at 10:26

[GoogleCodeExporter]

Ok, I finally got this working. I think the part that fixed it was I had to 
purge the old packages to get rid of the old configuration files. Also the 
final package I ended up using is mono-2.0-devel it seems to be enough for at 
least the starter package to work. If there are any other libraries that need 
to be added let me know

Original comment by janzert on 25 Oct 2010 at 11:52

[GoogleCodeExporter]

I've trying to upload c# 3.0 bot, but got this error:

Unfortunately, your latest submission to the Google AI Challenge did not 
compile successfully. Check out the error messages below for more information 
as to why this might be. Fix as many of the errors as you can, and then submit 
your code again.

COMPILER OUTPUT

Found entry.zip. Attempting to unpack.
unzip -u entry.zip > /dev/null 2> /dev/null
Found MyBot.cs. Compiling this entry as C#
gmcs -warn:0 -out:MyBot.exe Fleet.cs MyBot.cs Planet.cs PlanetWars.cs

COMPILER ERRORS

** ERROR **: shm_semaphores_init: semget error: No space left on device.  Try 
deleting some semaphores with ipcs and ipcrm
or increase the maximum number of semaphore in the system.
aborting...

** (process:26773): WARNING (recursed) **: Thread (nil) may have been 
prematurely finalized
Stacktrace:

** (process:26773): WARNING (recursed) **: Thread (nil) may have been 
prematurely finalized

** (process:26773): WARNING (recursed) **: Thread (nil) may have been 
prematurely finalized

** (process:26773): WARNING (recursed) **: Thread (nil) may have been 
prematurely finalized
Compilation failed.

Sincerely,
The Compile Script

Original comment by haz...@gmail.com on 26 Oct 2010 at 3:26

[GoogleCodeExporter]

thanks it seems works

Original comment by haz...@gmail.com on 27 Oct 2010 at 4:19

[GoogleCodeExporter]

Thanks very very much! This now works with all my code.

Original comment by mattur...@gmail.com on 27 Oct 2010 at 8:45

[GoogleCodeExporter]

Servers are now running latest badgerports backport

Original comment by janzert on 29 Oct 2010 at 5:20

• Changed state: Fixed