In the past, I suspected that we needed to do these kinds of paths so
that the JVM could find the C code for the JSS JNI modules. Is that no
longer true?
I do not see any tests below that necessarily test out JSS JNI
functionality. For example, one test might be to use pki to create a
client NSSDB.
If we still do need this, it would be nice to put in paths for Debian as
well, so that they do not need to patch this.
Ade
On Fri, 2015-05-29 at 18:02 -0600, Matthew Harmsen wrote:
Please review and test the attached patch out on platforms other
than
'x86_64' which addresses this issue:
* PKI TRAC Ticket #1392 - Remove i686/x86_64 architecture
limitations (e. g. - ppc64/ppc64le)
I did apply the attached patch and build it on an x86_64 machine, and
successfully tested out the following:
* built, installed, and tested out a CA
* built, installed, and tested out a CA console
* built, installed, and tested out a TKS and TPS
* built, installed, and tested out tpsclient
* AtoB and BtoA
_______________________________________________
Pki-devel mailing list
Pki-devel(a)redhat.com
https://www.redhat.com/mailman/listinfo/pki-devel