(1) If I do a make dist after having changed some files, I get an error:
Cannot make dist before commit
and I cannot make dist. I realize why it was done, but I like to be able to
make my own custom distributions which I unpack on remote machines for
testing. As you know I have access to many machines around the world, but I
don't always want to (or can) use cvs server access b/c it's slower, and may
not be permitted through a firewall.
I'd suggest the following friendlier patch:
Index: Makefile.am
===================================================================
RCS file: /var/cvs/libtool/Makefile.am,v
retrieving revision 1.56
diff -u -r1.56 Makefile.am
--- Makefile.am 2000/02/22 23:35:52 1.56
+++ Makefile.am 2000/04/01 20:53:11
@@ -63,7 +63,7 @@
update-timestamps:
@if (cd $(srcdir) && test -d CVS && \
$(CVS) -n update $(TSDEPS_DIST) | grep '^M'); then \
- echo "Cannot make dist before commit"; exit 1; else :; fi
+ echo "WARNING: please commit before make dist"; fi
$(MAKE) TSDEPS="$(TSDEPS_DIST)" $(srcdir)/ltconfig $(srcdir)/ltmain.sh
# Do line number substitution, as well as PACKAGE, VERSION and TIMESTAMP.
(2) The config.{sub,guess} distributed in libtool CVS tree are rather old.
The "common" GNU cvs package is gone. Instead, the newer files are
distributed from ftp://ftp.gnu.org/pub/gnu/config/
(3) when running bootstrap, using the latest autoconf/automake, I get
several of these errors:
> configure.in:35: warning: The macro `AC_OUTPUT_COMMANDS' is obsolete.
> You should run autoupdate.
> configure.in: 33: `AM_PROG_LIBTOOL' is obsolete, use `AC_PROG_LIBTOOL' instead
> configure.in:50: warning: The macro `AC_LANG_C' is obsolete.
> configure.in:29: warning: AC_C_CONST was called before AC_PROG_CC_STDC
I've asked about it a while back, and was told that these were new changes
in autoconf/automake and that you wanted to wait until autconf became more
stable. It's been a while since those changes were put in, no? Shouldn't
libool try to keep up w/ autoconf? I think it has to, b/c once the new
autoconf is released, you'd pretty much have to update libtool so the
warnings go away (else you'll get many similar user complaints).
Making the changes to libtol is pretty simple. I can make them and submit a
patch if you'd like.
Cheers,
Erez.
