Re: Build problems with packages which are using openssl
On Sun, Apr 23, 2023 at 6:56 PM e9hack wrote: > in the past, it was possible to build packages, which are using crypto > libraries like openssl, wolfssl or mbedtls, in parallel. One was build for > the image, selected as , the others were build as module selected as . > > This doesn't work any more, if a package is selected for usage of openssl > with and any other crypto library is selected with . > > Compiling is successful, but installation complains about to install a binary > twice from two different packages. > > I'm not sure, since when this does occur, but I assume, it was introduced > with the openssl update to 3.0.x. Hi Hartmut I'm trying to reproduce the issue here. I had hit it in my very first try, but then lost it when I tried to reproduce it with a log. From what I could glimpse, it appears to be an issue with the way opkg handles library selection. If a package depends on a library with a generic name, then it would use its own heuristics to install one of the versions found, and it may not be the one that was built into the image. Then, when it tries to install the selected library, it will fail because the file was already installed by the previous package. I submitted a patch series for opkg[1], but it has not caught much attention. You may try it yourself to see if it fixes your problem. I had it backwards in my case. Libustream-openssl was selected, but libustream-mbedtls got installed as a dependency. I couldn't identify the package right away. During the same run, dnsmasq and dnsmasq-full showed the same error, but it did not involve a library. It was strange and my tree was dirty, so I tried to build it from scratch, and the problem was gone. Also, note that menuconfig will let you choose bad combinations with libustream-ssl. It will let you install cache-domains-wolfssl, for example, even when libustream-mbedtls is already selected. That may also break install with the same error. I'm still trying, but if you can give me a config file, or the steps to reproduce it, I can work faster. Cheers, Eneas 1. https://patchwork.ozlabs.org/project/openwrt/cover/20221017170358.3628154-1-cotequei...@gmail.com/ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: Build problems with packages which are using openssl
I don't know if it's related, but syslog-ng-3.38.1 and now -4.1.1 keep crashing in libssl.so. [ 7263.710130] syslog-ng[6648]: segfault at 180 ip 7fe55725dd43 sp 7de33ed8 error 6 in libssl.so.3[7fe557252000+45000] [ 7263.715174] Code: e8 03 00 ff 15 8e dc 05 00 31 d2 31 c0 be 11 01 00 00 bf 14 00 00 00 ff 15 f2 d8 05 00 31 c0 5a c3 89 d1 48 8d 87 88 01 00 00 <48> 89 8f 80 01 00 00 48 39 f0 73 09 48 8d 14 08 48 39 d6 eb 0c 48 [ 7296.292439] syslog-ng[6767]: segfault at 180 ip 7fa446859d43 sp 7ffcb4e2dac8 error 6 in libssl.so.3[7fa44684e000+45000] [ 7296.297398] Code: e8 03 00 ff 15 8e dc 05 00 31 d2 31 c0 be 11 01 00 00 bf 14 00 00 00 ff 15 f2 d8 05 00 31 c0 5a c3 89 d1 48 8d 87 88 01 00 00 <48> 89 8f 80 01 00 00 48 39 f0 73 09 48 8d 14 08 48 39 d6 eb 0c 48 [ 7313.742858] syslog-ng[6832]: segfault at 180 ip 7f81280f0d43 sp 7fffcebbf898 error 6 in libssl.so.3[7f81280e5000+45000] [ 7313.747486] Code: e8 03 00 ff 15 8e dc 05 00 31 d2 31 c0 be 11 01 00 00 bf 14 00 00 00 ff 15 f2 d8 05 00 31 c0 5a c3 89 d1 48 8d 87 88 01 00 00 <48> 89 8f 80 01 00 00 48 39 f0 73 09 48 8d 14 08 48 39 d6 eb 0c 48 [ 7378.425765] syslog-ng[6916]: segfault at 180 ip 7f3c036a7d43 sp 7ffc825fd898 error 6 in libssl.so.3[7f3c0369c000+45000] [ 7378.430827] Code: e8 03 00 ff 15 8e dc 05 00 31 d2 31 c0 be 11 01 00 00 bf 14 00 00 00 ff 15 f2 d8 05 00 31 c0 5a c3 89 d1 48 8d 87 88 01 00 00 <48> 89 8f 80 01 00 00 48 39 f0 73 09 48 8d 14 08 48 39 d6 eb 0c 48 I'm having to switch over to rsyslog until we get this figured out. > On Apr 23, 2023, at 3:56 PM, e9hack wrote: > > Hi, > > in the past, it was possible to build packages, which are using crypto > libraries like openssl, wolfssl or mbedtls, in parallel. One was build for > the image, selected as , the others were build as module selected as . > > This doesn't work any more, if a package is selected for usage of openssl > with and any other crypto library is selected with . > > Compiling is successful, but installation complains about to install a binary > twice from two different packages. > > I'm not sure, since when this does occur, but I assume, it was introduced > with the openssl update to 3.0.x. > > Regards, > Hartmut > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Build problems with packages which are using openssl
Hi, in the past, it was possible to build packages, which are using crypto libraries like openssl, wolfssl or mbedtls, in parallel. One was build for the image, selected as , the others were build as module selected as . This doesn't work any more, if a package is selected for usage of openssl with and any other crypto library is selected with . Compiling is successful, but installation complains about to install a binary twice from two different packages. I'm not sure, since when this does occur, but I assume, it was introduced with the openssl update to 3.0.x. Regards, Hartmut ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
