[petsc-users] [petsc-dev] second patch for DMDAVecGetArrayF90

[Matthew Knepley]

On Wed, Jul 11, 2012 at 3:44 PM, TAY wee-beng <zonexo at gmail.com> wrote:

>  On 11/7/2012 8:10 PM, Satish Balay wrote:
>
> On Wed, 11 Jul 2012, TAY wee-beng wrote:
>
>
>  I just tried on a different system and the same error occurs. The 1st command
> :
> /
> /
>
> /patch -Np1 -R < DMDAVecRestoreArrayF90-2.patch
>
> $ patch -Np1 -R < DMDAVecRestoreArrayF90-2.patch
> (Stripping trailing CRs from patch.)
> patching file src/dm/impls/da/f90-custom/zda1f90.c
> (Stripping trailing CRs from patch.)
> patching file src/sys/f90-src/f90_cwrap.c
> (Stripping trailing CRs from patch.)
> patching file src/sys/f90-src/fsrc/f90_fwrap.F/
>
> works but the 2nd one doesn't:
> /
> $ patch -Np1  < DMDAVecRestoreArrayF90-2.1.patch
> (Stripping trailing CRs from patch.)
> patching file src/dm/impls/da/f90-custom/zda1f90.c
> Hunk #1 FAILED at 175.
> 1 out of 1 hunk FAILED -- saving rejects to file
> src/dm/impls/da/f90-custom/zda1f90.c.rej
> (Stripping trailing CRs from patch.)
> patching file src/sys/f90-src/f90_cwrap.c
> Hunk #1 FAILED at 307.
> Hunk #2 FAILED at 333.
> Hunk #3 FAILED at 436.
> 3 out of 3 hunks FAILED -- saving rejects to file
> src/sys/f90-src/f90_cwrap.c.rej
> (Stripping trailing CRs from patch.)
> patching file src/sys/f90-src/fsrc/f90_fwrap.F
> Hunk #1 FAILED at 322.
> Hunk #2 FAILED at 426.
> 2 out of 2 hunks FAILED -- saving rejects to file
> src/sys/f90-src/fsrc/f90_fwrap.F.rej/
>
>
> It is possible to send me the 3 patch files? Or is there some other ways?
>
>  This doesn't make any sense. What petsc-dev do you have? Is it hg
> repo? or something else?  What revisions? Are the sources locally
> modified?
>
> You can apply DMDAVecRestoreArrayF90-2.patch and then edit
> src/sys/f90-src/f90_cwrap.c and replace all occurances of 'F90ARRAY4d'
> with 'F90ARRAY4D' in the editor to get the same effect.
>
> Satish
>
>
> I just tried but the same error occurs:
> *
> 1>D:\Lib\petsc-3.3-dev_win32_vs2008/include/finclude/ftn-custom/petscdmcomposite.h90(8):
> warning #6717: This name has not been given an explicit type.   [D1]
> 1>Linking...
> 1>libpetsc.lib(f90_cwrap.o) : error LNK2019: unresolved external symbol
> F90ARRAY4dCREATESCALAR referenced in function F90Array4dCreate
> 1>libpetsc.lib(f90_cwrap.o) : error LNK2019: unresolved external symbol
> F90ARRAY4dACCESSFORTRANADDR referenced in function F90Array4dAccess
> 1>libpetsc.lib(f90_cwrap.o) : error LNK2019: unresolved external symbol
> F90ARRAY4dACCESSINT referenced in function F90Array4dAccess
> 1>libpetsc.lib(f90_cwrap.o) : error LNK2019: unresolved external symbol
> F90ARRAY4dACCESSREAL referenced in function F90Array4dAccess
> 1>libpetsc.lib(f90_cwrap.o) : error LNK2019: unresolved external symbol
> F90ARRAY4dACCESSSCALAR referenced in function F90Array4dAccess
> 1>libpetsc.lib(f90_cwrap.o) : error LNK2019: unresolved external symbol
> F90ARRAY4dDESTROYSCALAR referenced in function F90Array4dDestroy
> 1>c:\obj_tmp\dm_test2d\Debug/dm_test2d.exe : fatal error LNK1120: 6
> unresolved externals
> 1>
> 1>Build log written to  "file://c:\obj_tmp\dm_test2d\Debug\BuildLog.htm"*
>
> Any other solutions?
>

Look, if this stuff is not done systematically, if you do not know exactly
what
version of the code you have, and how to build, then it just generates an
endless
stream of emails without any progress.

If you have a link error, unresolved symbol, it means it can't find the
symbol in the library. Did you

  a) Look for the symbol in the library using nm?

  b) Check the build log (make.log) to see that all files built correctly?

  c) Check the source file for this function?

   Matt

-- 
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20120711/4183179c/attachment-0001.html>