PIC

[Satish Balay]

Barry,

I'm attaching the relavent logfiles for this failure case. Looks like
there is an exception raised for this case - so I can trap it in
MPI.py - and error out. [other case returns a '0' - which is ok for
PETSc sharedlibs]

So with this change to MPI.py, configure give a nice error message:

*********************************************************************************
         UNABLE to CONFIGURE with GIVEN OPTIONS    (see configure.log for details):
---------------------------------------------------------------------------------------
PETSc shared libraries cannot be built using MPI provided.
Either rebuild PETSc with --with-shared=0 or rebuild MPI with shared library support
*********************************************************************************

I'll push this change.

Satish


On Wed, 14 Dec 2005, Barry Smith wrote:

> 
> >   This also succeeds, unless I misunderstand greatly the error.
> 
>   The libraries get built, fine. Now you generate the executable.
> That FAILS! As I have been saying all the time! It fails NOT
> because the library is not shared but because one cannot use
> that library WITH shared libraries!
> 
>   The new test is suppose to check that it can link and generate
> the executable, BUT not run the executable to see what message
> you get.
> 
>   The new test could be called checkCanBeUsedWithSharedLibrary() and
> it would shared almost all the code with checkShared() except actually
> running the executable and checking the result.
> 
>   Is it clear now, or am I still messed up?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: configure.log
Type: application/octet-stream
Size: 965413 bytes
Desc: 
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20051215/22df36a5/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: make_log_linux-gnu-c-real-debug
Type: application/octet-stream
Size: 34839 bytes
Desc: 
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20051215/22df36a5/attachment-0001.obj>