[Mono-devel-list] PATCH: jay location in debugger

[Miguel de Icaza]

Hello,

>     Building debugger in an isolated location fails because it assumes a 
> particular path for the mcs source and that mcs src there is already 
> built. Is this patch ok?

This is becoming a FAQ.

Today Jay can not be installed (if it is installed, it is a bug),
because Jay does not know where its datafiles are.  In particular, it
matters where the skeleton lives.

This is not much of an issue for the debugger;  The debugger should
just ship with a generated parser.  Anyone who wants to rebuild the
language for the debugger (which btw, should be redone to start with
with something different than jay) must have the mcs setup as expected.

You can try to fix jay, the autoconf tools, but am not likely going to
have time to review it, and it is not important if you use tarballs
anyways.