From: Loic Dachary <loic@dachary.org>
To: Wido den Hollander <wido@42on.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Building Ceph statically linked
Date: Wed, 13 Nov 2013 21:24:32 +0100 [thread overview]
Message-ID: <5283E000.3040707@dachary.org> (raw)
In-Reply-To: <5283DF7D.9080203@42on.com>
On 13/11/2013 21:22, Wido den Hollander wrote:
> Hi,
>
> While doing some tests I'm trying to build Ceph statically. I have a bunch of machines where I run Ceph on for these test (mostly RGW now) and I'm running into some library issues when switching from branches.
>
> To make my life a bit easier I tried compiling Ceph (especially RGW) statically linked, but somehow I keep ending up with a dynamically linked binary.
>
> What I tried:
>
> $ env CXXFLAGS="-static" ./configure --enable-static --disable-shared
> $ make
>
> Usually that should spit out a static binary, but 'radosgw' is still dynamic.
>
I suspect it's because you did not --with-radosgw and it was not recompiled.
Cheers
> I'm not such a autoconf nor automake guru, so does anybody ever build static binaries with Ceph?
>
> Yes, I'm aware they can become very large, but that's not my concern right now. I just want to upload a binary to a machine, run it and see if it does what I'm hoping it does and not having to worry about all the dependencies being there and being the right version.
>
--
Loïc Dachary, Artisan Logiciel Libre
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-11-13 20:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 20:22 Building Ceph statically linked Wido den Hollander
2013-11-13 20:24 ` Loic Dachary [this message]
2013-11-13 20:33 ` Wido den Hollander
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=5283E000.3040707@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=wido@42on.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 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.