Re: [opendx-dev] Libtool branch: no proper configure script generated !?!
I don't quite understand these errors now. Have you tried doing a "make distclean" and trying it again? Try deleting your aclocal.m4 (maybe its being persistent somehow). RANLIB should be getting set with the AC_PROG_LIBTOOL line and I know that's in there (line 12 of configure.ac). David David Thompson wrote: Update your version of automake to at least 1.6. 1.7 is preferable. Thanks! I have 1.7 installed, but now I get this: $ ./CVSMake #!/bin/sh -v # These are the steps that must be done after a make maintainer-clean # in order to ./configure this package. libtoolize15 --force && \ aclocal17 && \ autoheader257 && \ automake17 -a -i && \ autoconf257 You should update your `aclocal.m4' by running aclocal. src/exec/Makefile.am:52: Libtool library used but `LIBTOOL' is undefined src/exec/Makefile.am:52: src/exec/Makefile.am:52: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' src/exec/Makefile.am:52: to `configure.ac' and run `aclocal' and `autoconf' -- . David L. Thompson Visualization and Imagery Solutions, Inc. mailto:[EMAIL PROTECTED]5515 Skyway Drive, Missoula, MT 59804 Phone : (406)756-7472
Re: [opendx-dev] Libtool branch: no proper configure script generated !?!
David Thompson wrote: > Update your version of automake to at least 1.6. 1.7 is preferable. > Thanks! I have 1.7 installed, but now I get this: $ ./CVSMake #!/bin/sh -v # These are the steps that must be done after a make maintainer-clean # in order to ./configure this package. libtoolize15 --force && \ aclocal17 && \ autoheader257 && \ automake17 -a -i && \ autoconf257 You should update your `aclocal.m4' by running aclocal. src/exec/Makefile.am:52: Libtool library used but `LIBTOOL' is undefined src/exec/Makefile.am:52: src/exec/Makefile.am:52: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' src/exec/Makefile.am:52: to `configure.ac' and run `aclocal' and `autoconf' again. src/exec/dpexec/Makefile.am:5: Libtool library used but `LIBTOOL' is undefined src/exec/dpexec/Makefile.am:5: src/exec/dpexec/Makefile.am:5: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' src/exec/dpexec/Makefile.am:5: to `configure.ac' and run `aclocal' and `autoconf' again. src/exec/dxexec/Makefile.am:8: Libtool library used but `LIBTOOL' is undefined src/exec/dxexec/Makefile.am:8: src/exec/dxexec/Makefile.am:8: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' src/exec/dxexec/Makefile.am:8: to `configure.ac' and run `aclocal' and `autoconf' again. src/exec/dxmods/Makefile.am:6: Libtool library used but `LIBTOOL' is undefined src/exec/dxmods/Makefile.am:6: src/exec/dxmods/Makefile.am:6: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' src/exec/dxmods/Makefile.am:6: to `configure.ac' and run `aclocal' and `autoconf' again. src/exec/hwrender/Makefile.am:7: Libtool library used but `LIBTOOL' is undefined src/exec/hwrender/Makefile.am:7: src/exec/hwrender/Makefile.am:7: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' src/exec/hwrender/Makefile.am:7: to `configure.ac' and run `aclocal' and `autoconf' again. src/exec/hwrender/opengl/Makefile.am:5: Libtool library used but `LIBTOOL' is undefined src/exec/hwrender/opengl/Makefile.am:5: src/exec/hwrender/opengl/Makefile.am:5: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' src/exec/hwrender/opengl/Makefile.am:5: to `configure.ac' and run `aclocal' and `autoconf' again. src/exec/libdx/Makefile.am:72: Libtool library used but `LIBTOOL' is undefined src/exec/libdx/Makefile.am:72: src/exec/libdx/Makefile.am:72: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' src/exec/libdx/Makefile.am:72: to `configure.ac' and run `aclocal' and `autoconf' again. src/uipp/base/Makefile.am:5: library used but `RANLIB' is undefined src/uipp/base/Makefile.am:5: src/uipp/base/Makefile.am:5: The usual way to define `RANLIB' is to add `AC_PROG_RANLIB' src/uipp/base/Makefile.am:5: to `configure.ac' and run `autoconf' again. src/uipp/dxl/Makefile.am:16: Libtool library used but `LIBTOOL' is undefined src/uipp/dxl/Makefile.am:16: src/uipp/dxl/Makefile.am:16: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' src/uipp/dxl/Makefile.am:16: to `configure.ac' and run `aclocal' and `autoconf' again. src/uipp/dxuilib/Makefile.am:5: library used but `RANLIB' is undefined src/uipp/dxuilib/Makefile.am:5: src/uipp/dxuilib/Makefile.am:5: The usual way to define `RANLIB' is to add `AC_PROG_RANLIB' src/uipp/dxuilib/Makefile.am:5: to `configure.ac' and run `autoconf' again. src/uipp/widgets/Makefile.am:5: library used but `RANLIB' is undefined src/uipp/widgets/Makefile.am:5: src/uipp/widgets/Makefile.am:5: The usual way to define `RANLIB' is to add `AC_PROG_RANLIB' src/uipp/widgets/Makefile.am:5: to `configure.ac' and run `autoconf' again. $ Can I safely ignore this? Regards, Rob.
Re: [opendx-dev] Libtool branch: no proper configure script generated !?!
Update your version of automake to at least 1.6. 1.7 is preferable. David I have DX/CVS updated to the libtool branch. For that I have: libtoolize (GNU libtool15) 1.5 aclocal (GNU automake) 1.5 autoheader (GNU Autoconf) 2.57 automake (GNU automake) 1.5 autoconf (GNU Autoconf) 2.57 When I do the ./CVSMake, I get: $ ./CVSMake #!/bin/sh -v # These are the steps that must be done after a make maintainer-clean # in order to ./configure this package. libtoolize15 --force && \ aclocal && \ autoheader257 && \ automake -a -i && \ autoconf257 You should update your `aclocal.m4' by running aclocal. configure.ac: 9: `automake requires `AM_CONFIG_HEADER', not `AC_CONFIG_HEADER' configure.ac: 964: automake requires `AM_PROG_LEX', not `AC_PROG_LEX' automake: configure.ac: `AM_INIT_AUTOMAKE' must be used $ There seems to be something wrong with the DX automake files, that causes the CVSMake to bail out before continuing with the autoconf script. And so the configure script is not there! --- Running these steps individually: $ libtoolize15 --force You should update your `aclocal.m4' by running aclocal. $ aclocal $ autoheader257 $ automake -a -i configure.ac: 9: `automake requires `AM_CONFIG_HEADER', not `AC_CONFIG_HEADER' configure.ac: 964: automake requires `AM_PROG_LEX', not `AC_PROG_LEX' automake: configure.ac: `AM_INIT_AUTOMAKE' must be used $ autoconf257 $ Then there is a configure script generated. --- $ ./configure --prefix=/opt --x-includes=/usr/local/include --x-libraries=/usr/local/lib checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking build system type... i386-unknown-freebsd4.8 checking host system type... i386-unknown-freebsd4.8 checking for ranlib... ranlib checking for style of include used by make... GNU checking for gcc... gcc checking for C compiler default output... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking dependency style of gcc... none checking for ld used by GCC... /usr/libexec/elf/ld checking if the linker (/usr/libexec/elf/ld) is GNU ld... yes checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes ./ltconfig: ./ltconfig: No such file or directory configure: error: libtool configure failed $ Any idea why all this is not properly working? Thanks, Rob. -- . David L. Thompson Visualization and Imagery Solutions, Inc. mailto:[EMAIL PROTECTED]5515 Skyway Drive, Missoula, MT 59804 Phone : (406)756-7472
[opendx-dev] Libtool branch: no proper configure script generated !?!
I have DX/CVS updated to the libtool branch. For that I have: libtoolize (GNU libtool15) 1.5 aclocal (GNU automake) 1.5 autoheader (GNU Autoconf) 2.57 automake (GNU automake) 1.5 autoconf (GNU Autoconf) 2.57 When I do the ./CVSMake, I get: $ ./CVSMake #!/bin/sh -v # These are the steps that must be done after a make maintainer-clean # in order to ./configure this package. libtoolize15 --force && \ aclocal && \ autoheader257 && \ automake -a -i && \ autoconf257 You should update your `aclocal.m4' by running aclocal. configure.ac: 9: `automake requires `AM_CONFIG_HEADER', not `AC_CONFIG_HEADER' configure.ac: 964: automake requires `AM_PROG_LEX', not `AC_PROG_LEX' automake: configure.ac: `AM_INIT_AUTOMAKE' must be used $ There seems to be something wrong with the DX automake files, that causes the CVSMake to bail out before continuing with the autoconf script. And so the configure script is not there! --- Running these steps individually: $ libtoolize15 --force You should update your `aclocal.m4' by running aclocal. $ aclocal $ autoheader257 $ automake -a -i configure.ac: 9: `automake requires `AM_CONFIG_HEADER', not `AC_CONFIG_HEADER' configure.ac: 964: automake requires `AM_PROG_LEX', not `AC_PROG_LEX' automake: configure.ac: `AM_INIT_AUTOMAKE' must be used $ autoconf257 $ Then there is a configure script generated. --- $ ./configure --prefix=/opt --x-includes=/usr/local/include --x-libraries=/usr/local/lib checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking build system type... i386-unknown-freebsd4.8 checking host system type... i386-unknown-freebsd4.8 checking for ranlib... ranlib checking for style of include used by make... GNU checking for gcc... gcc checking for C compiler default output... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking dependency style of gcc... none checking for ld used by GCC... /usr/libexec/elf/ld checking if the linker (/usr/libexec/elf/ld) is GNU ld... yes checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes ./ltconfig: ./ltconfig: No such file or directory configure: error: libtool configure failed $ Any idea why all this is not properly working? Thanks, Rob.
