[Mono-devel-list] csc build and SecurityPermissionAttribute problem on cygwin

Atsushi Eno atsushi at ximian.com
Fri Feb 20 00:39:16 EST 2004


Is there any problem around using mcs to build mcs on cygwin, like
we have been doing on Linux? Currently the cygwin build uses csc by
default, but it introduces a problem that we can never use
SecurityPermissionAttribute. So I would suggest that we had better
use mcs instead of csc.


As you might know, currently we use csc to build mcs. It is easier
way to build mcs on Windows and MS.NET than using mcs. However, csc
is not suitable to build complete mscorlib.dll. When we try to build
it, csc complains:

error CS1577: Assembly generation failed -- Security custom attributes
can not be referenced from defining assembly.

So currently we exclude SecurityPermissionAttribute from mscorlib.dll.
(written in mcs/class/corlib/corlib.dll.win32-excludes)

However, when we use our mono runtime and that mscorlib.dll, we cannot
reference to this attribute. The runtime complains that there is no such
attribute. They are used in several applications such as NAnt.


(BTW we usually don't see such problem ... it is because usually we are
running our IL executables on the MS runtime. For example, when you
call "mcs" from bash, it actually invokes "mcs.exe", not "mcs" shell
script... It causes some kind of problem. For example, we have
different probe way than the MS runtime. MS.NET never use MONO_PATH
but uses their GAC et al.)

Atsushi Eno

More information about the Mono-devel-list mailing list