Puzzling error

[Matthew Knepley]

On Sat, Jul 26, 2008 at 10:40 AM, Kevin Ellwood <kellwood at ameritech.net> wrote:
> Ah.  I think I have confused you guys.  I am using the most recent version
> pf Petsc (ie. 2.3.3 p13).  I am trying to get my old code (which I made
> using 2.0.22) up and running.  I have updated most everything and I am
> trying to run for the first time.  Given what you said, I am guessing that I
> have messed up in a way the causes KSPRegisterAll and KSPRegister not to be
> called.

Okay, this can happen if somehow you configure using --with-shared or
--with-dynamic,
but then link with static libraries. Can you send configure.log to
petsc-maint? Also, the
code would help as well.

  Matt

> Thanks
> Kev
>
>
> On Sat, Jul 26, 2008 at 10:14 AM, Matthew Knepley <knepley at gmail.com> wrote:
>>
>> On Fri, Jul 25, 2008 at 8:56 PM, Kevin Ellwood <kellwood at gmail.com> wrote:
>> > Hi and thanks.  Are there any example for the usage of these calls?
>>
>> There is not really a "usage". They are supposed to be called
>> automatically
>> and you never know. However, when using ancient versions of petsc,
>> sometimes
>> things go wrong. I really encourage upgrading to the latest version.
>>
>>  Thanks,
>>
>>     Matt
>>
>> > On Fri, Jul 25, 2008 at 5:21 PM, Barry Smith <bsmith at mcs.anl.gov> wrote:
>> >>
>> >>  Kevin,
>> >>
>> >>   Make sure KSPRegisterAll() is called and that KSPRegister() is called
>> >> specifically for KSPGMRES
>> >>
>> >>   Barry
>> >>
>> >> On Jul 25, 2008, at 4:12 PM, Kevin Ellwood wrote:
>> >>
>> >>> Hi All,
>> >>>
>> >>> I am trying to resurrect an old FEM code of mine that was based on a
>> >>> very
>> >>> early version of PETSC (ie. 2.0.x).  I am go through all the changes
>> >>> and I
>> >>> am pretty sure I have some issue to get through.  However, this set of
>> >>> errors below from an early test run are puzzling me.  The relevant
>> >>> lines of
>> >>> code are shown for setting two type of solvers.  Both generate an
>> >>> error
>> >>> message indicating the Petsc can't find the KSP type once the KSPSolve
>> >>> is
>> >>> called.   It seems odd that I can get such an error since  KSPBCGS and
>> >>> KSPGMRES are define in petsc header files and can't be typos or
>> >>> miss-spellings.
>> >>>
>> >>> I know I messed up somewhere.  Does anyone have advice as to where I
>> >>> should start looking?
>> >>>
>> >>> Thanks
>> >>> Kevin
>> >>>
>> >>>
>> >>>         KSPSetType(ksp_solver,KSPBCGS);
>> >>>         ierr = KSPSolve(ksp_solver, rhs, b); CHKERRQ(ierr);
>> >>>
>> >>> [0]PETSC ERROR: --------------------- Error Message
>> >>> ------------------------------------
>> >>> [0]PETSC ERROR: Unknown type. Check for miss-spelling or missing
>> >>> external
>> >>> package needed for type!
>> >>> [0]PETSC ERROR: Unable to find requested KSP type bcgs!
>> >>>
>> >>>
>> >>>         KSPSetType(ksp_solver,KSPGMRES);
>> >>>         ierr = KSPSolve(ksp_solver, rhs, b); CHKERRQ(ierr);
>> >>>
>> >>> [0]PETSC ERROR: --------------------- Error Message
>> >>> ------------------------------------
>> >>> [0]PETSC ERROR: Unknown type. Check for miss-spelling or missing
>> >>> external
>> >>> package needed for type!
>> >>> [0]PETSC ERROR: Unable to find requested KSP type gmres!
>> >>> [0]PETSC ERROR:
>> >>>
>> >>> ------------------------------------------------------------------------
>> >>> [0]PETSC ERROR: Petsc Release Version 2.3.3, Patch 3, Fri Jun 15
>> >>> 16:51:25
>> >>> CDT 2007 HG revision: f051789beadcd36f77fb6111d20225e26ed7cc0d
>> >>>
>> >>
>> >
>> >
>>
>>
>>
>> --
>> What most experimenters take for granted before they begin their
>> experiments is infinitely more interesting than any results to which
>> their experiments lead.
>> -- Norbert Wiener
>>
>
>



-- 
What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which
their experiments lead.
-- Norbert Wiener