On Sat, 11 Oct 2003, Micha Nelissen wrote: > Nelissen, M. wrote: > > > This is exactly the same as mine! (Without the --enable-debug). So my > > configure script itself is broken? Could it be my version of > > autoconf/automake or outdated or broken? > > This was indeed the case. I ran cygwin setup again and did some messing > with automake/autoconf. I turned out I had: autoconf, autoconf-devel, > autoconf-stable. Same for automake. I then removed autoconf and > reinstalled autoconf-stable. Again same for automake. Then all was built > succesfully. > > - Why are there 3 packages anyway? > There were major incompatible changes from the long lived autoconf version 2.13 to the current version 2.57a. Likewise for automake versuib 1.4-p5 to automake version 1.7.5a. Many projects have yet to convert to the new versions. As such, Cygwin's autoconf/automake maintainer was nice enough to provide both with wrapper scripts (the plain automake and autoconf packages) that try to pick the "right" versions.
> - Why is it autoconf, autoconf-stable and not autoconf-unstable, autoconf? > See above. As for your compile issues that were resolved by a re-install, I don't know. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
