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
Build failure on Linux #2519
Comments
It is not failing in travis (most of the times, there is some bug with dependencies, but that has nothing to do with openssl linking problems), see for example: https://travis-ci.org/telegramdesktop/tdesktop/jobs/166813384 I don't know why it fails in your system specifically :( Are you using custom built openssl or your system openssl (libssl / libcrypto) for linking? Some guys from stackoverflow have the same problem: |
@john-preston I followed your instructions step by step, didn't improvise or skipped something. I'm gonna build OpenSSL again and try again. |
@EhsaanF on Debug it should not take long, about 5-10 seconds. On release it is very long because of link time optimizations. They can be disabled in .gyp files if you don't want to wait so much - just remove all "-flto" flags from tdesktop/Telegram/gyp/telegram_linux.gypi. I didn't try that instructions step by step myself :) should test them I guess. |
@john-preston Test the instructions, please :) I think it has a few mistakes.
|
This function is part of openssl 1.0.2, not 1.0.1 that is used for tdesktop. Somehow you build Qt with support of the newer headers. What OS do you use? |
@john-preston Xubuntu 16.04.1 running on AMD64 on kernel v4.8.1 |
As I see in the openssl sources the headers for building Qt are used from the new version while the library is used of an older version. Try "git checkout OpenSSL_1_0_2-stable" when building openssl - it has that function. Will it work? But I didn't test tdesktop build with openssl of that branch, only with 1_0_1. |
Finally a healthy build !! |
@EhsaanF Well, the docs are for Ubuntu 12.04, it works there I suppose. |
After a successful build in debug mode, now I'm facing another error for build (I didn't change anything but OpenSans ttf files)
|
And if you check out openssl to the OpenSSL_1_0_1-stable branch this error goes away, but the old one returns in linking? (check out, make and sudo make install) |
Tested against OpenSSL_1_0_1-stable, same error I got last time.
😠 |
@EhsaanF I have no idea ¯_(ツ)_/¯ The "aes.h" header is included and "AES_ctr128_encrypt" should be there. |
All these problems motivates me to create my very own client, but implementing MTProto is so hard that almost makes me leave it 🤕 |
@EhsaanF If a feature implementation would take twice more time than creating an issue.. :) |
Hi. I'm trying to compile the source code on Linux as well and I'm getting the exact same errors. I see the issue is closed, but is there any solution for this? |
Okay I'm just trying to build this and it finally worked. Man, thanks a lot for your hard work, this is a great client! You're a nice guy @john-preston ^^ Also I've summarized the build process on this script and also added the missing dependencies which aren't mentioned. Anyway, thanks! |
Encountered the same issue with OpenSSL functions on 16.04. Perhaps it's time to update main build manual? |
I'm having this trouble on Arch:
with openssl 1.1.0.f This stands out:
|
Try "git checkout OpenSSL_1_0_2-stable" @john-preston Your solution works well. max@den: ~$ uname -a |
@angelskieglazki, this fix (and some others) already done in my all-in-one TD build script: https://github.com/vdmit/autogram |
Added the solution to the issues telegramdesktop#2519 and telegramdesktop#4418 that was found in respective thread discussion.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Build using GYP/CMake will be failed on Linux.
Needed a fast fix.
The text was updated successfully, but these errors were encountered: