Dima,
> 1)
> The FAQs link is dead, the link
> http://www-dimat.unipv.it/heltai/wikideal/index.php/Deal.II_Questions_an
>d_Answers at page
> http://www.dealii.org/developer/readme.html#optional-software
Yes, one of Luca Heltai's servers crashed and some data was lost. I don't
know what the current status is, though...
> 2) In "configure.in", looks like that the configuration process will
> issue the message "Parser was disabled" regardless of the
> option that was passed to the "--enable-parser=...". Order of
> commands there is wrong (in "configure.in", in the block
> defining this behaviour ).
I don't know. AC_ARG_ENABLE is sorta stupid: it takes a list of commands
for when the flag is given on the command line, and one list of commands
when the flag is not given on the command line. But it always calls the
first list independent of whether --enable-parser or --disable-parser was
given -- I actually don't know how exactly this is supposed to work, I
find it very confusing and I don't know how one is supposed to distinguish
between --enable-parser and --disable-parser.
Here's the manual:
---------------------------------
-- Macro: AC_ARG_ENABLE (FEATURE, HELP-STRING, [ACTION-IF-GIVEN],
[ACTION-IF-NOT-GIVEN])
If the user gave `configure' the option `--enable-FEATURE' or
`--disable-FEATURE', run shell commands ACTION-IF-GIVEN. If
neither option was given, run shell commands ACTION-IF-NOT-GIVEN.
The name FEATURE indicates an optional user-level facility. It
should consist only of alphanumeric characters, dashes, and dots.
The option's argument is available to the shell commands
ACTION-IF-GIVEN in the shell variable `enableval', which is
actually just the value of the shell variable `enable_FEATURE',
with any non-alphanumeric characters changed into `_'. You may
use that variable instead, if you wish. The HELP-STRING argument
is like that of `AC_ARG_WITH' (*note External Software::).
-------------------------------
So, yes, whenever you give --enable-parser on the command line, it will
actually disable the parser. What we intended with this is that by default
people don't give anything at all on the command line, which enables the
parser.
I agree that this is stupid. Do you have any suggestions on how to improve
the situation?
> 3) Is there a reason that in "common/scripts/Makefile" the
> "make_dependencies" is compiled in optimized mode and
> "extract_instantiations" in debug mode?
No, that's a bug. Thanks for pointing it out, I just checked in a patch for
this.
> 4) PETSc - It passed quite a long time since I compiled
> PETSc with DEAL.II, I need a reminder -- is C++ or C interface
> of PETSc is used ?
I didn't actually know that it has a C++ interface. We only always call C
functions, but if I remember this correctly we just
#include <petsc.h>
and so if that file does not contain something like
extern "C" { ... }
then you need to compile with a C++ compiler. Indeed, one has to configure
PETSc with --with-cxx (or a similar spelling).
Best
Wolfgang
--
-------------------------------------------------------------------------
Wolfgang Bangerth email: [EMAIL PROTECTED]
www: http://www.math.tamu.edu/~bangerth/
_______________________________________________
