David Thompson wrote:
> In order to use the libtool branch, you will also have to have libtool
> installed. Depending on your platform, 1.4.3 should work
I already have libtool:
ltmain.sh (GNU libtool) 1.3.4-freebsd-ports (1.385.2.196 1999/12/07 21:47:57)
My platform is FreeBSD (4.7 = latest release), installed last week
with reasonably up-to-date software; but my libtool version is
1.3.4 rather than 1.4.3. Is that a typo of yours, or is the 3/4 swap
just a coincidence?
> An easy way to do this is to update to the main branch
>
> cvs update -A -d -P
> cvs update -r libtool -d -P
OK, done that, and then ran CVSMake:
---------------------------------------
$ ./CVSMake
#!/bin/sh -v
# These are the steps that must be done after a make maintainer-clean
# in order to ./configure this package.
libtoolize --force && \
aclocal && \
autoheader && \
automake -a -i && \
autoconf
libtoolize: `configure.in' does not exist
Try `libtoolize --help' for more information.
$
---------------------------------------
configure.in is indeed missing, but configure.ac is there (a
new libtool policy?). Does this mean my libtool version is too old?
Regards,
Rob.
PS: "libtoolize --help" gives:
Usage: libtoolize [OPTION]...
Prepare a package to use libtool.
--automake work silently, and assume that Automake is in use
-c, --copy copy files rather than symlinking them
--debug enable verbose shell tracing
-n, --dry-run print commands rather than running them
-f, --force replace existing files
--help display this message and exit
--ltdl install libltdl in a subdirectory
--ltdl-tar install the libltdl tarball
--version print version information and exit
You must `cd' to the top directory of your package before you run
`libtoolize'.
