Indeed - ill add some minimum version checking and turn off anything 
unnecessary. 

While I'm at it, what is your automake and libtool (or glibtool on the Mac) 
version?

I intend to try successively older versions until I find what is really needed.

-Ben


On Mar 5, 2012, at 1:09 PM, "John Peterson" <jwpeter...@gmail.com> wrote:

> On Mon, Mar 5, 2012 at 11:16 AM, Kirk, Benjamin (JSC-EG311)
> <benjamin.kir...@nasa.gov> wrote:
>> This coming along quite nicely I think.  My last step is to clean out the
>> Make.common definitions and then test including it in client projects.  I
>> started on that over the weekend and don't see any issues with maintaining
>> that functionality.
>> 
>> The biggest changes from the developer's perspective will be
>> 
>> (1) files must manually be added to ./Makefile.am and ./include/Makefile.am
>> (2) METHOD is now a configure-time variable.  Multiple build methods are
>> still supported and are properly installed into different paths, but must be
>> built from different directories.  For example, I handle it like this:
>> 
>> $ ./bootstrap
>> $ mkdir $METHOD
>> $ cd $METHOD
>> $ ../configure ...
>> 
>> As part of this process I have also cleaned up almost all of our M4 sources
>> for consistency and brevity.   I recognize that automake is a big
>> stepfunction in our build process, but I think this will make long-term
>> maintenance a lot easier.
>> 
>> If anyone is feeling adventurous give ^/branches/libmesh.automake a whirl:
>> 
>> $ svn co
>> https://libmesh.svn.sourceforge.net/svnroot/libmesh/branches/libmesh.automake
>> $ cd libmesh.automake
>> $ ./bootstrap
>> $ ./configure --with-method=devel --prefix=/tmp/foo
>> $ make -j 18
>> $ make -j 18 check
>> $ make install
>> $ make installcheck
>> $ make -j 18 distcheck
> 
> I suspect this could be because I have an old autotools:
> 
> $ autoconf --version
> autoconf (GNU Autoconf) 2.61
> Copyright (C) 2006 Free Software Foundation, Inc.
> 
> But I get an error when calling bootstrap
> 
> inl421321(592)$ ./bootstrap
> autoreconf: Entering directory `.'
> autoreconf: configure.ac: not using Gettext
> autoreconf: running: aclocal -I m4
> autoreconf: configure.ac: tracing
> autoreconf: running: glibtoolize --copy
> glibtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `build-aux'.
> glibtoolize: copying file `build-aux/ltmain.sh'
> glibtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
> glibtoolize: copying file `m4/libtool.m4'
> glibtoolize: copying file `m4/ltoptions.m4'
> glibtoolize: copying file `m4/ltsugar.m4'
> glibtoolize: copying file `m4/ltversion.m4'
> glibtoolize: copying file `m4/lt~obsolete.m4'
> autoreconf: running: /usr/bin/autoconf
> autoreconf: running: /usr/bin/autoheader
> autoreconf: running: automake --add-missing --copy --no-force
> configure.ac:53: option `color-tests' not recognized
> autoreconf: automake failed with exit status: 1
> 
> 
> 
> -- 
> John

------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel

Reply via email to