On Fri, 26 Feb 2016, Kirk, Benjamin (JSC-EG311) wrote:
On Feb 26, 2016, at 2:05 PM, John Peterson wrote:
> Yeah, we should do this I think. Then just devs (and only devs
> that change m4 files) need to change their build scripts to add
> --enable-maintaner-mode, otherwise changes to th
On Feb 26, 2016, at 2:05 PM, John Peterson
mailto:jwpeter...@gmail.com>> wrote:
Yeah, we should do this I think. Then just devs (and only devs that change m4
files) need to change their build scripts to add --enable-maintaner-mode,
otherwise changes to the autoconf files don't trigger Makefile
> On Feb 26, 2016, at 12:54 PM, Boyce Griffith wrote:
>
> It is possible to configure configure so that maintainer mode needs to be
> enabled explicitly (by passing --enable-maintainer-mode):
>
> AM_MAINTAINER_MODE([disable])
>
Yeah, we should do this I think. Then just devs (and only devs
Yes, but that has downsides I at least consider to more severe, such as
forgetting the configure option will cause Makefile.ins never to get recreated
from Makefile.ams. And silently too, which is worse.
The convenient fix is
./bootstrap --build-autotools
And then make sure your path contains
It is possible to configure configure so that maintainer mode needs to be
enabled explicitly (by passing --enable-maintainer-mode):
AM_MAINTAINER_MODE([disable])
-- Boyce
> On Feb 26, 2016, at 2:29 PM, Derek Gaston wrote:
>
> That did it Cody - thanks!
>
> I will, of course, use this to poin
That did it Cody - thanks!
I will, of course, use this to point out that the current behavior should
not be the default. Any new user/developer that comes along and tries to
build libMesh for the first time and immediately gets a crazy error like
this will just immediately delete libMesh and move
