Bug#732201: Please add libnssdb.a and libnssckfw.a to libnss3-dev

[Mike Hommey]

On Tue, Jan 14, 2014 at 07:12:50AM +0200, Timo Aaltonen wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 14.01.2014 07:04, Daniel Kahn Gillmor wrote:
> > On 01/13/2014 11:57 PM, Timo Aaltonen wrote:
> >> On 13.01.2014 11:05, Mike Hommey wrote:
> >>> The contents of libnssb.a are in libnss3.so. Why do you need 
> >>> libnssb?
> >> 
> >> For an apache module called mod_rev.so, configure.in has:
> >> 
> >> if ! test -e "$nss_lib_dir"/libnssb.a then AC_MSG_ERROR([NSS is 
> >> installed but the PKCS11 development package is missing. Need 
> >> libnssb.a]) fi
> > 
> > can this be done with dynamic linking instead?  if you use a static
> >  library, than any bugs found in nssb will mean we need to update
> > nss and *then* rebuild libapache2-mod-rev.  this seems clumsier
> > than just needing to update nss itself.
> 
> guess it's related to this snippet from README:
> 
> DEVELOPERS
> 
>   This module uses some internals from NSS. This is normally a big no-no
> but there was no other way to get around it. As such a private copy of
> some of the NSS include files can be found in the mozilla
> subdirectory. If you use a version of NSS other than 3.9.3 then you
> should replace the files in this directory with appropriate files from
> whatever version you are using.
> 
> and mozilla/README:
> 
> We need some private header files from NSS in order to build the module.
> Rather than checking them out at build time it is easier to include them
> here. We just need to be careful and watch for API changes.
> 
> 
> Fedora is the upstream, I could ask why it's like this.

Sounds like they should *really* talk with NSS upstream.

Mike