Hi Paul, On Tue, Oct 25, 2011 at 12:44:00PM -0400, Paul Alfille wrote:
> Thanks for responding Chris. This is from the cvs since I want to > continue development. > > I'm sure libtool combines incredible cross-system intelligence, but its > operation is rather opaque and documentation abysmal. I thought that New Riders' book "GNU AUTOCONF, AUTOMAKE and LIBTOOL" (The Goat Book, http://sourceware.org/autobook/) was a decent reference on the subject. It's a bit old now, though. There is a newer book on Autotools that I have not had a chance to look at: A Practioner's Guide to GNU Autoconf, Automake, and Libtool http://shop.oreilly.com/product/9781593272067.do Seems to have an online version here: http://www.freesoftwaremagazine.com/books/autotools_a_guide_to_autoconf_automake_libtool Cheers, Eloy Paris.- > > I remember the IBM mainframe days with the JCL punch cards that you placed > before your program and never dared touch. Not much has changed! > > Paul > > On Tue, Oct 25, 2011 at 12:24 PM, Chris Boot <bo...@bootc.net> wrote: > > > On 25/10/2011 16:43, Paul Alfille wrote: > > > > Any suggestions on fixing this complie problem? > > > > The make script sails through owshell and then dies in ownet. This is > > from a clean pull of the source code. > > > > > > Do you mean from CVS or from a tarball? > > > > > > owshell are binaries and ownet a library. Maybe that's the difference? > > My system has > > *libtool (GNU libtool) 2.4* > > *autoconf (GNU Autoconf) 2.68* > > *automake (GNU automake) 1.11.1* > > GNU Make 3.81 > > > > Output: > > ... > > Making all in ownet > > make[2]: Entering directory `/home/paul/owfs/module/ownet' > > Making all in c > > make[3]: Entering directory `/home/paul/owfs/module/ownet/c' > > Making all in src > > make[4]: Entering directory `/home/paul/owfs/module/ownet/c/src' > > Making all in c > > make[5]: Entering directory `/home/paul/owfs/module/ownet/c/src/c' > > /bin/bash ../../../../../libtool --tag=CC --mode=compile gcc > > -DHAVE_CONFIG_H -I. -I../../../../../src/include -I../include > > -fexceptions -Wall -W -Wundef -Wshadow -Wpointer-arith -Wcast-qual > > -Wcast-align -Wstrict-prototypes -Wredundant-decls -D__EXTENSIONS__ > > -D_FILE_OFFSET_BITS=64 -D_XOPEN_SOURCE=500 -D_BSD_SOURCE=1 > > -D_ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -pthread -g -O2 -m64 > > -D_XOPEN_SOURCE=500 -D_BSD_SOURCE=1 -D_ISOC99_SOURCE=1 > > -D_POSIX_C_SOURCE=200112L -MT compat.lo -MD -MP -MF .deps/compat.Tpo -c -o > > compat.lo compat.c > > mv -f .deps/compat.Tpo .deps/compat.Plo > > mv: cannot stat `.deps/compat.Tpo': No such file or directory > > make[5]: *** [compat.lo] Error 1 > > ... > > > > > > I had something similar happen to me. The bootstrap script couldn't produce > > a working libtool for me, so I ran 'autoreconf --install' and that fixed > > things for me. It seems to rewrite 'src/scripts/install/ltmain.sh' among > > other things. > > > > HTH, > > Chris > > > > -- > > Chris bootbo...@bootc.net > > ------------------------------------------------------------------------------ The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
