--=-=-=
Content-Transfer-Encoding: quoted-printable


"John R. Shannon" <john@johnrshannon.com> writes:

> I've been working on this and am encountering problems I need guidance
> on. GnuPG 1.9.93 depends on libassuan built with pth. GnuPG 1.9.93 and
> pinentry also depend on pth. Currently, security/gnupg-devel and
> security/pinentry build pth locally and link statically to the pth
> library to avoid conflicts with native pthreads on NetBSD. I can
> eliminate the static linking to pth and make libassuan, gnupg-devel
> and pinentry dependant on pth, however, I noticed that having pth
> causes problems with other packages (perl won't build) on NetBSD.
>
> Recommendations?

I think pkgsrc should work with pth installed.  But breaking perl is
pretty serious.

I think it's broken that GnuPG stuff needs pth instead of working
POSIX threads.  But that seems to be the case.

So I suppose the short-term choices are to add static pth to
libassuan, or to depend on pth and pick up the pieces.  Longer term,
there's also getting GnuPG fixed to just require POSIX threads.

I'd lean towards trying to fix pkgsrc so it's ok to have pth
installed.

=2D-=20

    Greg Troxel <gdt@ir.bbn.com>

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (NetBSD)

iD8DBQFFN3kk+vesoDJhHiURAr3GAKC0+/0FK43Sf0Pn4i1hxEzLt8l3JACcDbIR
wsdHuUiGWRnXOqnD8jR4vdE=
=n8j8
-----END PGP SIGNATURE-----
--=-=-=--