<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">Hi<br><br>The petsc build was done by the ubuntu (or debian) guys. I think it may be something to do with my Makefile. I should be able to link to the *.a libs and, I am guessing, that this issue will go away. Before wasting you time, ley me look into that and I will get back to you.<br><br>Thanks for the tips.<br>Kev<br><br><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">----- Original Message ----<br>From: Matthew Knepley <knepley@gmail.com><br>To: petsc-users@mcs.anl.gov<br>Sent: Saturday, July 26, 2008 12:01:34 PM<br>Subject: Re: Puzzling error<br><br>
On Sat, Jul 26, 2008 at 10:40 AM, Kevin Ellwood <<a ymailto="mailto:kellwood@ameritech.net" href="mailto:kellwood@ameritech.net">kellwood@ameritech.net</a>> wrote:<br>> Ah. I think I have confused you guys. I am using the most recent version<br>> pf Petsc (ie. 2.3.3 p13). I am trying to get my old code (which I made<br>> using 2.0.22) up and running. I have updated most everything and I am<br>> trying to run for the first time. Given what you said, I am guessing that I<br>> have messed up in a way the causes KSPRegisterAll and KSPRegister not to be<br>> called.<br><br>Okay, this can happen if somehow you configure using --with-shared or<br>--with-dynamic,<br>but then link with static libraries. Can you send configure.log to<br>petsc-maint? Also, the<br>code would help as well.<br><br> Matt<br><br>> Thanks<br>> Kev<br>><br>><br>> On Sat, Jul 26, 2008 at 10:14 AM, Matthew Knepley
<<a ymailto="mailto:knepley@gmail.com" href="mailto:knepley@gmail.com">knepley@gmail.com</a>> wrote:<br>>><br>>> On Fri, Jul 25, 2008 at 8:56 PM, Kevin Ellwood <<a ymailto="mailto:kellwood@gmail.com" href="mailto:kellwood@gmail.com">kellwood@gmail.com</a>> wrote:<br>>> > Hi and thanks. Are there any example for the usage of these calls?<br>>><br>>> There is not really a "usage". They are supposed to be called<br>>> automatically<br>>> and you never know. However, when using ancient versions of petsc,<br>>> sometimes<br>>> things go wrong. I really encourage upgrading to the latest version.<br>>><br>>> Thanks,<br>>><br>>> Matt<br>>><br>>> > On Fri, Jul 25, 2008 at 5:21 PM, Barry Smith <<a ymailto="mailto:bsmith@mcs.anl.gov" href="mailto:bsmith@mcs.anl.gov">bsmith@mcs.anl.gov</a>> wrote:<br>>>
>><br>>> >> Kevin,<br>>> >><br>>> >> Make sure KSPRegisterAll() is called and that KSPRegister() is called<br>>> >> specifically for KSPGMRES<br>>> >><br>>> >> Barry<br>>> >><br>>> >> On Jul 25, 2008, at 4:12 PM, Kevin Ellwood wrote:<br>>> >><br>>> >>> Hi All,<br>>> >>><br>>> >>> I am trying to resurrect an old FEM code of mine that was based on a<br>>> >>> very<br>>> >>> early version of PETSC (ie. 2.0.x). I am go through all the changes<br>>> >>> and I<br>>> >>> am pretty sure I have some issue to get through. However, this set of<br>>> >>> errors below from an early test run are puzzling me. The relevant<br>>> >>> lines of<br>>> >>> code are shown for
setting two type of solvers. Both generate an<br>>> >>> error<br>>> >>> message indicating the Petsc can't find the KSP type once the KSPSolve<br>>> >>> is<br>>> >>> called. It seems odd that I can get such an error since KSPBCGS and<br>>> >>> KSPGMRES are define in petsc header files and can't be typos or<br>>> >>> miss-spellings.<br>>> >>><br>>> >>> I know I messed up somewhere. Does anyone have advice as to where I<br>>> >>> should start looking?<br>>> >>><br>>> >>> Thanks<br>>> >>> Kevin<br>>> >>><br>>> >>><br>>> >>> KSPSetType(ksp_solver,KSPBCGS);<br>>> >>> ierr = KSPSolve(ksp_solver, rhs, b); CHKERRQ(ierr);<br>>>
>>><br>>> >>> [0]PETSC ERROR: --------------------- Error Message<br>>> >>> ------------------------------------<br>>> >>> [0]PETSC ERROR: Unknown type. Check for miss-spelling or missing<br>>> >>> external<br>>> >>> package needed for type!<br>>> >>> [0]PETSC ERROR: Unable to find requested KSP type bcgs!<br>>> >>><br>>> >>><br>>> >>> KSPSetType(ksp_solver,KSPGMRES);<br>>> >>> ierr = KSPSolve(ksp_solver, rhs, b); CHKERRQ(ierr);<br>>> >>><br>>> >>> [0]PETSC ERROR: --------------------- Error Message<br>>> >>> ------------------------------------<br>>> >>> [0]PETSC ERROR: Unknown type. Check for miss-spelling or missing<br>>> >>> external<br>>> >>>
package needed for type!<br>>> >>> [0]PETSC ERROR: Unable to find requested KSP type gmres!<br>>> >>> [0]PETSC ERROR:<br>>> >>><br>>> >>> ------------------------------------------------------------------------<br>>> >>> [0]PETSC ERROR: Petsc Release Version 2.3.3, Patch 3, Fri Jun 15<br>>> >>> 16:51:25<br>>> >>> CDT 2007 HG revision: f051789beadcd36f77fb6111d20225e26ed7cc0d<br>>> >>><br>>> >><br>>> ><br>>> ><br>>><br>>><br>>><br>>> --<br>>> What most experimenters take for granted before they begin their<br>>> experiments is infinitely more interesting than any results to which<br>>> their experiments lead.<br>>> -- Norbert Wiener<br>>><br>><br>><br><br><br><br>-- <br>What most experimenters take for granted before they begin their<br>experiments
is infinitely more interesting than any results to which<br>their experiments lead.<br>-- Norbert Wiener<br><br></div></div></div></body></html>