Re: structuring a front-end subdirectory

[Paolo Bonzini <bonzini at gnu dot org>]

>  A number of these sources are indeed shared (some compiler sources
>  are used by the library and/or some tools) and moving them is not
>  straightforward.

Would it be possible to add a --enable-small option to libada, which 
would enable compilation of the subset used by GNAT?  Then, one could 
make libada build twice: as a host module with --enable-small, and as a 
target module without the option.


>   1) Add a new "gcc_subdir" variable in config-lang.in. When set, configure
>      looks for a complete config-lang.in, makefile fragments (Make-lang.in),
>      lang tree files, ... in $(srcdir)/<lang_name>/<gcc_subdir>. When not
>      set it looks in $(srcdir)/<lang_name> as usual.

Could you please outline the final "look" of the filesystem?  It would 
seem to me that if everything was moved to libada, this would not be 
necessary anymore.  If you need this as a stopgap measure, it's fine by 
me but I would like a comment in configure.ac saying that this is bound 
to disappear and should not be used by other language front-ends.

In this case, by the way, the gengtype changes would also be less 
necessary, and I could approve the configure.ac patch myself (note that 
I have not finished reviewing it, so this is not --yet-- an approval).

Paolo