I'll address this with 'maintainer mode', so no one panic...



On Nov 17, 2012, at 4:06 PM, "Kirk, Benjamin (JSC-EG311)" <benjamin.kirk-1@nasa.gov> wrote:

In the meantime try my latest bootstrap though and see if it works on your machine. 

On Nov 17, 2012, at 3:33 PM, "Kirk, Benjamin (JSC-EG311)" <benjamin.kirk-1@nasa.gov> wrote:

The problem is I cannot control the date stamps yet - ill work on it. I bet the date on your configure.ac is newer than the configure I checked in, so it is rightly trying to regenerate itself?

-Ben



On Nov 17, 2012, at 3:23 PM, "Derek Gaston" <friedmud@gmail.com> wrote:

I just tried out the configure that is checked in... and everything seemed to go well.

However, a "make" produces:

CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh /Users/gastdr/projects/libmesh/build-aux/missing --run aclocal-1.12 -I m4
/Users/gastdr/projects/libmesh/build-aux/missing: line 51: aclocal-1.12: command not found
WARNING: 'aclocal-1.12' is missing on your system.  You should only need it if
         you modified 'acinclude.m4' or 'configure.ac'.  You might want
         to install the Automake and Perl packages.  Grab them from
         any GNU archive site.
CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh /Users/gastdr/projects/libmesh/build-aux/missing --run autoconf
configure.ac:59: error: possibly undefined macro: AM_INIT_AUTOMAKE
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.ac:71: error: possibly undefined macro: AM_CONDITIONAL
make: *** [configure] Error 1


On Sat, Nov 17, 2012 at 1:17 PM, Derek Gaston <friedmud@gmail.com> wrote:
Sounds good Ben!

We'll see how this evolves over time.  If it's a problem having it in
the repo we can remove it later.

Derek

Sent from my iPhone

On Nov 17, 2012, at 11:23 AM, "Kirk, Benjamin (JSC-EG311)"
<benjamin.kirk-1@nasa.gov> wrote:

> I'm updating bootstrap now, if we are going to check in generated files I'm going to be really pedantic about only allowing one to generate a file with the newest version of everything.
>
> Then I'll add the generated files.
>
> -Ben
>
>
>
>
> On Nov 17, 2012, at 11:42 AM, "Roy Stogner" <roystgnr@ices.utexas.edu> wrote:
>
>>
>> On Sat, 17 Nov 2012, Derek Gaston wrote:
>>
>>> So I'm only going to argue for configure in the repo one more time.
>>
>> For what it's worth, I generally *despise* putting intermediate,
>> generated files in svn repositories.  The PECOS svn tree log is
>> littered with entries that are nothing more than roystgnr is svn
>> removing other users' regeneratable files the way Rain Man picks up
>> toothpicks.
>>
>> I count configure in the "stuff to get out of the repo" category, in
>> an environment like PECOS where professional IT people (or Paul or me,
>> at least) are making sure that everyone has access to a tested recent
>> autotools version.
>>
>> But in a publically-available project?  Let's make an exception.
>>
>> Until we start auto-tarring nightly releases or doing something
>> similar to give users a minimal-dependencies way to build a recent
>> libMesh, let's leave a pre-built configure in svn.
>> ---
>> Roy