search

rishiroy1984 / graphlabapi

Automatically exported from code.google.com/p/graphlabapi
0 stars 0 forks source link

tests don't link to kyotocabinet? #34

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Building graphlab from source will fail unless I patch the CMakeLists.txt in 
the tests directory. This is pretty low priority but I figured you'd want to 
know.

What steps will reproduce the problem?
1. grab the latest version of graphlab from hg
2. grab a version of kyotocabinet (I'm using 1.2.53)
3. build and install kyotocabinet to $HOME/local
4. configure graphlab using cmake
5. build

What is the expected output? What do you see instead?

I expect graphlab to build :) But when "Linking CXX executable 
disk_graph_test.cxxtest", I get many linker errors, which seem to arise from 
kyotocabinet not being linked correctly (or at all, it seems).

graphlab *will* build if I change graphlab/graphlabapi/tests/CMakeLists.txt to 
include a line like

link_libraries(kyotocabinet)

What version of the product are you using? On what operating system?

Ubuntu 10.04 64-bit, graphlab from mercurial.
changeset:   1177:b47f83948bdf
kyotocabinet version 1.2.53

Please provide any additional information below.

gperftools and kyotocabinet are in $HOME/local, in case that's important and 
unclear from above. Everything else comes, I believe, from ubuntu's 
repositories.

Original issue reported on code.google.com by carlos.s...@gmail.com on 26 May 2011 at 5:41

GoogleCodeExporter commented 8 years ago 
For added clarification, what I meant by "configure graphlab using cmake" was 
the standard CMake idiom of

$ cd graphlababi
$ mkdir build
$ cd build
$ ccmake ..
$ make

This is different from the suggestion of using ./configure --bootstrap which 
appears in the documentation, and might account for this issue. Feel free to 
disregard my previous message if you believe that ./configure --bootstrap 
should be considered the only way of setting up CMake for graphlab.

Original comment by carlos.s...@gmail.com on 26 May 2011 at 5:47

GoogleCodeExporter commented 8 years ago 
Ah. I appear to have fixed it May 30th (changeset 597c80564405)

Original comment by yucheng...@gmail.com on 17 Jun 2011 at 6:29