We just upgraded libtool from 1.5.26 to 2.2.6 and our build
broke. Our host requires 2.2.6 so keeping the old appears difficult.
Even though we only run autoreconf manually in our project, the new libtool
slipped into the project and the build broke.
I can fix this by rerunning autoreconf -i -f in the current trunk but
I cannot do that in already released SW.
I had the impression that the libtool files installed by libtoolize -f
should contain everything needed by libtool, that is, there would not be
any dependencies of the host libtool.
How can I prevent the new host libtool from slipping into
the project?
I would like to be able to run autoreconf even after upgrading the host libtool
too, if possible.
Jocke
_______________________________________________
http://lists.gnu.org/mailman/listinfo/libtool
