-
Notifications
You must be signed in to change notification settings - Fork 520
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
[BUG] Install fails with BUILD_TLS=yes, USE_REDIS_SYMLINKS=no #377
Comments
The problem is that the It's fixable by appending this after export BULD_TLS I'm not sure if that's the right/clean way to fix it though. |
@michael-grunder What does this has to do with USE_REDIS_SYMLINKS=no? |
@zuiderkwast Nothing, I don't think anyway. The build was failing because the second invocation of make rebuilt hiredis but without forwarding Making the above change fixes the linker error. Isn't |
Yes, but it seemed to be part of the problem. @furai Do you get the same error without |
No that also solves the problem which does seem weird. Interestingly when you include |
Yeah, that's it! That USE_REDIS_SYMLINKS variable sets some macro in CFLAGS! We can remove that. We don't need to set that macro in CFLAGS. |
@furai Workaround: Use USE_REDIS_SYMLINKS=no in |
Don't let the Make valiable `USE_REDIS_SYMLINKS` affect the build. If it does, it causes the second line in the example below (`make install`) to recompile what was already compiled on the line above, and this time it's built without BUILD_TLS=yes USE_SYSTEMD=yes. make BUILD_TLS=yes USE_SYSTEMD=yes make PREFIX=custom/usr USE_REDIS_SYMLINKS=no install Fixes #377 Signed-off-by: Viktor Söderqvist <viktor.soderqvist@est.tech>
Workaround worked for me, thanks! |
I haven't had time to dig into it. What I'm doing is pretty simple, e.g.:
And then it fails with error because it can't find the aforementioned file. I was building from prepackaged version 7.2.5 available here on github.
Originally posted by @furai in #193 (comment)
Installation fails cause it can't find
libhiredis_ssl.a
.The text was updated successfully, but these errors were encountered: