Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installation Problems on Ubuntu 16.04.1 LTS #298

Closed
ilkerkesen opened this issue Feb 11, 2017 · 9 comments
Closed

Installation Problems on Ubuntu 16.04.1 LTS #298

ilkerkesen opened this issue Feb 11, 2017 · 9 comments
Labels
moderate bug Issues that should be fixed but only affect less common environments or functionality

Comments

@ilkerkesen
Copy link

ilkerkesen commented Feb 11, 2017

Hi all,

I am trying to install DyNet on Ubuntu 16.04.1 LTS by following instructions on the official documentation. However, I am facing with some problems. Thanks to this issue, I was able to setup DyNet on my server. However, when I try to run the example mentioned in the docs, I get a Segmentation Fault (core dumped) error. I'm using the current master branch.

There it is, how I created Makefile:

CC=gcc-4.9 CXX=g++-5 cmake .. -DEIGEN3_INCLUDE_DIR=/usr/local/include/eigen3 -DBACKEND=cuda -DBOOST_ROOT:PATHNAME=/usr/include/boost -DBoost_LIBRARY_DIRS:FILEPATH=/usr/lib/x86_64-linux-gnu -DBoost_NO_BOOST_CMAKE=TRUE -DBoost_NO_SYSTEM_PATHS=TRUE -DPYTHON=which python`

This gist includes make.log file and train_xor example output:

https://gist.github.com/ilkerkesen/f3a13def6c9088ba9338cbd105d1bc7e

I checked the other examples and they all ended up with a segmentation fault. Thanks in advance.

@neubig
Copy link
Contributor

neubig commented Feb 12, 2017

It looks like @pmichel31415 also complained of segfaults in the upstream issue, so maybe this is the same problem? If so, it would be very nice to get this resolved.

@neubig
Copy link
Contributor

neubig commented Feb 15, 2017

Is this the same problem as upstream having two versions of boost installed?
#282

@ilkerkesen
Copy link
Author

Sorry for the late response. I don't think this is the same problem, because I couldn't have find libboost in the paths you mentioned. I just followed the installation guide and installed libboost via apt. My libboost version is 1.58.0.

@neubig
Copy link
Contributor

neubig commented Feb 20, 2017

@ilkerkesen OK, could you please remove the CC=gcc-4.9 CXX=g++-5 variable declaration, and do a clean build following these instructions?

http://dynet.readthedocs.io/en/latest/install.html#debugging-build-problems

If you can send the make.log file we might be able to debug your original problem.

@ilkerkesen
Copy link
Author

Here is the new make log. Thanks a lot for your concern.

@neubig
Copy link
Contributor

neubig commented Feb 20, 2017

Hmm, I still strongly suspect that you have two different versions of boost installed on your machine. Does DyNet compile without any of the Boost flags? Try removing -DBOOST_ROOT:PATHNAME=/usr/include/boost -DBoost_LIBRARY_DIRS:FILEPATH=/usr/lib/x86_64-linux-gnu -DBoost_NO_BOOST_CMAKE=TRUE -DBoost_NO_SYSTEM_PATHS=TRUE and see if compilation works.

@ilkerkesen
Copy link
Author

ilkerkesen commented Feb 20, 2017

I've just updated the gist. Still I've a compilation error.

@neubig neubig added moderate bug Issues that should be fixed but only affect less common environments or functionality and removed duplicate fix needs confirmation labels Feb 21, 2017
@ilkerkesen
Copy link
Author

I think I've solved the issue, this is the output of train_xor:

https://gist.github.com/ilkerkesen/1105d1fa319cbd9d2ec9f5f9487a7e99

What I did is, I just compared my compilation process with Travis CI building. Ubuntu versions differ. So do the library versions. I've set CC/CXX variables to gcc-5/g++-5 (in Travis configuration, both of them same, 4.8).

I've also tried to run train_rnnlm example and now I am able to run it with no problem.

@neubig
Copy link
Contributor

neubig commented Feb 24, 2017

Glad to hear it was resolved!

@neubig neubig closed this as completed Feb 24, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
moderate bug Issues that should be fixed but only affect less common environments or functionality
Projects
None yet
Development

No branches or pull requests

2 participants