From: "Jim Schutt" <jaschut@sandia.gov>
To: ceph-devel@vger.kernel.org
Cc: Jim Schutt <jaschut@sandia.gov>
Subject: [PATCH] osd: nss build of OSD.cc needs CRYPTO_CXXFLAGS since commit d59f34ab
Date: Fri, 2 Sep 2011 14:50:45 -0600 [thread overview]
Message-ID: <1314996645-19678-1-git-send-email-jaschut@sandia.gov> (raw)
nss build fails like this:
if /bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I. -D__KERNEL_STRICT_NAMES -Wall -D__CEPH__ -D_FILE_OFFSET_BITS=64 -D_REENTRANT -D_THREAD_SAFE -D__STDC_FORMAT_MACROS -D_GNU_SOURCE -rdynamic -Winit-self -Wpointer-arith -fno-strict-aliasing -Wnon-virtual-dtor -Wno-invalid-offsetof -Wstrict-null-sentinel -g -MT OSD.lo -MD -MP -MF ".deps/OSD.Tpo" -c -o OSD.lo `test -f 'osd/OSD.cc' || echo './'`osd/OSD.cc; \
then mv -f ".deps/OSD.Tpo" ".deps/OSD.Plo"; else rm -f ".deps/OSD.Tpo"; exit 1; fi
g++ -DHAVE_CONFIG_H -I. -I. -I. -D__KERNEL_STRICT_NAMES -Wall -D__CEPH__ -D_FILE_OFFSET_BITS=64 -D_REENTRANT -D_THREAD_SAFE -D__STDC_FORMAT_MACROS -D_GNU_SOURCE -rdynamic -Winit-self -Wpointer-arith -fno-strict-aliasing -Wnon-virtual-dtor -Wno-invalid-offsetof -Wstrict-null-sentinel -g -MT OSD.lo -MD -MP -MF .deps/OSD.Tpo -c osd/OSD.cc -fPIC -DPIC -o .libs/OSD.o
In file included from ./os/LFNIndex.h:27,
from ./os/HashIndex.h:20,
from ./os/FileStore.h:26,
from osd/OSD.cc:25:
./common/ceph_crypto.h:44:22: error: pk11pub.h: No such file or directory
Commit d59f34ab made FileStore.h include HashIndex.h, which ultimately
results in OSD.cc including ceph_crypto.h.
Signed-off-by: Jim Schutt <jaschut@sandia.gov>
---
src/Makefile.am | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/src/Makefile.am b/src/Makefile.am
index e53b68d..f3ca34b 100644
--- a/src/Makefile.am
+++ b/src/Makefile.am
@@ -928,6 +928,7 @@ libosd_la_SOURCES = \
osd/OSDCaps.cc \
osd/Watch.cc \
osd/ClassHandler.cc
+libosd_la_CXXFLAGS= ${CRYPTO_CXXFLAGS} ${AM_CXXFLAGS}
libosd_la_LIBADD = libglobal.la
noinst_LTLIBRARIES += libosd.la
--
1.7.1
reply other threads:[~2011-09-02 20:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1314996645-19678-1-git-send-email-jaschut@sandia.gov \
--to=jaschut@sandia.gov \
--cc=ceph-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.