From: Thierry L. <thi...@in...> - 2010-03-03 11:19:55
|
Hi Gabriele, Thanks for your answer. For gcc4cli compilation, I've just realised that the build did not use the version of mono I wanted. It used an old 1.9.1 instead of the 2.6.1... Rebuild is on the way now... Thierry Lafage. Gabriele Svelto a écrit : > Hi Thierry, > > 2010/3/3 Thierry Lafage <thi...@in...>: > >> Hi all, >> >> [snip] >> >> So I have 2 questions: >> >> Is it normal that gcc4li DLLs are not portable since they are .NET >> assemblies? >> > > Yes, it is normal because the structures layout is tied to 32-bit > little-endian architectures (i.e. pointer are 32-bit large, bit-fields > are arranged in little-endian fashion, etc...). On top of that SPARC64 > requires 64-bit alignment for all 64-bit operands (including long > integers, and floating-point doubles, not only pointers) something > that the CLI-BE layout engine doesn't enforce. > > >> Are there special configuration options to compile gcc4cli on SPARC64? >> > > If I remember correctly we should have a big-endian switch somewhere > which might help but it won't fix the alignment/layout problems, aside > from that you must make sure that on the SPARC64 you are using the > 32-bit version of Mono and its libraries as we have no support for > 64-bit architectures. > > Gabriele Svelto > |