> | After setting some environment variables (CC, etc.) and correcting a DJGPP
> | specific bug in Bash 2.04, the test went well with one minor and one major
> | exception.
>
> Could you give more details on these steps? What can be done to have
> it right without tuning by hand?
What I set i
> "Steven" == Steven G Johnson <[EMAIL PROTECTED]> writes:
Steven> My inclination is to think that the list of things "required"
Steven> for 2.15 is a little overly ambitious. If some minor issue is
Steven> unchanged from 2.13, e.g. not enough environment variables
Steven> being documented,
| Seeing as how Akim wants DJGPP to pass the testsuite, I figure it would be a
| good idea report my initial results using DJGPP and Autoconf from CVS.
Thanks a lot!
| After setting some environment variables (CC, etc.) and correcting a DJGPP
| specific bug in Bash 2.04, the test went well wi
> "Mo" == Mo DeJong <[EMAIL PROTECTED]> writes:
Mo> mo(~/project/SDL)% grep AC_CHECK_TOOL_PREFIX *
Mo> acinclude.m4:[AC_REQUIRE([AC_CHECK_TOOL_PREFIX])dnl
Mo> This acinclude.m4 file seems to have been generated by libtool.
:( OK, thanks, will add a stub for it.
> "Paul" == Paul Berrevoets <[EMAIL PROTECTED]> writes:
>> If you want to get folks using and improving Java macros, you need
>> to make them part of the "standard" install.
Paul> I concur that Java is ubiquitous enough to warrant "standard"
Paul> support.
The long range goal is to have Aut
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> But we have to be careful, since there are two (three?)
Alexandre> kinds of Java compilers: those that translate Java source
Alexandre> to bytecode, and those (that?) that translate(s?) Java
Alexandre> source (or bytecod
> "Mo" == Mo DeJong <[EMAIL PROTECTED]> writes:
Mo> How much interest would there be in adding Java to the > autoconf
Mo> supported languages?
Alexandre> I'd certainly welcome this effort, but I don't think this
Alexandre> is something for autoconf 2.50.
Mo> I am not really interested in do
