Closed GoogleCodeExporter closed 8 years ago
Maybe we should as distributions generally only install one version of libtool.
2.4.2 has been around a while but MSYS seems to maintain its own fork of some
kind. I don't know how backwards-compatible libtool is but at least this gives
it a chance. I know that autoconf/automake are less backwards-compatible but it
is usually possible to install more than one version of these and it will
automatically pick the right one.
Original comment by JerseyChewi@gmail.com
on 25 Jan 2014 at 11:01
Sorry, to clarify, I think we should force libtoolize but not aclocal (which is
part of automake).
Original comment by JerseyChewi@gmail.com
on 25 Jan 2014 at 11:49
So to be very clear, we should do build this way, with a -f flag on libtoolize?
libtoolize -c -f
aclocal
autoheader
autoconf
automake -a -c
Original comment by dan.bloo...@gmail.com
on 26 Jan 2014 at 1:23
I found this documentation on libtool:
http://www.gnu.org/software/libtool/manual/libtool.html#Invoking-libtoolize
Original comment by dan.bloo...@gmail.com
on 26 Jan 2014 at 1:25
Yes, just like that.
Original comment by JerseyChewi@gmail.com
on 26 Jan 2014 at 10:04
I make my test once again and I confirm "libtoolize -c -f" is sufficient to fix
my original problem.
Original comment by zde...@gmail.com
on 27 Jan 2014 at 6:54
Good. We'll use -f from here on out.
Original comment by dan.bloo...@gmail.com
on 27 Jan 2014 at 9:40
Original comment by dan.bloo...@gmail.com
on 6 Feb 2014 at 3:52
Original issue reported on code.google.com by
zde...@gmail.com
on 24 Jan 2014 at 8:11Attachments: