Would anyone be willing to comment on the differences and ramifications
of using the mcs.exe created by the mono src tree vs. the mcs.exe
created in the mcs src tree?

I am still unable to compile mcs unless I skip the mcs compiler steps
and copy the mcs.exe from the mono src tree (IOW, I am compiling the
class library using the mcs.exe created by the mono source tree). The
error I am getting is below:

make[2]: Entering directory `/home/sdowns/src/mono/mcs/class/corlib'
touch library-deps.stamp
MONO_PATH= mono ../../mcs/mcs.exe --target library --noconfig -o
../lib/corlib.dll --unsafe --nostdlib @.response

** ERROR **: file jit.c: line 1441 (mono_analyze_stack): assertion
failed: (sbb->outdepth == (sp - stack))
aborting...
make[2]: *** [../lib/corlib.dll] Aborted


Steve




On Fri, 2002-08-02 at 09:41, Steven Downs wrote:
> I have been seeing this as well for the past week.  Prior to the 29th I
> was able to compile everything fine.  I have removed all the source dirs
> and checked everything out fresh as well.
> 
> I am on a standard RH 7.3 using a self-compiled gcc 3.1 (incidentally I
> went back to the RH standard gcc 2.96 and got the same problem).
> 
> As a side note: the mcs.exe created during the mono compile happens to
> work if it is copied over the mcs.exe in the mcs/ directory after it has
> been compiled--I just don't know if this is creating a really compliant
> set of classes (XSP works for me which is what I have been testing
> though).
> 
> Steve
> 
> On Fri, 2002-08-02 at 08:54, Stephen Bardsley wrote:
> > Greetings:
> > 
> > I am having trouble compiling mcs.  Following is the error
> > being reported:
> > 
> > make[2]: Entering directory `/home/sbardsley/Projects/Mono/mcs/class/corlib'
> > MONO_PATH= mono ../../mcs/mcs.exe --target library --noconfig -o
> > ../lib/corlib.dll --unsafe --nostdlib @.response
> > 
> > ** ERROR **: file jit.c: line 1441 (mono_analyze_stack): assertion failed: 
>(sbb->outdepth
> > == (sp - stack))
> > aborting...
> > 
> > -------
> > 
> > I am using the freshest sources checked out of CVS for mono and mcs.
> > The mono module compiles with no problem.
> > 
> > Is this a known issue or am I doing something wrong?
> > 
> > Thanks for your help.
> > 
> > 
> > Steve
> > _____________________
> > Stephen Bardsley
> > RLW Inc.
> > Malta, NY
> > 
> > 
> > _______________________________________________
> > Mono-list maillist  -  [EMAIL PROTECTED]
> > http://lists.ximian.com/mailman/listinfo/mono-list
> 




_______________________________________________
Mono-list maillist  -  [EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/mono-list

Reply via email to