Charles Wilson wrote:
> /not/ update them at all;
> 1) The current and soon-to-be-released gcc's, based on gcc-3.4.5 and
> gcc-4.3.x, both still require autoconf-2.59 and automake-1.9.6
Good reasoning.
> So, as soon as I spin the "regular" cygwin autoconf-2.64 package, then
> our "standard" auto* installations will satisfy gcc's needs; all you'd
> need to do is /stop/ setting PATH to prepend /opt/gcc-tools/bin.
Yeh, this makes sense. Leave the old version there, for when it's needed.
> ...until automake-1.11.1 or autoconf-2.65 is released. Then we get to
> worry about it more. I've a few ideas about that, but for later...unless
> you want to handle the transition /now/ for gcc-tools-*.
Nah, can't see any reason. Maybe by the time that happens we'll be able to
drop the 2.59 version and go back to using /opt/gcc-tools again.
> Side question: has anybody checked to see if src/winsup can handle
> autoconf-2.64 and automake-1.11?
Nope, not me. Yet.
cheers,
DaveK
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
