[Mono-list] "mscorlib.dll is an invalid CIL image"

[Chris Plasun]

Hi Jonathan,

Thanks for your reply...

> This came up on #mono a few weeks ago, I believe.  I forget the
> platform, but I remember the problem: as part of the embedded build
> process, there was a post-processing step over the assemblies that was
> rendering them invalid (because the post-processing step was presumably
> for ELF shared libraries, so it completely screwed up the assemblies).
> 
> So do three things:
> 
> 1. Try to run monodis against your created mscorlib.dll.
> 
> 2. Copy your created mscorlib.dll to a different machine, and run
> monodis on the other machine.
> 
> 3. For good measure, copy the installation directory from a working
> machine onto your MPC8313 machine, and try running your app again.
> 
> It should be noted that *.dll/*.exe files don't need to be built on the
> host machine; they're platform independent, and thus can be copied
> directly from any machine with a known working build.

So the Mono build **does** create a MSCORLIB.DLL?

I understand that the  *.dll/*.exe files are platform independent, but are 
they **architecture** independent? I'm using PowerPC.

It looks like some of the paths are messed up as I can't run monodis
on the board. I'll have to fix that first.

Monodis on SUSE doesn't report any mscorlib.dll corruption...

I think I need to learn how to cross-build Mono myself, no?

The build I have for this board doesn't have mscorlib.dll so I'm using 
the SUSE one; that's not doable?

Thanks,
Chris Plasun