On Thu, Sep 07, 2000 at 09:51:50AM -0700, Bruce Korb wrote:
>
> Anyway, the last message bothers me:
>
> $ ./bootstrap
> [[snip]]
> configure.in: 33: required file `../ltconfig' not found
Already fixed in the repository. Please update again.
The problem is deepr than the cheap fix I committed. libtool no
longer creates or uses an ltconfig, since I have moved all of that
functionality into libtool.m4 so that the tests can be written using
autoconf macros, rather than writing in raw shell. Unfortunately,
automake hardcodes ltconfig (I had assumed it relied on libtoolize).
Should I commit the following to libtool as an ugly fix?
$ echo "This file is intentionally blank" > ltconfig
$ cvs add ltconfig
$ clcommit
I fear that this will lead to a generation of packages which ship a
bogus ltconfig file...
Here is a patch to CVS automake to fix the problem properly.
Cheers,
Gary.
--
___ _ ___ __ _ mailto: [EMAIL PROTECTED]
/ __|__ _ _ ___ _| | / / | / /_ _ _ _ __ _| |_ __ _ ___ [EMAIL PROTECTED]
| (_ / _` | '_|// / |/ /| |/ / _` | || / _` | ' \/ _` | _ \
\___\__,_|_|\_, /|___(_)___/\__,_|\_,_\__, |_||_\__,_|//_/
home page: /___/ /___/ gpg public key:
http://www.oranda.demon.co.uk http://www.oranda.demon.co.uk/key.asc
2000-09-07 Gary V. Vaughan <[EMAIL PROTECTED]>
* automake.in (libtoolize_files): CVS libtool no longer
generates or uses ltconfig.
Index: automake.in
===================================================================
RCS file: /cvs/automake/automake/automake.in,v
retrieving revision 1.795
diff -u -p -r1.795 automake.in
--- automake.in 2000/08/30 17:54:33 1.795
+++ automake.in 2000/09/07 21:02:29
@@ -189,7 +189,7 @@ $seen_libtool = 0;
$libtool_line = 0;
# Files installed by libtoolize.
-@libtoolize_files = ('ltconfig', 'ltmain.sh', 'config.guess', 'config.sub');
+@libtoolize_files = ('ltmain.sh', 'config.guess', 'config.sub');
# TRUE if we've seen AM_MAINTAINER_MODE.
$seen_maint_mode = 0;
