[Mono-list] build of mono 1.1.7 & fails on Solaris: failure to compile mcs

Raja R Harinath rharinath at novell.com
Tue Jul 19 03:34:18 EDT 2005


"Gerard Tromp" <mono.lists at sanger.med.wayne.edu> writes:

> Raja R Harinath [mailto:rharinath at novell.com] writes:
>> "Gerard Tromp" <mono.lists at sanger.med.wayne.edu> writes:
>>> The build fails because make fails to build mcs. The failure appears to be
>>> in the scripts and configuration.
>> Nope :-)
>> [snip]
>>> gmake all-local
>>> gmake[7]: Entering directory `/home/tromp/software/mono-1.1.7/mcs/mcs'
>>> MONO_PATH="../class/lib/basic:$MONO_PATH"
>>> /home/tromp/software/mono-1.1.7/runtime/mono-wrapper
>>> ../class/lib/basic/mcs.exe   -d:NET_1_1 -d:ONLY_1_1 -debug /target:exe
>>> /out:mcs.exe cs-parser.cs  @mcs.exe.sources
>>> Segmentation Fault - core dumped
>>> gmake[7]: *** [../class/lib/net_1_1_bootstrap/mcs.exe] Error 139
>>> gmake[7]: Leaving directory `/home/tromp/software/mono-1.1.7/mcs/mcs'
>>> gmake[6]: *** [all.real] Error 2
>> It probably means there's something wrong with the just-compiled mono.
> Thanks for the reply. That would have been my initial guess also. Perhaps I
> should have indicated the additional diagnostics that I performed to rule
> that out.

And it is the right guess too, I think :-)

> 1. cmp shows no difference between class/lib/monolite/mcs.exe (part of the
> distribution) and the newly made class/lib/basic/mcs.exe (what is supposed
> to be the newly made mcs.exe) (The path references are relative to the mcs
> subdirectory.)
> 2. file class/lib/basic/mcs.exe indicates: data. Even for an incorrectly
> built binary object file indicates something like: "_binary_name_: ELF
> 32-bit MSB executable SPARC Version 1, dynamically linked, stripped" on a
> sparc system.
> 3. copying the mcs.exe (either one) executable to an x386 *nix system
> results in file yielding "mcs.exe: MS Windows PE 32-bit Intel 80386 console
> executable"

Which is all fine, but not to the point.  mcs.exe appears to be a proper
executable .NET assembly. 

As I said before, the problem is likely in the just built mono runtime,
not in the mcs.exe.  So, you'll have to see what happened to the 'mono'
binary in mono-1.1.7/mono/mini/.

- Hari

More information about the Mono-list mailing list