Re: systemd-resolved
Pocket ([email protected] via lfs-support Mailing List) <[email protected]> Wed, 29 Jul 2026 16:31:55 -0400
| Newsgroups | gmane.linux.lfs.support |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format... ------------=_1785357129-2574352-6531 Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 7/29/26 14:22, Bruce Dubbs ([email protected] via lfs-support Mailing List) wrote: > On 7/29/26 12:50 PM, Pocket ([email protected] via lfs-support > Mailing List) wrote: >> >> On 7/29/26 13:40, Bruce Dubbs ([email protected] via lfs-support >> Mailing List) wrote: >>> On 7/29/26 12:20 PM, Pocket ([email protected] via lfs-support >>> Mailing List) wrote: >>>> > > [snip] > >>>> >>>> >>>> There isn't libcrypto.so.3 or libssl.so.3 >>>> >>>> find /usr/lib -name 'libcrypto*' >>>> /usr/lib/pkgconfig/libcrypto.pc >>>> /usr/lib/libcrypto.so >>>> /usr/lib/libcrypto.so.4 >>>> >>>> find /usr/lib -name 'libssl*' >>>> /usr/lib/pkgconfig/libssl.pc >>>> /usr/lib/libssl.so >>>> /usr/lib/libssl.so.4 >>>> /usr/lib/libssl3.so >>> >>> It looks like you have portions of both openssl3 and openssl4 >>> present. Check the contents of libcrypto.pc and libssl.pc. What >>> version of systemd do you have? There are a lot of changes needed for >>> openssl4 if you are doing an in-place update. >>> >>> You are using a development version of LFS (r13.0-152-systemd) which >>> is quite a bit out of date. The current version is -160 and there >>> will be a new version on Saturday with some significant package updates. > >> I cloned the lfs.git repo and made the book myself >> >> This build is straight from that book version I posted >> >> Systemd-261.1 >> >> OpenSSL-4.0.1 >> >> >> The .pc files are as follows >> >> libcrypto.pc >> >> prefix=/usr >> exec_prefix=${prefix} >> libdir=${exec_prefix}/lib >> includedir=${prefix}/include >> modulesdir=${libdir}/ossl-modules >> >> Name: OpenSSL-libcrypto >> Description: OpenSSL cryptography library >> Version: 4.0.1 >> Libs: -L${libdir} -lcrypto >> Libs.private: -ldl -pthread >> Cflags: -I${includedir} >> >> >> libssl.pc >> >> prefix=/usr >> exec_prefix=${prefix} >> libdir=${exec_prefix}/lib >> includedir=${prefix}/include >> >> Name: OpenSSL-libssl >> Description: Secure Sockets Layer and cryptography libraries >> Version: 4.0.1 >> Requires.private: libcrypto >> Libs: -L${libdir} -lssl >> Cflags: -I${includedir} > > Ok. Those look good. I am confused though why your first post said you > have /usr/lib/libssl3.so. I do not have that on my > >> I am of the opinion that resolved will not link to /usr/lib/ >> libssl.so.4 and /usr/lib/ libcrypto.so.4 > > That's possible. I cannot confirm or deny right now. > >> Archlinux has not update to openssl 4 as of today, so I think is is an >> issue with systemd >> Things may still be i a state of flux. > Yes openssl4 causes a lot of changes. We will be starting our full > tests for LFS-13.1 in about two weeks. That will include systemd-261.2. > You might want to try that. > > -- Bruce > Right now my focus is on creating a LXQT desktop, If I can pull that off then I can ditch the distro I am now currently using. -- Hindi madali ang maging ako ------------=_1785357129-2574352-6531 Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- http://lists.linuxfromscratch.org/sympa/info/lfs-support Unsubscribe: See the above information page ------------=_1785357129-2574352-6531--