Dave Kleikamp wrote: > The tarball was built using automake 1.4. automake 1.5 expects the > depcomp script to be in the tarball, which automake 1.4 doesn't create. > I tried creating the tarball with automake 1.5.1, but depcomp still > didn't make it into the tarball. (I couldn't get automake 1.5.2 to work > at all.)
I'd suggest not to rebuild configures and Makefiles in release build. For example, building rpm now does: + ./configure --mandir=/usr/share/man/en/ creating cache ./config.cache checking for a BSD compatible install... /usr/bin/ginstall -c ... creating config.h + make cd . && aclocal cd . && automake --gnu --include-deps Makefile cd . && autoconf /bin/sh ./config.status --recheck running /bin/sh ./configure --mandir=/usr/share/man/en/ --no-create --no-recursion checking for a BSD compatible install... /usr/bin/ginstall -c There is no need for running aclocal, automake and autoconf IMHO, if configure script is already in tarball. Regards, Nerijus P.S. I am not subscribed. _______________________________________________ Jfs-discussion mailing list [EMAIL PROTECTED] http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-discussion
