On Sun, Apr 23, 2023 at 6:56 PM e9hack <e9h...@gmail.com> 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 <y>, the others were build as module selected as <m>. > > This doesn't work any more, if a package is selected for usage of openssl > with <m> and any other crypto library is selected with <y>. > > 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
