Re: searching for libtool.m4 in tests/defs

2004-05-27 Thread Gary V. Vaughan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ralf Wildenhues wrote:
| The Automake test suite (CVS HEAD version) explicitly looks for
| libtool.m4 in aclocaldir and a list of directories specified in the
| dirlist file there.  Now recent CVS Libtool versions remove libtool.m4
| from that location and add it to .../share/libtool/m4/ .
| This lead to many SKIPped tests in the test suite (quite silently, by
| the way).  How would I resolve this issue correctly?  Is this an
| Automake, a Libtool or a user problem?  Why is there no standard way to
| ask a libtoolize for its corresponding m4 files (at least, one would
| think, newer versions would improve this situation)?
That is a good idea.  What do you think the interface should be?  Maybe:
$ libtoolize --macro-files
/usr/local/share/libtool/m4/libtool.m4
/usr/local/share/libtool/m4/ltdl.m4
/usr/local/share/libtool/m4/ltoptions.m4
/usr/local/share/libtool/m4/ltsugar.m4
/usr/local/share/libtool/m4/ltversion.m4
Cheers,
Gary.
- --
Gary V. Vaughan  ())_.  [EMAIL PROTECTED],gnu.org}
Research Scientist   ( '/   http://tkd.kicks-ass.net
GNU Hacker   / )=   http://www.gnu.org/software/libtool
Technical Author   `(_~)_   http://sources.redhat.com/autobook
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFAtg/6FRMICSmD1gYRApD8AJ4sSirtBJNYdYF+51eUFVHydGNsBgCfQ4wx
TtafwumTe1g6bGzx7iY0jKk=
=jHT5
-END PGP SIGNATURE-



Re: searching for libtool.m4 in tests/defs

2004-05-27 Thread Ralf Wildenhues
* Gary V. Vaughan wrote on Thu, May 27, 2004 at 05:57:47PM CEST:
 Ralf Wildenhues wrote:
*snip*
 | Automake, a Libtool or a user problem?  Why is there no standard way to
 | ask a libtoolize for its corresponding m4 files (at least, one would
 | think, newer versions would improve this situation)?
 
 That is a good idea.  What do you think the interface should be?  Maybe:
 
 $ libtoolize --macro-files
 /usr/local/share/libtool/m4/libtool.m4
 /usr/local/share/libtool/m4/ltdl.m4
 /usr/local/share/libtool/m4/ltoptions.m4
 /usr/local/share/libtool/m4/ltsugar.m4
 /usr/local/share/libtool/m4/ltversion.m4

As I was very unsure about what tools will ever need this -- maybe.
I'm not sure if I want the switch --ltdl (and whatever other switches
libtoolize will ever have that change the set of macro files) to affect
the output (maybe --all-macro-files as well?).  The other idea that
springs to my mind is to have
   libtoolize --macro-srcdir
give me the directory from which aclocal could pull those macro files.
I'm not in a position to decide as I know far too little about the
overall machinery involved.

Regards,
Ralf




Re: searching for libtool.m4 in tests/defs

2004-05-27 Thread Alexandre Duret-Lutz
 Ralf == Ralf Wildenhues [EMAIL PROTECTED] writes:

 Ralf The Automake test suite (CVS HEAD version) explicitly looks for
 Ralf libtool.m4 in aclocaldir and a list of directories specified in the
 Ralf dirlist file there.  Now recent CVS Libtool versions remove libtool.m4
 Ralf from that location and add it to .../share/libtool/m4/ .

Yep.  Gary agreed to revert this and populate
/usr/share/aclocal/ as in the past.  But it's not a big deal to
work around: simply copy these files to /usr/share/aclocal by
hand.

Gary, I've also noticed that in packages that do not use
`ACLOCAL_AMFLAGS = -I m4dir' the libtoolize script will dump all
m4 macros in the current directory.  This sounds bogus because
no tool will read these macros there.  People that do not use 
`-I m4dir' simply want their aclocal.m4 filled.
-- 
Alexandre Duret-Lutz





searching for libtool.m4 in tests/defs

2004-05-26 Thread Ralf Wildenhues
The Automake test suite (CVS HEAD version) explicitly looks for
libtool.m4 in aclocaldir and a list of directories specified in the
dirlist file there.  Now recent CVS Libtool versions remove libtool.m4
from that location and add it to .../share/libtool/m4/ .
This lead to many SKIPped tests in the test suite (quite silently, by
the way).  How would I resolve this issue correctly?  Is this an
Automake, a Libtool or a user problem?  Why is there no standard way to
ask a libtoolize for its corresponding m4 files (at least, one would
think, newer versions would improve this situation)?

Regards,
Ralf