[petsc-dev] Some problems with builds --with-matlab

[Jose E. Roman]

El 07/03/2013, a las 01:33, Barry Smith escribió:

> 
>  Fixed both 767347ff803d   I believe

Yes, thanks. However I get warnings in the definition of PetscBeganMPI, PetscInitializedCalled and PetscFinalizedCalled. I pushed a fix. Feel free to revert.

> 
> On Mar 6, 2013, at 11:00 AM, "Jose E. Roman" <jroman at dsic.upv.es> wrote:
> 
>> Hi.
>> 
>> Today I pushed some fixes for compilation --with-matlab --with-matlab-engine. However, there is still a compilation problem when Fortran in enabled: the automatic Fortran bindings in src/sys/classes/matlabengine need the definition of PetscMatlabEngine. I tried adding /*I "petscmatlab.h" I*/ in matlab.c but that does not work.
> 
>   This is the right fix and worked for me. Did you rerun make allfortranstubs?

I reran configure and the file was regenerated. I must have made something wrong.

Jose

> 
>   Barry
> 
>> 
>> The other problem is related to the visibility topic discussed in another thread. In SLEPc we have SlepcInitializeNoPointers() to be called from Matlab. There I set PetscBeganMPI = PETSC_FALSE (as is done in PetscInitializeNoPointers()) because otherwise I get PetscFinalize() errors the second time I run a Matlab script containing SLEPc calls. So the symbol PetscBeganMPI should be exported (unless you can suggest a better solution).
>> 
>> Jose
>> 
>