Yes, I do. I was just writing to you to ask what sort of details do you need to
find out the problem. ;)

I can provide my current CMakeCache with the working parameters and which
libraries I installed on my system to make the linker work.

Do I need to open an issue on Github?

Giovanni

P.S: I renamed the mail subject since the discussion moved on another topic. Does this list have an archive?

On 27/01/2017 17:38, Heiko Strathmann wrote:
You  want to go ahead, Giovanni?
We would need instructions how to reproduce this

2017-01-27 8:47 GMT+00:00 Viktor Gal <[email protected]>:
i reckon we should create an issue for this, because as i suspect there’s 
something wrong with our atlas detection module for cmake.

cheers,
viktor

On 27 Jan 2017, at 4:31 PM, Giovanni De Toni <[email protected]> wrote:

Good news! I am finally able to build shogun without the linker errors.
To make things work I removed the ATLAS libraries and I installed only the
libblas and liblapack packages.

To be honest, I don't understand why this setup is working and
the previous does not, since ATLAS also provides its custom libblas/liblapack 
files.

Thank you very much for all the help!

Giovanni

On 26/01/2017 21:43, Heiko Strathmann wrote:
No, please dont do that...it will take a lot of time and not help you
sorting out the problem.

You need to check if the libraries in your LD path contain the symbols
that the linker moans about...
There have been some problems with ATLAS in the past, that is why we
had this additional switch.
Björn knows about this I think...

2017-01-26 12:05 GMT+00:00 Giovanni De Toni
<[email protected]>
:

As suggested, I used ccmake to check the correctness of the library paths.
It seems that cmake detects correctly the location of
libblas/libatlas/liblapack,
but it still gives linker errors (I also tried to manually add the paths to
LD_LIBRARY_PATH).

It feels strange to me, because I installed all the packages through
apt-get.
I would have been less surprised to get these errors if I had compiled and
installed
all these packages by myself.

I will try to build everything again on a clean separate machine to see if
it gets better.

Giovanni


On 25/01/2017 12:17, Heiko Strathmann wrote:

This is a faulty setup. These things should be in your LD_LIBRARY_PATH.
Maybe cmake detected them wrong? We also have manual options to set
that (try ccmake), and also a special option for ATLAS.
H

2017-01-24 21:35 GMT+00:00 Giovanni De Toni
<[email protected]>
:

Hi,

the latest commits solved my issue. I am now able to compile
all the meta examples (except those which require the LAPACK library).

However, for curiosity's sake, I tried to compile everything after
installing
the ATLAS library (that includes also LAPACK and BLAS). The cmake
configuration goes well,
but when I try to compile the cpp meta examples or the shogun unit tests
the
linker complains
that it cannot find some symbols (for example, dsyev_, dorgqr_ etc.).

Here the gist with the complete errors:

https://gist.github.com/geektoni/9ec823a1b05085f33f0c561053a705a9


Is there a way to fix it? Thanks for the help!

Giovanni


On 23/01/2017 17:18, Heiko Strathmann wrote:

Hi!

That will be unmet dependencies that are not clearly handled in our
build.
The latest merge should solve the CMahalanobisDistance problem.

Let us know how things go

2017-01-21 10:26 GMT+00:00 Giovanni De Toni
<[email protected]>
:

Hello everybody,

I am a computer science undergraduate student from Italy. Recently, I got
interested in the Shogun Project and I have begun to "play" with the
code,
to understand its structure and its internal logics.

Unfortunately, I encountered some problem when compiling the cpp meta
examples.

Specifically, I get compilation errors on the file
examples/meta/cpp/distance/mahalanobis.cpp.
You can find the complete message at this link:

https://gist.github.com/geektoni/29c8cad970478b834e353348a0431130

I have also tried to compile it manually but it gave me the same result.

I am on Ubuntu 16.04 and I have set up cmake with these flags:
-DBUILD_META_EXAMPLES=ON -DENABLE_TESTING=ON
(my gcc version is 4.9.3).

Am I missing something? Perhaps some configuration parameters?
Thank you in advance for the help!

Best regards,
Giovanni





Reply via email to