[petsc-dev] still relevant in ./configure help ? Should Matt remove them?
Matthew Knepley
knepley at gmail.com
Tue Dec 26 08:49:58 CST 2017
On Mon, Dec 25, 2017 at 10:19 PM, Smith, Barry F. <bsmith at mcs.anl.gov>
wrote:
>
>
> > On Dec 25, 2017, at 8:08 PM, Balay, Satish <balay at mcs.anl.gov> wrote:
> >
> > On Mon, 25 Dec 2017, Smith, Barry F. wrote:
> >
> >>
> >> --with-autoreconf=<prog>
> >> Specify autoreconf current: autoreconf
> >> --with-libtoolize=<prog>
> >> Specify libtoolize current: libtoolize
> >
> > Well I think configure uses autoreconf and libtoolize for packages
> > that it downloads via git - and then needs to build its
> > configure script. [for eg: MOAB]
> >
> > And if petsc configure needs these tools - it should provide a way for
> > user to specify them [i.e override configure default guesses]
>
> Ah, ok.
This sounds to me like the reason we have Christmas trees. The old gods
must be appeased ;)
Matt
> >
> > Satish
> >
> >>
> >>
> >> --with-alternatives=<bool>
> >> Provide a choice among alternative package installations
> current: 0
> >>
> >>
> >>
> >
>
>
--
What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which their
experiments lead.
-- Norbert Wiener
https://www.cse.buffalo.edu/~knepley/ <http://www.caam.rice.edu/~mk51/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20171226/7b789c49/attachment.html>
More information about the petsc-dev
mailing list