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

configure: error: Didn't find the libev library dir in #105

Open
daniixxl opened this issue Dec 8, 2016 · 2 comments
Open

configure: error: Didn't find the libev library dir in #105

daniixxl opened this issue Dec 8, 2016 · 2 comments

Comments

@daniixxl
Copy link

daniixxl commented Dec 8, 2016

checking for libev library location... no
configure: error: Didn't find the libev library dir in '/usr/lib/x86_64-linux-gnu/ /usr/lib/x86_64-linux-gnu//lib64 /usr/lib/x86_64-linux-gnu//lib /usr/lib/x86_64-linux-gnu//lib64/libev /usr/lib/x86_64-linux-gnu//lib/libev'

@scriptzteam
Copy link

which os, ubuntu? debian? what did you ./configure(ing), ocelot? how do we know ? not much info there ;)

@lwd-adam
Copy link

lwd-adam commented May 2, 2020

I'm having this same issue on Focal Fossa 20.04.

Using no --with-ev flag complains about "/usr/local/libev/lib64 /usr/local/libev/lib /usr/local/lib64/libev /usr/local/lib/libev /opt/libev/lib64 /opt/libev/lib /usr/lib64/libev /usr/lib/libev /usr/local/lib64 /usr/local/lib /usr/lib64 /usr/lib" instead. Using the flag for /usr/lib/x86_64-linux-gnu/ yields a search for subdirectories which don't exist - the libev.a and libev.so files are in the directory itself.

According to ev++.m4 this message is triggered by the absence of libev.a and libev.so which are indeed in the x86_64-linux-gnu folder, I suppose I will try symlinking each to one of the error folders and maybe remove the links after the build.

Update: it works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants