libtool-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: fix path search initialisation bugs [libtool--gary--1.0--patch-9]


From: Ralf Wildenhues
Subject: Re: fix path search initialisation bugs [libtool--gary--1.0--patch-9]
Date: Mon, 21 Mar 2005 08:45:44 +0100
User-agent: Mutt/1.4.1i

Hi Gary,

* Gary V. Vaughan wrote on Sun, Mar 20, 2005 at 10:10:02PM CET:
> 
> Thanks for the reviews :-)

Sure.

> Ralf Wildenhues wrote:
> > * Gary V. Vaughan wrote on Sun, Mar 20, 2005 at 05:01:01PM CET:
> >
> >>Okay to commit?
> >
> > This is getting more and more complicated..
> > but yes.
> 
> There is an alternative to the complicated part of this patch.  We
> could move config/ltmain.sh out of $top_srcdir/config and trade a few
> more files in $top_srcdir for a simpler libtoolize?
> 
> Now that I think about it, it does seem sensible to make the $top_srcdir
> layout of installed files used by libtoolize match their layout in the
> installation tree, which will make libtoolizes life a whole lot easier
> all round.  Shall we aim at that instead of this patch?

I'm not so sure things *will* get easier that way.

> >>    * libtoolize.m4sh: Fix a typo, s/pkgvltdldirs/pkgvdatadirs/.
> >>    When using -I to test an uninstalled libtoolize, we need to add
> >>    the config subdirectory to the search path so that ltmain.sh can
> >>    be found in the source tree.

Would it not suffice to put all the testsuite tests which would need
this, into `installcheck'?  Would that defeat some purpose?

Regards,
Ralf




reply via email to

[Prev in Thread] Current Thread [Next in Thread]