Stupid question. Are both in c not c++? If at least one is in cpp wrap them in namespace. Can work anyway with wrapping if youll write thin cpp wrapper for one or both. Or some nifty macro nss_name(x) and ossl_name(x) to deconflict both xses.
śr., 7.04.2021, 14:57 użytkownik Thomas Klausner <w...@netbsd.org> napisał: > Hi! > > TL;DR: nss has some of the same symbols as openssl, which leads to > core dumps when both are linked in the same binary > > Long version: > > Recently I tried packaging Sigil for pkgsrc. It links against nss via > qtwebengine. It also links against openssl via qtbase libraries, and > it has an embedded python interpreter that loads python's ssl loadable > module, which links against openssl. > > Sigil's update checker uses a python script to download a file via > https. This dumps core on my machine, with a backtrace that ends in > nss, but the nss functions are called from openssl (which intends to > call its own functions of the same name instead). > > Lots of details are in the Sigil bug report[1]. > > In the meantime I've found that the pkgsrc package for nss already > renames some of the symbols for the same reason, but triggered by > libcups or libgssapi.[2] > > I wonder why this does not affect more people. Is pkgsrc or NetBSD > doing something weird/strange/wrong? > > I'm not quite sure what the best fix is. I can add more patches to the > pkgsrc package to locally rename symbols. > > I understand that it's hard to ask nss to change their symbols just > because openssl has the same names, but I think that's what I'm trying > to do with this email :) > > What do you recommend? > > Cheers, > Thomas > > > [1] https://github.com/Sigil-Ebook/Sigil/issues/604 > > [2] https://github.com/NetBSD/pkgsrc/blob/trunk/devel/nss/patches/patch-am > https://github.com/NetBSD/pkgsrc/blob/trunk/devel/nss/patches/patch-an > > https://github.com/NetBSD/pkgsrc/blob/trunk/devel/nss/patches/patch-nss_lib_freebl_md5.c > > -- > You received this message because you are subscribed to the Google Groups " > dev-tech-crypto@mozilla.org" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to dev-tech-crypto+unsubscr...@mozilla.org. > To view this discussion on the web visit > https://groups.google.com/a/mozilla.org/d/msgid/dev-tech-crypto/20210407121811.fuhja7gbgwg7qnst%40yt.nih.at > . > -- You received this message because you are subscribed to the Google Groups "dev-tech-crypto@mozilla.org" group. To unsubscribe from this group and stop receiving emails from it, send an email to dev-tech-crypto+unsubscr...@mozilla.org. To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/dev-tech-crypto/CALTpEH4j2zEQTon-%3Dy9u7FjBoZM%3DQLstomHHU7%2B6yD5%2BDdKCPA%40mail.gmail.com.
