Re: Arpack-ng Digest, Vol 11, Issue 3

classic Classic list List threaded Threaded
2 messages Options
Jose ALVES Jose ALVES
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Arpack-ng Digest, Vol 11, Issue 3

Hello Andrew,

Thank you very much for your answer.

Indeed you were right, I had a 32bit configuration for my project. After correcting that I no longer have the errors associated with lapack/blas libraries.

After correcting I still had the errors of "unresolved external symbol" for the arpack functions cnaupd, cneupd and smout.

(Just for information) I had to include the following modification in my test project:

Project properties -> Fortran -> External Procedures:
        Calling Convention: C, REFERENCE
        Append Underscore to External Names: Yes

Now it compiles without problems.

At execution of the .exe I get the message "Impossible to start the program because lapack.dll doesn't exist in your computer". When compiling arpack I only obtained the static libraries for blas and lapack (.lib) which are automatically linked but not the .dll... Do you know if I should then download and compile lapack and blas?? Or is there another work around??

Thank you very much for your help!!

Sincerely,

José Alves

******************************************************************
Date: Tue, 26 Jul 2016 12:40:50 -0700
From: Andrew Cunningham <[hidden email]>
To: arpack-ng mailing list <[hidden email]>,
        [hidden email]
Subject: Re: [Arpack-ng] Error during compilation of example with
        MVS2015
Message-ID:
        <CAGTJuHgYDc4ZW4Kr6SO8ZvhV=[hidden email]>
Content-Type: text/plain; charset="utf-8"

Hi Jose,
 it looks like you are trying to build a 32 bit EXE using a 64-bit arpack library. I would assume that you have no interest in 32-bit, so I would make sure you have/create a 64-bit configuration for your test project. Be careful when building your DLL. Check that 64-bit and 32-bit builds have separate destination directories so they don't step on each other. I just delete all 32-bit configurations.

Then  go to the settings for your project,  FORTRAN ->Libraries and make sure "Use Intel MKL" is turned on with appropriate settings (e.g.
Parallel). That should cause the problems with "unresolved" BLAS/LAPACK externals to go away.

Andrew



On Tue, Jul 26, 2016 at 8:03 AM, Jose ALVES <[hidden email]>
wrote:

> Hello,
>
>
>
> I have downloaded the project to do some tryouts. I opened and
> compiled the project using VS2015 with Intel Parallel Studio We2016.
>
>
>
> The project compiled without errors and I obtained the .lib .dll needed?
>
>
>
> After that I wanted to test and example case: say the file cnsimp.f;  
> For doing that I created a new project as shown below
>
>
>
>
>
> In the project ?Test-Examples? I included the library by doing as follows:
> properties -> Linker -> Input -> Additional Dependencies ->
> (PATH)\arpack-ng.lib
>
>
>
>
>
> But when compiling I get the following errors
>
>
>
> Severity
>
> Code
>
> Description
>
> Project
>
> File
>
> Line
>
> Suppression State
>
> Error
>
>
>
> error LNK2019: unresolved external symbol _CAXPY referenced in
> function _MAIN__
>
>
>
> cnsimp.obj
>
>
>
>
>
> Error
>
>
>
> error LNK2019: unresolved external symbol _CNAUPD referenced in
> function _MAIN__
>
>
>
> cnsimp.obj
>
>
>
>
>
> Error
>
>
>
> error LNK2019: unresolved external symbol _SMOUT referenced in
> function _MAIN__
>
>
>
> cnsimp.obj
>
>
>
>
>
> Error
>
>
>
> error LNK2019: unresolved external symbol _SLAPY2 referenced in
> function _MAIN__
>
>
>
> cnsimp.obj
>
>
>
>
>
> Error
>
>
>
> error LNK2019: unresolved external symbol _CNEUPD referenced in
> function _MAIN__
>
>
>
> cnsimp.obj
>
>
>
>
>
> Error
>
>
>
> error LNK2019: unresolved external symbol _SCNRM2 referenced in
> function _MAIN__
>
>
>
> cnsimp.obj
>
>
>
>
>
> Error
>
>
>
> fatal error LNK1120: 6 unresolved externals
>
>
>
> Release\Test-Examples.exe
>
>
>
>
>
> Warning
>
>
>
> warning LNK4272: library machine type 'x64' conflicts with target
> machine type 'X86'
>
>
>
> D:\Perforce\arpack-ng\VISUAL_STUDIO\Release\arpack-ng.lib
>
> 1
>
>
>
>
>
> I found that a similar question was posted here
> https://forge.scilab.org/index.php/p/arpack-ng/issues/1334/ but
> without answer.
>
>
>
> I would really appreciate if someone could give me some idea on how to
> get around this (probably) basic problem.
>
>
>
> My sincerest regards,
>
>
>
> Jos? R. Alves Z.
>
> R&D Engineer
>
> Phone : + 33(0)4 92 92 38 70
>
> Email: [hidden email]
>
>
>
> TRANSVALOR S.A.
>
> Parc de Haute Technologie
>
> 694 Avenue du Dr. Maurice Donat
>
> 06255 Mougins cedex - France
>
> Web: www.transvalor.com
>
>
>
> _______________________________________________
> Arpack-ng mailing list
> [hidden email]
> http://lists.scilab.org/mailman/listinfo/arpack-ng
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.scilab.org/pipermail/arpack-ng/attachments/20160726/7a39a9d6/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 8146 bytes
Desc: not available
URL: <http://lists.scilab.org/pipermail/arpack-ng/attachments/20160726/7a39a9d6/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 9713 bytes
Desc: not available
URL: <http://lists.scilab.org/pipermail/arpack-ng/attachments/20160726/7a39a9d6/attachment-0001.png>

------------------------------

Subject: Digest Footer

_______________________________________________
Arpack-ng mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/arpack-ng


------------------------------

End of Arpack-ng Digest, Vol 11, Issue 3
****************************************

_______________________________________________
Arpack-ng mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/arpack-ng
Andrew Cunningham Andrew Cunningham
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Arpack-ng Digest, Vol 11, Issue 3

Hi Jose,
First of all , you said you had the Intel Compiler 2016. Do you have Intel MKL? If you have Intel MKL you should be using that, not some other (likely much slower) LAPACK library.

Secondly, you probably do not have the static .lib files for LAPACK and BLAS. On Windows, to use a DLL you link against a .LIB that matches the DLL. For example LAPACK.DLL would have a matching LAPACK.LIB. It sounds like your project(s) linked against a LAPACK.LIB that goes with a LAPACK.DLL

Windows finds a .DLL by first looking in same directory as the .EXE and then looks in the system PATH.
Usually one just  puts the required DLL's in the same directory as the .EXE.

But , let me reiterate, if you have Intel MKL installed, it is much better to use Intel MKL as per my previous email.

Andrew



On Wed, Jul 27, 2016 at 5:23 AM, Jose ALVES <[hidden email]> wrote:
Hello Andrew,

Thank you very much for your answer.

Indeed you were right, I had a 32bit configuration for my project. After correcting that I no longer have the errors associated with lapack/blas libraries.

After correcting I still had the errors of "unresolved external symbol" for the arpack functions cnaupd, cneupd and smout.

(Just for information) I had to include the following modification in my test project:

Project properties -> Fortran -> External Procedures:
        Calling Convention: C, REFERENCE
        Append Underscore to External Names: Yes

Now it compiles without problems.

At execution of the .exe I get the message "Impossible to start the program because lapack.dll doesn't exist in your computer". When compiling arpack I only obtained the static libraries for blas and lapack (.lib) which are automatically linked but not the .dll... Do you know if I should then download and compile lapack and blas?? Or is there another work around??

Thank you very much for your help!!

Sincerely,

José Alves

******************************************************************
Date: Tue, 26 Jul 2016 12:40:50 -0700
From: Andrew Cunningham <[hidden email]>
To: arpack-ng mailing list <[hidden email]>,
        [hidden email]
Subject: Re: [Arpack-ng] Error during compilation of example with
        MVS2015
Message-ID:
        <CAGTJuHgYDc4ZW4Kr6SO8ZvhV=[hidden email]>
Content-Type: text/plain; charset="utf-8"

Hi Jose,
 it looks like you are trying to build a 32 bit EXE using a 64-bit arpack library. I would assume that you have no interest in 32-bit, so I would make sure you have/create a 64-bit configuration for your test project. Be careful when building your DLL. Check that 64-bit and 32-bit builds have separate destination directories so they don't step on each other. I just delete all 32-bit configurations.

Then  go to the settings for your project,  FORTRAN ->Libraries and make sure "Use Intel MKL" is turned on with appropriate settings (e.g.
Parallel). That should cause the problems with "unresolved" BLAS/LAPACK externals to go away.

Andrew




_______________________________________________
Arpack-ng mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/arpack-ng
Loading...