> It's definitely building xpdf from the GIT tree. We need to
> apply all patches or pull the latest xpdf code. Note the numerous deprecation
> warnings associated with xpdf as well:

The primary issue then would seem to be that the internal Trinity xpdf is not being updated with security patches.

> The CMake files could probably be changed to use xpdf
> libraries instead of the statically built xpdf libraries from the GIT tree. Well
> above my coding grade.

Likewise.

I'll write Yet Another Bug Report. Or two.

Darrell