[petsc-dev] BuildSystem optional requirements
    Matthew Knepley 
    knepley at gmail.com
       
    Sun Jan  1 18:20:55 CST 2012
    
    
  
On Sun, Jan 1, 2012 at 6:04 PM, Matthew Knepley <knepley at gmail.com> wrote:
> On Sun, Jan 1, 2012 at 6:03 PM, Jed Brown <jedbrown at mcs.anl.gov> wrote:
>
>> On Sun, Jan 1, 2012 at 18:01, Matthew Knepley <knepley at gmail.com> wrote:
>>
>>> Make a dependency for BOTH and choose one during package configure. What
>>> else would you do?
>>
>>
>> I'm not sure I understand how you mean to implement this. Wouldn't it be
>> a failure if you have a dependency that is not satisfied? Are there any
>> examples of this, or can you just update MUMPS.py?
>>
>
> No. Does anyone fucking read the documentation, not to mention the code? I
> will look at the code.
Pushed. Is it easy for you to test?
  Matt
>   Matt
>
> --
> 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
>
-- 
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120101/542365f7/attachment.html>
    
    
More information about the petsc-dev
mailing list