[Mono-devel-list] mono Cygwin build fail on CSC error CS1904

Kornél Pál kornelpal at hotmail.com
Sun Jul 24 13:16:21 EDT 2005


Look at:

As I stated in buzilla I was never able to compile Mono using MC csc.exe.

And I allways have to use make EXTERNAL_MCS=/usr/local/bin/mcs
EXTERNAL_RUNTIME=/usr/local/bin/mono instead of simply make on Win32.

I think Mono should either default to mcs on Win32 as well or should support
csc.exe and MS runtime for building.


----- Original Message -----
From: Atsushi Eno
To: Rafael Mizrahi
Sent: Sunday, July 24, 2005 7:03 PM
Subject: Re: [Mono-devel-list] mono Cygwin build fail on CSC error CS1904

> Hello,
> Rafael Mizrahi wrote:
>> Hi Ben,
>> After updating mono and mcs, I fail to build mono on Cygwin.
>> I have checked with other "mono on Cygwin" users and I am not the only
>> one who experiences this problem.
>> Do we need mcs bootstrap?
>> Here is the log:
>> make[7]: Entering directory `/monobuild/mcs/class/corlib'
>> ../../build/library.make:306: no file name for `-include'
>> make all-local
>> make[8]: Entering directory `/monobuild/mcs/class/corlib'
>> ../../build/library.make:306: no file name for `-include'
>> csc.exe /nowarn:649 /nowarn:169 /nowarn:414 -nowarn:612 -nowarn:618
>> -d:INSIDE_CORLIB /nologo /optimize -d:NET_1_1 -d:ONLY_1_1 /debug+
>> /debug:full /noconfig /unsafe /nostdlib /target:library
>> /out:mscorlib.dll
>> @../../build/deps/net_1_1_bootstrap_corlib.dll.response
>> error CS1904: '414' is not a valid warning number
> Maybe we could 1)remove /norwarn:414 and 2)make a change on
> class.cs to not warn 414 when /langversion indicates ISO-1.
> Until this problem got fixed (and funky internal error caused by
> csc bug went away), yes you will need mcs bootstrap.
> Atsushi Eno

More information about the Mono-devel-list mailing list