![]() |
Blitz Support : |
From: Todd Veldhuizen (tveldhui_at_[hidden])
Date: 2003-09-04 13:30:36
Okay.... but I still think we should minimally include a premade
"configure" script in cvs. Would this cause problems I'm unaware
of?
Thanks,
Todd
-- Todd Veldhuizen / tveldhui_at_[hidden] / Indiana University Computer Science On Thu, 4 Sep 2003, Julian Cummings wrote: > Hi Todd, > > It's possible that you may need a more current version of libtool (I > have 1.4.3 and > there is now a 1.5 available) or that your m4 installation is broken. I > just did a > fresh checkout and configuration on my Linux box with no problems. Here is > what the normal output looks like: > > artemis [~/blitz-dev/blitz] autoreconf -fiv > autoreconf: Entering directory `.' > autoreconf: configure.in: not using Gettext > autoreconf: running: aclocal --output=aclocal.m4t > autoreconf: `aclocal.m4' is created > autoreconf: configure.in: tracing > autoreconf: running: libtoolize --copy --force > autoreconf: running: aclocal --output=aclocal.m4t > autoreconf: `aclocal.m4' is unchanged > autoreconf: running: /cacr/home/user/cummings/bin/autoconf --force > autoreconf: configure.in: not using Autoheader > autoreconf: running: automake --add-missing --copy --force-missing > configure.in: installing `./install-sh' > configure.in: installing `./mkinstalldirs' > configure.in: installing `./missing' > benchmarks/Makefile.am: installing `./depcomp' > autoreconf: Leaving directory `.' > > I do not have the symlink that Fernando Perez mentioned in his reply, > although I do have > a libtool.m4 file in /usr/local/share/aclocal. I believe this file is > used as the basis for the > aclocal.m4 file that is created locally in the blitz directory. The > bootstrap script that > Robert Techentin mentioned might be helpful, although I think it does > more or less what > is done by saying "autoreconf -fiv". > > Patrick Guio, who is helping me with Blitz maintenance, did most of the > mods to use the > standard autoconf tools. I agree that using libtool here is a bit of > overkill, since the actual > Blitz library is pretty trivial and almost all the action is in the > header files. But it *really* > does all work if your GNU tools are properly installed and up to date. > Of course, a more > intelligent version of "make" would make everything much easier. > > Regards, Julian C. > > > Todd Veldhuizen wrote: > > >I already have libtool 1.4.2 installed. I tried copying libtool.m4 into > >the blitz directory too and that didn't work. Eventually I just commented > >out the AC_PROG_LIBTOOL line from configure.in and that let me get a > >makefile. Is libtool really needed for blitz? Should we just comment out > >this line in cvs? > > > >I think the current state of affairs wrt installing from cvs is not so > >great. > > > >Can we go back to including configure etc. in the cvs? > > > >Thanks, > >Todd > > > > > > > > -- > Dr. Julian C. Cummings E-mail: cummings_at_[hidden] > California Institute of Technology Phone: 626-395-2543 > 1200 E. California Blvd., Mail Code 158-79 Fax: 626-584-5917 > Pasadena, CA 91125 > > > > _______________________________________________ > Blitz-support mailing list > Blitz-support_at_[hidden] > http://www.oonumerics.org/mailman/listinfo.cgi/blitz-support >