SPECS: openldap.spec - better way to fix libtool 2.2 issues

Elan Ruusamäe glen at delfi.ee
Thu Jun 26 12:48:06 CEST 2008


On Wednesday 25 June 2008 18:26, Jakub Bogusz wrote:
> On Wed, Jun 25, 2008 at 12:16:48PM +0300, Elan Ruusamäe wrote:
> > On Thursday 19 June 2008 14:57, hawk wrote:
> > > -%{__libtoolize}
> > > -cp -f /usr/share/automake/config.sub ./build/
> > > +%{__libtoolize} --install
> >
> > do it globallly in rpm-build-macros?
>
> I don't think so, it's usually done by automake --add-missing and
> required only in projects which don't use automake.

would it hurt if added to libtool >= 2.0? e.g. append to libtoolize macro sth like:

libtoolize --version | awk '/^libtoolize/{split($NF, a, "."); v=a[1]"."a[2];if (v > 2.0) {print "--install"}}'



$ rpm --define "__libtoolize libtoolize --copy --force %(libtoolize --version | awk '/^libtoolize/{split(\$NF, a, \".\"); v=a[1]\".\"a[2];if (v > 2.0) print 
\"--install\"}')" -E %__libtoolize
libtoolize --copy --force

$ libtoolize --version
libtoolize (GNU libtool) 1.5.26

$ rpm --define "__libtoolize libtoolize --copy --force %(libtoolize --version | awk '/^libtoolize/{split(\$NF, a, \".\"); v=a[1]\".\"a[2];if (v > 2.0) print 
\"--install\"}')" -E %__libtoolize
libtoolize --copy --force --install

$ libtoolize --version
libtoolize (GNU libtool) 2.2.4



-- 
glen


More information about the pld-devel-en mailing list