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

Wrong check for libevent #49

Closed
RoyBellingan opened this issue Nov 16, 2014 · 4 comments
Closed

Wrong check for libevent #49

RoyBellingan opened this issue Nov 16, 2014 · 4 comments

Comments

@RoyBellingan
Copy link

I'm getting the error
...
checking for libevent >= 1.0... no
configure: error: Please install libevent

The code used to check the libevent version is https://gist.github.com/RoyBellingan/42d1cd5a974e64ce3367
(of course the stdio and the printf are mine, I've also hardcoded the min requested version)
This is around line 18070 in configure (another check is around 19888)
The first check is failed (and secondo seems to pass or is not executed) but the version is 2.0.21-stable

@azgo14
Copy link

azgo14 commented Nov 25, 2014

I had the same problem (same output as you). From looking at my config.log, it seems the problem actually wasn't libevent, it was that double-conversion library could not be found (forgot to add it it LDFLAGS and LD_LIBRARY_PATH). Not sure if you have the same problem but hopefully this helps.

@NotYoCheese
Copy link

I'm trying to get proxygen to build on Centos 7. Proxygen clones and builds fbthrift. I will send in the deps scripts if I can get them working. I too am having a failure in the check for libevent in ./configure. Looking into the config.log it creates a conftest.c, compiles and runs the executable. The executable fails with the error:
"./conftest: error while loading shared libraries: libfolly.so.18: cannot open shared object file: No such file or directory"

If I manually add the folly/.libs directory to the LD_LIBRARY_PATH:
export LD_LIBRARY_PATH="pwd/folly/folly/.libs/:$LD_LIBRARY_PATH" configure finishes successfully. This is the cause of my particular "libevent" version failure.

@ghost
Copy link

ghost commented Aug 5, 2015

Thank you for reporting this issue and appreciate your patience. We've notified the core team for an update on this issue. We're looking for a response within the next 30 days or the issue may be closed.

@eduardo-elizondo
Copy link
Contributor

Closing to clean and provide better support to new issues. We are rewriting docs and guides on how to support this.

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

4 participants