Stuart, On Thu, Apr 16, 2020 at 12:10 AM Stuart Henderson <[email protected]> wrote: > > On 2020/04/15 21:52, Paul Hardy wrote: > > With what's available "out of the box" on OpenBSD 6.6, one conflict is > > that the latest version of autoconf available with pkg_add insists > > upon the latest version of GNU libtool, which is newer than the latest > > libtool version available through pkg_add. > > I don't understand this. We have 500+ ports that use autoconf 2.69 at > build time (and more that use a configure scripg pre-generated with > 2.69), many of which use libtool...
Sorry, I had put the prerequisite for 2.4.6 in my configure.ac file without even thinking about it. That's why it failed. I tried installing GNU libtool 2.4.6 from the GNU sources on OpenBSD 6.6 but it didn't work. So for the sake of expedience I just generated the configure file on another distro where libtool 2.4.6 installed okay. The whole thing built perfectly the first time and I didn't go back to investigating the OpenBSD failure, and forgot about the prerequisite I put in. I'd prefer using the latest GNU libtool version with the expectation that a package won't be affected by older libtool bugs, and it will have consistent behavior across distros. The latest released version, libtool 2.4.6, was created with automake 1.15 five years ago though. automake 1.15 had bugs that were corrected in version 1.16, one of which caused me a lot of trouble a couple of years ago until I figured out a workaround. So I am really hoping that GNU libtool will have a new release built with automake 1.16 but that's not OpenBSD's problem of course. *Anyways*, I didn't intend this thread to focus on libtool. As a first step, I just wanted to address the OpenBSD automake installation complaining about .c files left over that were created from lex / flex sources, because that affects even the pre-libtool versions. Thank you, Paul Hardy
