-
Notifications
You must be signed in to change notification settings - Fork 446
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
Misses -lz for client to compile #3205
Comments
If not using miniconda2 in favor of openssl, no additional flag required. Adding |
I fail to understand why this omitted -lz could be caused by conda. I accredited it to --enable-boinczip . I don't want to create a pull request just now and propose to leave this report open for a while to collect more opinions/observations. |
Since I am the only one with weird experiences I suggest to just close this issue. What should possibly think about, though, is to provide a conda package for the client. This should then also clarify what this -lz is all about. |
The One reason that could fail is if your compiler can't build a simple program using gzopen() with -lz flag. I'd look for line |
config.log should show some additional detail.
…On Tue, Jul 30, 2019 at 9:04 AM Teemu Mannermaa ***@***.***> wrote:
The -lz flag is already required (and normally used) to build a BOINC
Client due to async_file.cpp
<https://github.com/BOINC/boinc/blob/master/client/async_file.cpp#L208>
and some other files referencing gzopen(), gzclose() and gzread()
unconditionally. The flag comes into client build via BOINC_EXTRA_LIBS
variable generated at configure.ac line 513
<https://github.com/BOINC/boinc/blob/master/configure.ac#L513>.
One reason that could fail is if your compiler can't build a simple
program using gzopen() with -lz flag. I'd look for line checking for
gzopen in static library z... -lz line in your config output. Other
configure output files like it's log and status can be consulted for more
information as well.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#3205?email_source=notifications&email_token=ACS5ZMWXT5JMZWTI6ZCCXELQCBRBZA5CNFSM4H43PQGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3EPAVA#issuecomment-516485204>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACS5ZMRVSORAGIRGGQE4LODQCBRBZANCNFSM4H43PQGA>
.
--
Eric Korpela
korpela@ssl.berkeley.edu
AST:7731^29u18e3
|
@smoe, any updated on this? |
I don't have the time to reinvestigate, I must admit. You don't mind me closing the issue for now, I presume. Thank you tons for your comments which will certainly help to get a better error report by whoever runs next into this (non?)issue. |
The error was
Circumvented with
Configuration was
The text was updated successfully, but these errors were encountered: