Re: [RFC] Update to current automake/autoconf/libtool versions.

[DJ Delorie <dj at delorie dot com>]

> As far as I can tell offhand, none of the other patches depend on
> libiberty being updated, so one option is to upgrade the other
> directories, and leave libiberty alone.

That would be fine.  If you had a patch that depended on libiberty
being upgraded, I'd probably question it anyway.

> The downside of this is that gcc/binutils folks now need to keep
> multiple versions of the tools around, and I imagine it would play
> hell with --enable-maintainer-mode.

You didn't propose changing gcc, newlib, cygwin, sid, or many other
projects, so this will be an issue regardless.

> In what way is it a bad time to change libiberty?

GCC is getting ready to branch for a release.  After the branch, we'll
merge bib and be back to the usual openness.

> Would it be possible to convert the libiberty on the bib-branch, and
> import the binutils/gdb version from there?

By the time the issues are worked out for gdb/binutils and the switch
made there, gcc will hopefully have branched.  Plus the gcc head is
more stable than the branch anyway, which is what I'd prefer be the
main copy for everyone else.

How much of a hurry are you in, anyway?