Hi!
Thanks, Martin & Bob!
I've created
https://bugzilla.mozilla.org/show_bug.cgi?id=1709654
I can't assign to people, but I cc'd Bob.
Thank you for the help,
Thomas
On Wed, May 05, 2021 at 10:05:02AM +1000, Martin Thomson wrote:
> https://bugzilla.mozilla.org/enter_bug.cgi?product=NSS&compon
https://bugzilla.mozilla.org/enter_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 system.
> >
> > With it, it wa
On 5/1/21 2:57 PM, Thomas Klausner wrote:
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, Free
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
On 4/16/21 11:12 AM, Thomas Klausner wrote:
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 o
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 again!
No ideas for solutions this time?
Then I come back to my original request of renaming these internal
symbols so that they don't conflict with openssl...
(We've worked around this in pkgsrc by switching libreoffice from nss
to openssl, but now the same problem appeared in konqueror).
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 napis
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
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
On 4/7/21 5:18 AM, Thomas Klausner wrote:
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
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
12 matches
Mail list logo
