Re: [gentoo-dev] sanity checking libtool versions & portability

Re: [gentoo-dev] sanity checking libtool versions & portability

[Mike Frysinger]

On Fri, Dec 23, 2005 at 03:52:37PM +0100, erik.nolf@ugent.be wrote:
> In other words, it breaks portability. And let this be the one thing people
> expect from using GNU's ubiquitous autotools. Our comments follow:

this has been fixed already, you should update to libtool-1.5.20-r1

> c) follow advice on <http://www.mail-archive.com/libtool@gnu.org/msg08172.html>

i've already chatted with upstream about the version checking idea and
what we're doing now is the best course for Gentoo
-mike
-- 
gentoo-dev@gentoo.org mailing list

[gentoo-dev] sanity checking libtool versions & portability

[erik.nolf]

Hello,

We recently switched development platform from RedHat/Fedora to Gentoo.
Great you'd say. However, now our users (most notably on Solaris) complain
that our small utility's "./configure" bails out with the dreadful message:

	*** [Gentoo] sanity check failed! ***
	*** libtool.m4 and ltmain.sh have a version mismatch! ***
	*** (libtool.m4 = 1.5.20, ltmain.sh = ) ***

	Please run: ...

When in fact there is no mismatch. It seems Solaris regular "grep" or "sed" do
not handle "[[:space:]]" syntax used in libtool.m4's _LT_VERSION_CHECK macro.

	gentoo_ltmain_version=`grep '^[[:space:]]*VERSION=' $ltmain | sed -e...

In other words, it breaks portability. And let this be the one thing people
expect from using GNU's ubiquitous autotools. Our comments follow:

a) wouldn't a '^VERSION=' be sufficient?

	(strict but portable, at least we patched our libtool.m4 this way)

b) keep syntax, checks needed for proper grep/sed

	(too elaborated)

c) follow advice on <http://www.mail-archive.com/libtool@gnu.org/msg08172.html>

	(func_check_version_match sounds neat, don't know how to use yet ;-)

Thanks for reading. If one considers to implement c) we 'll be eager to help.
After all, we appreciate Gentoo very much.

Greetings,

	Erik



-- 
gentoo-dev@gentoo.org mailing list