[Mono-devel-list] Building System.Security.dll

Sébastien Pouliot spouliot at videotron.ca
Sun Jul 27 23:15:14 EDT 2003

Hello Peter,

I'm now back to the point where I can run the unit tests under Windows (I
had some problems with nunit-console). I noticed that there were a very HIGH
number of errors when testing System.Security assembly.

Tests run: 111, Failures: 38, Not run: 6, Time: 4,375 seconds

Most of the errors are like...

1) MonoTests.System.Security.Cryptography.Xml.DSAKeyValueTest.GenerateKey :
d not load type System.Object from assembly corlib, Version=,
tral, PublicKeyToken=null because the parent does not exist.

... and are related to using corlib.dll...
LIB_MCS_FLAGS = /r:$(corlib) /r:System.dll /r:System.Xml.dll

... simultaneously with mscorlib. After changing the Makefile to...
LIB_MCS_FLAGS = /r:mscorlib.dll /r:System.dll /r:System.Xml.dll

... the number of errors falls to almost none :-)
Tests run: 111, Failures: 3, Not run: 6, Time: 10,40625 seconds

I suspect this is because the System.Security assembly tries to create
objects that exists in in both mscorlib and corlib (when running on
Microsoft's CLR).

We already faced the problem before and I had to make a special version of
System.Security assembly (System.Security_cmp.dll) so that corcompare could
work to generate the class status page.

So my guess is that we need to
a.	Change the makefile to use mscorlib and Win32 and corlib on Linux
b.	Make a special System.Security_cmp.dll (or something similar to
corlib_platform.dll) which use corlib (for the class status page)


Sebastien Pouliot
Security Architect, Motus Technologies, http://www.motus.com/
work: spouliot at motus.com
home: spouliot at videotron.ca

More information about the Mono-devel-list mailing list