On Fri, 2 Nov 2012, Gary Lowell wrote: > Digging a little bit deeper, there is actually a comment in > common/ceph_crypto.h that when using libnss you need the CRYPTO_CXFLAGS. > Since the pk11 headers are installed, I'm not sure there is problem we > could detect. Let's add the flags to all of our builds. Is it possible to include them in AM_CXXFLAGS or something insetad of adding it to every target's CXXFLAGS? sage > This may be related to dmick's question about include paths. Someone > who knows more history will have to answer that. > > Cheers, > Gary > > > > On Nov 2, 2012, at 7:21 PM, Noah Watkins wrote: > > > On Fri, Nov 2, 2012 at 6:04 PM, Gary Lowell <gary.lowell@xxxxxxxxxxx> wrote: > >> Looks like the complaints come from a small number of newish programs that are compiled only when the --with-debug flag is given. When building against cryptpp (--with-cryptpp) the pk11 headers are found implicitly and when building agains libnss (--with-nss) they are not. > >> > >> So we probably need the changes in your wip-make-crypto-flags branch. > > > > Ahh that makes sense. Now I can reproduce it. The branch is up at > > wip-crypto-flags. Seems like we should have ./configure blow up too if > > it can't find this stuff? > > > > - Noah > > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > > -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
