On 16/06/2026 20:06, ASSI via Cygwin wrote:
Jon Turney via Cygwin writes:
It does seem that both libssl1.1 and libssl3 have this file (which is
permitted).
Oh I forgot about this wart… that only rears it's ugly head when both
packages are installed in the same run, though. Now what pulls in
libssl1.1 still on a fresh Cygwin install? I guess I should just rename
Both libssl1.1 and libssl3 have "Base" category.
Generally, I don't think that category should be applied to packages
which are just libraries.
that script to openssl3.sh to get around that issue.
Not sure how the logic in setup handles that case, though.
It will have renamed the sole existing file the first time it was run to
openssl.sh.done and then complain it can find it when it wants to run it
for the second package.
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation: https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
