Mail Archives: djgpp/2001/07/25/05:45:04
Peter J. Farley III <pjfarley3 AT escape DOT com> wrote:
> In the past, running DJGPP autoconf against previously unix-only
> configure scripts was advised to permit various unixy tests
> (especially the notorious test for executables with no "EXE_EXT"
> macros used) to work cleanly.
Actually, that was quite a while back, AFAIK. At the moment, the
recommended solution seems to be to just run the configure script
as-is, after making sure that the DJGPP version of config.site is in
scope. Most of the necessary tricks (TEST_FINDS_EXE, PATH_SEPARATOR=:
and so on) have been put into config.site, for that purpose.
> With the advent of autoconf 2.50 and the more recent port of bash
> 2.04, is it still advisable to re-run autoconf on unix-developed
> source packages to re-create the configure script?
No, it isn't. autoconf-2.50 is a beta release, and it's incompatible
with existing packages and their configure.in's. Even on actual Unix
systems, most packages stop working if you run autoconf-2.50. If you
want to run autoconf on existing packages, use the DJGPP port of
autoconf-2.13. Only if the package explicitly requires 2.50 (you'll
notice: it should have AC_PREREQ(2.50)), you'll want to use that.
--
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.
- Raw text -