On Thu, Dec 05, 2002 at 03:45:57PM -0800, mikel evins wrote: > > On Thursday, December 5, 2002, at 03:31 PM, Nicholas Riley wrote: > > > >>> > >>>Did you rerun libtoolize/aclocal/autoconf? This should happen > >>>automatically when you run configure, at least the second half of it, > >>>but it may not have. > >>> > >> > >>Tried it; same result. > > > >Can you post your entire build log somewhere? > > Do you just want me to pipe the build output to a file or is a log > constructed in the filetree somewhere in the normal course of things? > > In order to save one potential trouble, is there implicit a more > complicated set of instructions for running libtoolize/aclocal/autoconf > than simply executing them simple-mindedly in the unix subdir?
To really be sure, here's what I generally do: % rm aclocal.m4 % rm -rf autom4te.cache % glibtoolize --copy --force % aclocal % autoconf If any of those give error messages such as missing macros, then something is probably wrong. Make sure that the versions of autoconf/automake and libtool running are all configured to work with one another - i.e., if you're using glibtool from Fink, then the other two should be from there too. The reason for this is that there are a lot of interdependencies between the packages and some item can be out of date but still appear to work at the auto* stage, but fail on configure/make. I went through about three hours of pain a few days ago trying to get Metakit to compile on Linux until I figured out that they weren't all using the same m4 directories. -- =Nicholas Riley <[EMAIL PROTECTED]> | <http://www.uiuc.edu/ph/www/njriley> Pablo Research Group, Department of Computer Science and Medical Scholars Program, University of Illinois at Urbana-Champaign _______________________________________________ metakit mailing list - [EMAIL PROTECTED] http://www.equi4.com/mailman/listinfo/metakit
