On our Mac OS X system here, libtool is /usr/bin/libtool, so there is no need to set any environment variables. I don't know why it is different on your system. You do need a fairly current set of the autoconf/automake/libtool tools installed in order for everything to configure and build properly, and *all the tools* need to be installed in the same place, since they interact and refer to each other when you run autoreconf. If you use the --disable-fortran option, you will not be able to make the benchmarks codes, since they require a Fortran compiler. I changed the blitz configure script to not bother trying to create a Makefile for the benchmarks directory in this case. Everything else should be OK.

I just was playing with it. Because on OS X libtool is actually glibtool and libtoolize is glibtoolize, I had to do the following:

export LIBTOOLIZE=/usr/bin/glibtoolize

export LIBTOOL=/usr/bin/glibtool

This fixed some things, but OS X comes with an old automake (version 1.6.3). If I autoreconf it actually makes the configure file though. I can ./configure --prefix=/Users/helenbrk/Codes --disable-fortran, make, & make install and get the library as well as the include files but it reports an error when it gets to "benchmarks". However, I did end up with a working copy of blitz++ so I was happy. The following shows the errors I ended up with.

autoreconf: Entering directory `.'

autoreconf: configure.ac: not using Gettext

autoreconf: running: aclocal -I m4 --output=aclocal.m4t

autoreconf: `aclocal.m4' is created

autoreconf: configure.ac: tracing

autoreconf: running: /usr/bin/glibtoolize --copy --force

Putting files in AC_CONFIG_AUX_DIR, `config'.

autoreconf: `aclocal.m4' is unchanged

autoreconf: running: /usr/bin/autoconf --force

autoreconf: running: /usr/bin/autoheader --force

autoreconf: running: automake --add-missing --copy --force-missing

configure.ac:9: `automake requires `AM_CONFIG_HEADER', not `AC_CONFIG_HEADER'

configure.ac: installing `config/install-sh'

configure.ac: installing `config/mkinstalldirs'

configure.ac: installing `config/missing'

configure.ac:13: require version 1.9, but have 1.6.3

benchmarks/Makefile.am: installing `config/depcomp'

doc/Makefile.am:44: installing `config/texinfo.tex'

autoreconf: automake failed with exit status: 1

Configure doesn't report any errors, and make and make install report errors when getting to "benchmarks":

gamgee:~/Codes/blitz helenbrk$ make

Making all in benchmarks

make[1]: *** No rule to make target `all'. Stop.

make: *** [all-recursive] Error 1

Making install in benchmarks

make[1]: *** No rule to make target `install'. Stop.

make: *** [install-recursive] Error 1

I downloaded the newest version of automake (includes aclocal as well), but I am hesistant to clobber my old ones. I installed automake and aclocal in my home directory and defined AUTOMAKE=${HOME}/bin/automake and ACLOCAL=${HOME}/bin/aclocal, but that didn't work out:

gamgee:~/Codes/blitz helenbrk$ autoreconf -fiv

autoreconf: Entering directory `.'

autoreconf: configure.ac: not using Gettext

autoreconf: running: /Users/helenbrk/bin/aclocal --force -I m4

aclocal:configure.ac:76: warning: macro `AM_DISABLE_SHARED' not found in library

autoreconf: configure.ac: tracing

autoreconf: configure.ac: not using Libtool

autoreconf: running: /usr/bin/autoconf --force

configure.ac:76: error: possibly undefined macro: AM_DISABLE_SHARED

If this token and others are legitimate, please use m4_pattern_allow.

See the Autoconf documentation.

configure.ac:77: error: possibly undefined macro: AC_PROG_LIBTOOL

autoreconf: /usr/bin/autoconf failed with exit status: 1

On May 25, 2005, at 8:18 PM, Julian Cummings wrote:

Brian,

Did installing a current version of libtool resolve the problems you were having with configuring and building blitz?

Your messages to blitz-support just showed up on the mailing list today.

Regards, Julian C.

Dr. Julian C. Cummings Office: PB-111
Caltech/CACR, MC 158-79 Phone: 626-395-2543
1200 E. California Blvd. Fax: 626-584-5917
Pasadena, CA 91125

From: blitz-support-bounces@oonumerics.org [mailto:blitz-support-bounces@oonumerics.org] On Behalf Of Brian Helenbrook
Sent: Friday, May 20, 2005 8:49 PM
To: Support list for Blitz++
Cc: Julian Cummings
Subject: [Blitz-support] cvs Build on OS X

Hello,

So far I have been using blitz on OS X and been very happy with its performance (as good as my own hand-tuned really ugly C code). It fills a giant gaping hole in C++ that has always driven me crazy. Anyway, I have two questions. The first is that I tried to post to the list, but I seem to be getting moderated... Its been about 3 days now. Any reason for that? The real question is concering building from CVS on OS X Tiger. This is the e-mail I tried to send 3 days ago:

blitz-support,

I saw in past e-mails people have gotten blitz to compile from CVS on OS X, but I can't figure it out. I am running OS X 10.4.1 (Tiger). I was able to download from cvs, and I tried autoreconf -fiv, but I ran into trouble there.

Tiger comes with autoconf --version

autoconf (GNU Autoconf) 2.59

and automake --version

automake (GNU automake) 1.6.3

Written by Tom Tromey <tromey@redhat.com>.

I upgraded automake locally to version 1.9.5, and that fixed some problems, (Before doing this I had some problem with the command "libtoolize"

Now I get the following error message:

autoreconf -fiv

autoreconf: Entering directory `.'

autoreconf: configure.ac: not using Gettext

autoreconf: running: aclocal --force -I m4

aclocal:configure.ac:76: warning: macro `AM_DISABLE_SHARED' not found in library

autoreconf: configure.ac: tracing

autoreconf: configure.ac: not using Libtool

autoreconf: running: /usr/bin/autoconf --force

configure.ac:76: error: possibly undefined macro: AM_DISABLE_SHARED

If this token and others are legitimate, please use m4_pattern_allow.

See the Autoconf documentation.

configure.ac:77: error: possibly undefined macro: AC_PROG_LIBTOOL

autoreconf: /usr/bin/autoconf failed with exit status: 1

Sorry if this had been discussed before, I couldn't find anything in the archives.

Brian

P.S. the reason I want to do this is to use the --disable-fortran configure flag