[petsc-dev] [petsc-maint #42769] Test Examples

[Barry Smith]

    Currently ./configure does not test that Fortran/C work together.  
It only checks that links between the two succeed.

    Do we need a "run" example that would detect the [64bit D.I is  
incomatible with C] issue? Or another kind of test?


    Barry

On Mar 5, 2010, at 10:00 PM, Satish Balay wrote:

> g95 should also work.
>
> One potential problem is: using 'Linux x86_64/EMT64 (64 bit D.I.)'
> instead of 'Linux x86_64/EMT64 (32 bit D.I.)'
>
> [64bit D.I is incomatible with C]
>
> Satish
>
> On Fri, 5 Mar 2010, Barry Smith wrote:
>
>>
>>   I suspect that the g95 does not work with the gcc.
>>
>>    We now always recommend using gfortran instead of g95 because it
>> is part of the GNU compiler suite and automatically works properly
>> with gcc.
>>
>>    Barry
>>
>> On Mar 5, 2010, at 6:01 PM, Arensman, Will L. wrote:
>>
>>> Good Evening,
>>>
>>> I've run into a problem getting the PETSC tests to run when PETSC is
>>> build
>>> in conjuction with g95. Make test results in this error:
>>>
>>> Error running Fortran example src/snes/examples/tutorials/ex5f with
>>> 1 MPI
>>> process
>>> See http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html
>>> [0]PETSC ERROR:
>>> ------------------------------------------------------------------------
>>> [0]PETSC ERROR: Caught signal number 11 SEGV: Segmentation  
>>> Violation,
>>> probably memory access out of range
>>> [0]PETSC ERROR: Try option -start_in_debugger or -
>>> on_error_attach_debugger
>>> [0]PETSC ERROR: or see
>>> http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Sig
>>> nal[0]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple
>>> Mac OS
>>> X to find memory corruption errors
>>>
>>> I've looked through the documentation and haven't found anything
>>> that looks
>>> quite like this. I am including the configure log, the make log, and
>>> also
>>> the complete output when make test is run.
>>>
>>> -Machine type: (e.g., sun4)
>>> Ordinary Linux server.
>>>
>>> -OS Version: (run uname -a to get the version number)
>>> Linux katana.cnwra.swri.edu 2.6.18-8.el5 #1 SMP Fri Jan 26 14:15:14
>>> EST 2007
>>> x86_64 x86_64 x86_64 GNU/Linux
>>>
>>> -PETSc Version: (run PETSc program with -v, or look in
>>> include/petscversion.h)
>>> petsc-dev downloaded using Mercurial on 3/5/2010.
>>>
>>> -MPI implementation: (e.g., MPICH, LAM, IBM, SGI)
>>> OpenMPI downloaded using "--download-openmpi=1".
>>>
>>> -Compiler: (e.g., Gnu C, Gnu g++, native C)
>>> Using gcc and g95.
>>>
>>> -Probable PETSc component: (for example, Mat, Vec, Draw, KSP, etc.)
>>> Not sure.
>>>
>>> Any advice is appreciated. Thanks!
>>>
>>> Will Arensman
>>> Senior Research Analyst
>>> Southwest Research Institute
>>> 210.522.3151
>>>
>>> <configure.log><make.log><make_test_log.txt><smime.p7s>
>>
>>
>>
>