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 py
Hi Bob!
On Wed, Apr 07, 2021 at 09:00:36AM -0700, Robert Relyea wrote:
> In order to run into problems you are either:
...
> Linking directly with softoken (not supported).
Thank you for the detailed reply. This in particular was the problem.
The pkgsrc package had since time immemorial (> 15 ye
Hi again!
So I've fixed the pkgsrc package to not link nss users against
libsoftokn3 any longer, and this fixed the problem in Sigil.
The pkgsrc package had renamed the MD5_Update and SHA1_Update
functions in nss; since I assumed this to be safe now after stopping
to link against libsoftokn3, I'v
konqueror).
Thomas
On Sat, Apr 10, 2021 at 11:06:44AM +0200, Thomas Klausner wrote:
> Hi again!
>
> So I've fixed the pkgsrc package to not link nss users against
> libsoftokn3 any longer, and this fixed the problem in Sigil.
>
> The pkgsrc package had renamed the MD5_Upda
Hi Ryan!
Thanks for the reply.
Bob's reply was quite helpful already with his hint that nothing
should link against softokn3 or freebl. This was a bug in pkgsrc
previously, but I fixed it after his message. Nothing in pkgsrc now
links against either of the two directly. I think I followed all of
Hi Bob!
Thanks again for the detailed explanation of the nss build system.
With it, it was quite easy to see that the whole symbol hiding stuff
was just missing in the NetBSD configuration coming with nss. For
nss' purposes, you can handle NetBSD, FreeBSD, and OpenBSD nearly the
same. I reduced
er_bug.cgi?product=NSS&component=Build
> for a direct link.
>
> On Wed, May 5, 2021 at 9:45 AM Robert Relyea wrote:
> >
> > On 5/1/21 2:57 PM, Thomas Klausner wrote:
> > > Hi Bob!
> > >
> > > Thanks again for the detailed explanation of the nss build s
