Re: superfluous link rule for unknown languages

[Tim Van Holder]

> We could make a special case here (don't make the foo$(EXEEXT) target
> if we see `foo') and just hope that doesn't happen.

That's what I was suggesting.

> 
> The other question is how and when to define EXEEXT.
> One idea is to hook it to AC_PROG_CC/CXX via hackery in
> AM_INIT_AUTOMAKE.  That is, make it mandatory just like it is in
> autoconf 2.50.

We could just have a bare AC_SUBST(EXEEXT) in AM_INIT; if EXEEXT is
never set (as in autoconf < 2.50 without AC_EXEEXT) it would still
get substituted (with the empty string, which is what we want as
default anyway).
Not the cleanest solution, but one that (probably) works.