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
zsh.pl fails because libssl.so.1.0.0 cannot be found #620
Comments
This issue was also mentioned here: fb7cbf7#commitcomment-15705608 I don't have an immediate fix for this that doesn't just bring back the old problem again... |
I vote that we remove this action from being done by default by the makefile as it produces problems no matter what. |
Sounds good to me. |
Perhaps zsh.pl could run during (Sorry for late response, I haven't seen the issue until just now.) |
@danielshahaf I don't think that would solve the problem. We already use the just built curl binary, but that doesn't work if e.g. some of the shared libraries used are in non-standard paths. This specific problem can be solved by passing In any case I'm ok with disabling the zsh generation by default too. |
I imagine this also applies to the test suite, but since that is run as a separate target it can just be not run at all. While the zsh generation is run as part of the main build. Another possible solution would be to just ignore the result from |
I think I've already asked this somewhere but for you guys using autotools isn't libtool supposed to do all this automatically? In other words it creates some sort of stub and then loads the right shared libraries before they're installed? |
@jay If you look at libtool only handles LD_LIBRARY_PATH for libraries internal to the project (that is libcurl), but if that library or executable depend on a library external to the project (e.g. libssl) then libtool depends on the system linker to know where to find it. And if that library is in non'standard paths (like in this case) then everything just breaks down. Of course there are ugly hacks like rpath that could solve this, but that's not really a proper solution. |
Environment:
/path/to/openssl
(which has the necessarylib/
andinclude/openssl
subdirectories)--with-ssl="/path/to/openssl"
Configuration and building work fine up to the point when the zsh completion is generated. The latter fails:
I can fix the build by
export
ingLD_LIBRARY_PATH="/path/to/openssl/lib"
before running make. Is this intended or should the build system set the LD_LIBRARY_PATH itself if I provideconfigure
with the path to my OpenSSL installation? I'm asking becauseconfigure
outputs the following, which seems to be limited to the configure run itself:The failure is detected by make since 92a2041. Before that, it would fail silently so that I didn't recognize the issue in 7.46.0.
The text was updated successfully, but these errors were encountered: