From: Sitsofe Wheeler <sitsofe@gmail.com>
To: Mark Beierl <Mark.Beierl@dell.com>
Cc: fio <fio@vger.kernel.org>
Subject: Re: Static linking and RDB/Rados
Date: Fri, 26 Oct 2018 05:11:53 +0100 [thread overview]
Message-ID: <CALjAwxjS4MXpf_K6mqE2vb=+sJ40iVgKQyLJ0zfEyR2JEBpfAQ@mail.gmail.com> (raw)
In-Reply-To: <3AF0240C-DE31-4E79-AB21-31D04B863142@emc.com>
Hi,
On Fri, 26 Oct 2018 at 00:53, Beierl, Mark <Mark.Beierl@dell.com> wrote:
>
> I’ve been doing some playing around with static linking and from the looks of it the static libraries for Rados and RDB are no longer available. Same goes for some of the libraries needed to enable HTTP (S3) support.
>
> So, I don’t think the options for –build-static are valid anymore. If anyone has pointers as to how to get the static Rados or RDB libraries, I’d love to hear about it :)
You didn't mention your distro but I think in the case of curl (which
is used for the HTTP/S3 suport) it will be highly environment
dependent. For example, Ubuntu seem to ship a static version of
libcurl (https://packages.ubuntu.com/bionic/amd64/libcurl4-gnutls-dev/filelist
and see libcurl-gnutls.a) but I can't see any static libcurl in
regular Fedora packages. In fact, I know that Fedora doesn't ship a
static libaio either and others have been forced to download the
source, build a private copy with a static library and then point fio
at that in they wanted such a binary on Fedora.
--
Sitsofe | http://sucs.org/~sits/
next prev parent reply other threads:[~2018-10-26 12:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-25 23:51 Static linking and RDB/Rados Beierl, Mark
2018-10-26 4:11 ` Sitsofe Wheeler [this message]
2018-10-26 11:02 ` Beierl, Mark
2018-10-26 21:24 ` Beierl, Mark
2018-10-27 9:54 ` Sitsofe Wheeler
2018-11-08 21:17 ` Beierl, Mark
2018-11-08 21:45 ` Sitsofe Wheeler
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='CALjAwxjS4MXpf_K6mqE2vb=+sJ40iVgKQyLJ0zfEyR2JEBpfAQ@mail.gmail.com' \
--to=sitsofe@gmail.com \
--cc=Mark.Beierl@dell.com \
--cc=fio@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.