lapackpp-devel

[Lapackpp-devel] Re: again about the lapackpp

[Christian S. <sti...@tu...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Arash Noorghorbani schrieb:
> Then I add all header files of SDK to Projects
> and also add 4 dll of the first installation () to the projects and then 
> I get this error:  for 'libg2c.a'
> 
> ------ Build started: Project: lapackpp, Configuration: Debug Win32 ------
> (...)
> Compiling resources...
> Creating library...
> LIB : fatal error LNK1181: cannot open input file 'libg2c.a'
> Build log was saved at "file://d:\WORK\lapackpp-2.4.9\Debug\BuildLog.htm"
> lapackpp - 1 error(s), 1 warning(s)

Are you not quite familiar with the compiler? If you say in the Linker
tab of the preferences that libg2c.a is an input file to the linker,
then you need to put that file into a place that will be used by the
linker, e.g. d:\WORK\lapackpp-2.4.9\ .

> ------ Build started: Project: tGenSolve, Configuration: Debug Win32 ------
> Compiling...
> (...)
> Linking...
> LINK : fatal error LNK1181: cannot open input file 'lapackpp.lib'
> Build log was saved at
> "file://d:\WORK\lapackpp-2.4.9\testing\Debug\BuildLog.htm"
> tGenSolve - 1 error(s), 0 warning(s)

Of course the tGenSolve project cannot open the file lapackpp.lib --
this will only be generated if the lapackpp project (the first one,
above) finishes successfully, which it doesn't do so far.

Christian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQCVAwUBRGsB5WXAi+BfhivFAQI5OwQAreQrA4Vkbm2DxuXYs9Z1TUmeFZD+puXw
bdE+efulZWpo5nx5SRYdrSR972xor7Qs4dfx02V/Tv7AD/SYfPsO1vdoQxmCtIcU
Ng7zIIsKw+Q6j3I7PugYxqTlbVcYk9c67qzT41Vq/XL/iSlRfC8+elVm2Kdz1eE2
5SgL9m1/j5s=
=I32A
-----END PGP SIGNATURE-----

[Lapackpp-devel] Re: again about the lapackpp

[Christian S. <sti...@tu...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Arash Noorghorbani schrieb:
> I did not good understand one of your latest email, that you said to me 
> that prepare an upload link for libg2c.a and so I did not have it.
> 
> Now I download it and ..., But Now it need 'libgcc.a'!
> ________________________________________________________________
> LIB : fatal error LNK1181: cannot open input file 'libgcc.a'
> ________________________________________________________________
> 
> Am I install mingw32_gcc_forteran or not?

No. You have to edit the "Linker" input setting of the lapackpp project.
Click "Properties", then "Linker", then "Input" and in the topmost line
you see the input libraries. Remove the libgcc.a from that line.

I can help with lapackpp-related problems, but I cannot teach you how to
use your compiler. Sorry for that.

Christian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQCVAwUBRGsqm2XAi+BfhivFAQLTcAQArF3QGM//0AVgqFs0jcvd08lSj5rzDKoH
w3t2oy66xK//eT7fM+R1CczYyUT69tFleN84P/I/LGaLQpCbpAAP5XQwUfvucYOb
6Hbe0iojKpaz8iqXzbNWJ2A5vG2KXaRzypyPZKQ6f/s2vV10iZIg6UAxjNjVG608
tF4f6qcN9Fs=
=I/qp
-----END PGP SIGNATURE-----

[Lapackpp-devel] Re: again about the lapackpp

[Christian S. <sti...@tu...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Arash Noorghorbani schrieb:
> I think that this source need to "libgcc.a", that's why I asked you.
> By your advise, I do what you say. But there is one problem now:
> It seems that for compile twice use  form 'liblapack32.dll' , first time
> is ok, BUT for the second time, it said cannot open!!
> 
> ------ Build started: Project: lapackpp, Configuration: Debug Win32 ------
> ...
> Build log was saved at "file://d:\WORK\lapackpp-2.4.9\Debug\BuildLog.htm"
> lapackpp - 0 error(s), 8 warning(s)

so the lapackpp.dll library now compiled without errors. That's at least
something.

> ------ Build started: Project: tGenSolve, Configuration: Debug Win32
> Compiling...
> Linking...
> LINK : fatal error LNK1181: cannot open input file 'liblapack32.dll'

I'm sorry; it turns out the project file in lapackpp-2.4.9 cannot build
an actual DLL of lapackpp. I've just released a version lapackpp-2.4.10
that will now build an actual DLL. You will need a libblas32.lib and
liblapack32.lib for that, but this is (already) contained in the
setup.exe of 2.4.9 in "Program files\lapackpp\lib".  But you won't need
libg2c.a or libgcc.a anymore.

It is up to you to adapt the linker input directory accordingly, but
apart from that, the vcproj file in 2.4.10 should now work without
further problems.

Christian

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQCVAwUBRGtAMmXAi+BfhivFAQIjQQP8DxRZR1ur5yNUKbhkW+8F+m1aUIsDycb4
6iQnipbJp+S3lNhkI6P03H7CutCPBO2hLJ9KwQQNGn0k9ayr59baKvN3LmaEcd4q
h5/Bm9/bkFI++h4nLGLi+1YBrl1HIHmiqSJb1VXTgfEyVVfTGwjVpsAbqZ/NMHKS
P9xR6+7hcKE=
=yqIm
-----END PGP SIGNATURE-----