[IronPython] IronPython 1.0 Beta 1 / Mono 1.1.12 Compilation

Jeff Griffiths jeffg at ActiveState.com
Thu Jan 5 20:37:55 CET 2006

I looked into getting IronPython working on Linux with Mono 1.1.12 this 
morning. In my defense, I just hadn't seen anything about whether this 
would work either way, so these problems are likely known issues?

Some problems:

1. makefile: I changed this:


then got this:

makefile:16: *** missing separator (did you mean TAB instead of 8 
spaces?).  Stop.

I changed the 8 spaces to a tab in vim, then got a little farther:

jeffg at apple Src> make
gmcs -t:library -r:bin/IronMath.dll -out:bin/IronPython.dll 
IronPython/Compiler/NewTypeMaker.cs(1011,17): error CS0019: Operator 
`==' cannot be applied to operands of type `System.RuntimeMethodHandle' 
and `System.RuntimeMethodHandle'
IronPython/Hosting/PythonEngine.cs(76,20): warning CS0219: The variable 
`o' is assigned but its value is never used
Compilation failed: 1 error(s), 1 warnings
make: *** [bin/IronPython.dll] Error 1

Is this a mono version incompatibility with 1.0 Beta 1? ( just guessing )

Background: we're looking at IronPython to see what kind of effort is 
involved in debugging it with Komodo. Using the MS .Net Runtime, 
currently the issues are:

- IronPython has no '-u' option. We can hack around this as we did for 
Jython in the past.

- IronPython does not have an 'os' module, which the PyDBGP client 
currently depends on. Current os module usage includes: os.environ, 
os.path.*, os.popen, os.getcwd. We have clever ideas about working 
around this in a fepy-specific code path.

- IronPython does not have the logging module. We could fairly easily 
cobble up a stub one that was good enough... or look at porting enough 
of the logging module.

cheers, JeffG

More information about the Ironpython-users mailing list