[petsc-dev] ugliness due to missing lapack routines

[Jed Brown]

On Thu, Feb 7, 2013 at 5:42 PM, Matthew Knepley <knepley at gmail.com> wrote:

> Hmm, it seems like the easiest thing to do is delete them if they don't
> exist.


How will you deal with headers that were determined unsafe or undesirable
to import (e.g., complex.h conflicts with hypre)? Or feature test macros?

Where does the code guarded by PETSC_HAVE_4ARG_SIGNAL_HANDLER go? What
about PETSC_HAVE_SIGINFO_T? These aren't single-line pieces of code, but
you're going to move all that stuff into generated files? How are you going
to tell the generator what to generate in all these cases? What does that
achieve?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130207/a35f7689/attachment.html>