-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
invalid use of incomplete type 'SSL_CTX {aka struct ssl_ctx_st}' #2799
Comments
Latest GCC version is currently 7.2, is that right ? I had also asked for OpenSSL version and boost version (we use openssl via boost). |
GCC is 7.2 |
BOOST Version: 1.62 |
Do you have commit 29497f7 ? If not, update. If yes, make clean and try again. |
I have cleaned my vps and I added more swap. Now compilation works well. Can we close @moneromooo-monero ? |
That's got nothing to do with the SSL type error, which has got to do with particular versions of software. |
I just had the same issue on a different computer (Ubuntu 16.04 LTS), might it have to do with libssl1.1.0g? Looks as if boost1.58 does not like openssl1.1.0.
and then later down the line
|
Did you build from scratch ? The cmake stuff is supposed to warn if you're using incompatible boost and openssl versions (29497f7) |
I've ran |
Maybe the version check should be against 106200, not 1.62. Not sure how that one works. Try it :) |
After building boost-1.65 I get a different error.
|
monero builds fine here with boost 1.65 and openssl 1.1.0f, GCC 6.4.1 (though I doubt the GCC version would cause those type issues). |
Does #3007 fix it ? make clean first to be sure. |
Builds just fine with #3007. Awesome! :) |
Great, thanks :) |
Should I close? I can confirm building is okay with patch #3007. |
When it's merged. |
+resolved |
Hello,
I'm trying to build Monero in my server. I created a partitioned disk only for building Monero.
OS: Debian 8.9
Platform: 64bit System, 50gb hard disk, 1gb RAM
I have cloned the repo 'monero' and
cd monero && make
GCC Version is the latest, cmake version 3.10
The text was updated successfully, but these errors were encountered: