[Mono-devel-list] Problem: CSC fails to compile corlib (bug?) or is it an MCS bug ?

[Jacek Blaszczynski]

Hello!

Thanks for info but neither latest cvs checkout (today 10:00) nor setting
__SECURITY_BOOTSTRAP_DB helps in building corlib with csc

my command line is as follows:

...\Mono\mcs\class\corlib>set __SECURITY_BOOTSTRAP_DB=IS_SET_BY_JB

...\Mono\mcs\class\corlib>csc /out:mscorlib.dll /target:library
/recurse:*.cs /d:INSIDE_CORLIB /d:NET_1_1 /debug+ /unsafe+
/nowarn:0649;0169;0067 /nologo /nostdlib+

System\Guid.cs(449,18): warning CS0675: Bitwise-or operator used on a
sign-extended operand; consider casting to a smaller unsigned type first
error CS1577: Assembly generation failed -- Nieokreślony błąd (eng.
translation: Undefined error).

My configuration is as follows: WinXP Pro SP1 PL fully patched, NET SDK v
1.1

The only change after setting __SECURITY_BOOTSTRAP_DB is that error CS1577
is not extended with additional info on security attributes.

Any ideas?

Jacek

-----Original Message-----
From: mono-devel-list-admin at lists.ximian.com
[mailto:mono-devel-list-admin at lists.ximian.com] On Behalf Of Atsushi Eno
Sent: Tuesday, August 10, 2004 9:20 AM
To: mono-devel-list at lists.ximian.com
Subject: Re: [Mono-devel-list] Problem: CSC fails to compile corlib (bug?)
or is it an MCS bug ?

Hello,

Actually the fixage that Marcus suggested was already applied to cvs. At
least I had been having no trouble on building corlib with csc.

Or is Jacek using other version of csc than MS.NET 1.1?

Atsushi Eno

Marcus wrote:
> mscorlib.dll is a special case. csc complains when you define and use 
> a security attribute in the same assembly. Try setting the 
> environmental variable __SECURITY_BOOTSTRAP_DB (to anything) and building.
> 
> 
> On Monday 09 August 2004 3:45 am, Jacek Blaszczynski wrote:
> 
>>csc is unable to compile corlib under windows throwing the following
error:
>>
>>Assembly generation failed -- Common Language Runtime Internal error:
>>0x80131443 later complining about using security attributes defind in 
>>the same assembly.
>>
>>Obviously mcs compiles without any problems.
>>
>>No problems with csc compiling other assemblies I have tested so far.
>>
>>Q1: is the use of security attributes within corlib violating in any 
>>way ECMA C# specs?
>>Q2: who is right prohibiting use of security attributes in defining 
>>assembly?
>>Q3: is it possible to compile corlib with csc - any workarounds ?
>>
>>Cheers
>>
>>Jacek
> 
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
> 

_______________________________________________
Mono-devel-list mailing list
Mono-devel-list at lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list