Bug #77463 [Opn->Nab]: gcc warning & PHP doesn't start using own openssl & curl

Edit report at https://bugs.php.net/bug.php?id=77463&edit=1 ID: 77463 Updated by: nikic@php.net Reported by: office at vargapeter dot net Summary: gcc warning & PHP doesn't start using own openssl & curl -Status: Open +Status: Not a bug Type: Bug Package: Compile Warning Operating System: SLES 12.4 PHP Version: 7.2.14 Block user comment: N Private report: N New Comment: What I gather from the discussion is that the issue here was multiple different openssl versions getting loaded, as dependencies were linked against different openssl versions. As that wouldn't be an issue in PHP, I'm closing this issue, but please correct me if I misunderstood something and we need to address something on our side. Previous Comments: ------------------------------------------------------------------------ [2019-02-20 14:15:34] office at vargapeter dot net Yes my friend, you are right. ------------------------------------------------------------------------ [2019-02-20 14:02:20] spam2 at rhsoft dot net > More or less the same with glibc frankly, when you try to replace glibc you are asking for troubles as loud as possible and i would ask myself when i start to replace such low level parts of a distribution the following questions: * what do i gain with it * is it worth the troubles * is it worth having a unsupportable system given that nobody but you has the same setup for testing * if i gain someting with it why i am using the wrong distribution either i use something like Arch/Fedora or a LTS distribution and in case of an LTS distribution he whole point is to not have major bumps of everything so stick with the distribution libraries and when you can't build a recent PHP with that versions for whatever reason consider upgrade the OS anyways, this is hardly a PHP issue ------------------------------------------------------------------------ [2019-02-20 13:51:34] office at vargapeter dot net I pressed to fast the ENTER key. BUT, what about the wrong directories used by libtool? This is what I mean. That it doesn't work, OK, due to the openssl mixture, but that the compile process is using wrong paths? ------------------------------------------------------------------------ [2019-02-20 13:49:31] office at vargapeter dot net Yeah, I realized openssl must have a "deal breaker" in the past versions because NOTHING works with the new version when it expects openssl 1.0.x I may reconsider to use the most current openssl version because this is making me only lot of troubles. More or less the same with glibc - this must also run in a separated installation, otherwise the whole systems crashes... However guys, compiling it with --enable-debug produces lot of compiler warnings... ------------------------------------------------------------------------ [2019-02-20 13:31:01] spam2 at rhsoft dot net well, when you mix different library versions with inter-dependencies within the same process you are in the hands of god - that's why you should avoid override system packages until you know exactly what you are doing * the webserver loads openssl * curl loads openssl * php loads openssl and pretty sure some other libraries in the mix also are linked against openssl ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=77463 -- Edit this bug report at https://bugs.php.net/bug.php?id=77463&edit=1