From: Willem Jan Withagen <wjw@digiware.nl>
To: Matt Benjamin <mbenjamin@redhat.com>
Cc: Ali Maredia <amaredia@redhat.com>, ceph-devel@vger.kernel.org
Subject: Re: Running Test Scripts without CMake Environment Variables
Date: Thu, 21 Apr 2016 11:11:01 +0200 [thread overview]
Message-ID: <57189925.6010407@digiware.nl> (raw)
In-Reply-To: <386579066.15401424.1461125540382.JavaMail.zimbra@redhat.com>
On 20-4-2016 06:12, Matt Benjamin wrote:
> Hi Willem,
>
> I think most devs now believe it's worth switching to cmake, mainly
> for build performance.
>
> I recall having issues compiling with Clang++ recently too--but for
> me, the issues seemed to be related to leveldb and rocksdb linkage.
> I know that a number of us would like Clang++ builds to be generally
> supported, not something that you have to maintain yourself just for
> FreeBSD.
>
> When you do experiment with cmake again, I'm sure folks will try to
> be helpful with specific issues.
'mmmm, lets give it a shot....
Created a separate WIP for it
And hope that Cmake guys lurk here
FreeBSD does have not udev, something similar is devd but it is
certainly not used to the extend
that udev it is used under Linux, as far as I can tell.
-- Not Found libudev: UDEV_LIBRARY-NOTFOUND
CMake Error at
/usr/local/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:148
(message):
Could NOT find udev (missing: UDEV_LIBRARIES UDEV_INCLUDE_DIR)
Call Stack (most recent call first):
/usr/local/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:388
(_FPHSA_FAILURE_MESSAGE)
cmake/modules/Findudev.cmake:52 (find_package_handle_standard_args)
CMakeLists.txt:129 (find_package)
And as for UUIDs I'm using a different library from a package
misc/e2fsprogs-libuuid and link with -luuid.
These are my full setting I use before running autogen.sh and configure:
CWARN=""
COPTIMIZE="-g -O0 -fno-omit-frame-pointer"
CLANGWARN="-Wno-unused-local-typedef -Wno-mismatched-tags
-Wno-macro-redefined -Wno-unused-function -Wno-unused-label
-Wno-undefined-bool-conversion -Wno-unused-private-field
-Wno-unused-local-typedef -Wno-uninitialized -Wno-gnu-designator
-Wno-inconsistent-missing-override -Wno-deprecated-declarations
-Wno-parentheses -Wno-missing-braces"
CFLAGS="${COPTIMIZE} -I/usr/local/include ${CWARN} ${CLANGWARN}"
CXXFLAGS="${COPTIMIZE} -DGTEST_USE_OWN_TR1_TUPLE=1
-I/usr/local/include ${CWARN} ${CLANGWARN}"
LDFLAGS="-g ${LDFLAGS} -L/usr/local/lib -export-dynamic -luuid -lcxxrt"
FREEBSD_CONFIGURE_FLAGS="
--disable-silent-rules
--disable-gitversion
--with-debug
--with-rados
--without-rbd
--with-radosgw
--with-radosstriper
--with-mon
--with-osd
--with-mds
--with-radosgw
--with-nss
--without-tcmalloc
--without-libaio
--without-libxfs
--without-fuse
--without-lttng
--with-libzfs=no
--without-rocksdb
--with-cephfs=no
"
With what incantations do I glue the above in the Cmake build process?
Thanx,
--WjW
prev parent reply other threads:[~2016-04-21 9:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <75379254.14369376.1461010122306.JavaMail.zimbra@redhat.com>
2016-04-18 21:53 ` Running Test Scripts without CMake Environment Variables Ali Maredia
2016-04-19 8:07 ` Willem Jan Withagen
2016-04-19 13:59 ` Matt Benjamin
2016-04-19 17:57 ` Willem Jan Withagen
2016-04-20 4:12 ` Matt Benjamin
2016-04-20 9:51 ` Willem Jan Withagen
2016-04-21 9:11 ` Willem Jan Withagen [this message]
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=57189925.6010407@digiware.nl \
--to=wjw@digiware.nl \
--cc=amaredia@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=mbenjamin@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).