From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthias Fischer To: development@lists.ipfire.org Subject: Re: [PATCH] apache: Update to 2.4.38 Date: Fri, 01 Feb 2019 19:07:14 +0100 Message-ID: In-Reply-To: <6A16C532-07D6-460D-915E-B4F07C438AE9@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0879699068489043014==" List-Id: --===============0879699068489043014== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, On 01.02.2019 18:47, Michael Tremer wrote: >> Right now, '2.4.38' is running here under Core 126. No seen problems >> with GUI or anything else so far. Log is clean. My only glitch is the >> d*** 'libcrypto.so.1.1'-lib from sse2. As I wrote, all of my update >> efforts ended in breaking the system. >> >> One last thing I could do - would take some time - is to build under >> current 'next' and make a test installation on my testmachine (offline). > Hmm, I am slightly confused. Understandable. > So in Core 128, we are going to ship apache together with OpenSSL 1.1.1. So= that should be fine because the runtime version is the same as the built ver= sion. All older SSL libraries should be removed then. Yes - that's what I'm assuming too. In commit https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dcommit;h=3Df8d407e5f7ff0812bea= a6b45eae18b57475aa3d8 Arne added the missing '/usr/lib/sse2/libcrypto.so.1.1' for i586 which seems to be the culprit of my problems. They should be solved with this update. > So I suppose if the nightly build works, then the update should work, too. >=20 > Right? Yes. What I still don't understand: why the manual updates always failed with "openssl bus error". :-(( Best, Matthias --===============0879699068489043014==--