From: Matt Benjamin <mbenjamin@redhat.com>
To: Sage Weil <sage@newdream.net>
Cc: ceph-devel@vger.kernel.org
Subject: Re: building boost statically
Date: Thu, 28 Apr 2016 19:45:06 -0400 (EDT) [thread overview]
Message-ID: <847912519.21444831.1461887106208.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1604281908430.25990@cpach.fuggernut.com>
Hi,
----- Original Message -----
> From: "Sage Weil" <sage@newdream.net>
> To: ceph-devel@vger.kernel.org
> Sent: Thursday, April 28, 2016 7:14:15 PM
> Subject: Re: building boost statically
>
> On Thu, 28 Apr 2016, Robin H. Johnson wrote:
> > On Thu, Apr 28, 2016 at 06:47:55PM -0400, Sage Weil wrote:
> > > Hi all,
> > >
> > > We'd really like to use the latest boost, mainly so that we can use
> > > small_vector in a zillion places and avoid extra memory allocations. The
> > > distros, as always, are behind.
> >
> > From a distribution perspective, LESS static building is better, so this
> > proposal is a concern, but I do realize that the Gentoo/ArchLinux/CoreOS
> > perspective is very different than the Ubuntu LTS perspective.
> >
> > What's the state of having a more-up-to-date Boost in things like Ubuntu
> > backports, so that you don't have the overhead of having to maintain
> > your own boost packages or statically link?
> >
> > If support for statically linking a newer Boost is brought it, please,
> > please keep dynamic boost builds as fully supported, for distributions
> > that can keep up to date. As a bonus, at some point in the future, when
> > the slower distributions catch up, you might be able to escape the
> > static again.
>
> Yeah, having the option to either build statically or dynamically against
> an up-to-date distro is probably the right carrot/stick combination to
> incentivize the distros to move to a newer boost.
++
>
> Being able to conditionally not use the new stuff (e.g., typedef
> small_vector<> back to vector<>) may or may not work well, depending on
> which new thing we're trying to use.
I wouldn't want to do that.
>
> FWIW, we made the static -> dynamic transition with leveldb because the
> distros complained and it was nothing but sadness--so so many hours wasted
> chasing bugs in ancient distro versions of leveldb, and a huge matrix of
> version possibilities that made it difficult to reproduce user issues. I
> can't tell if there was ever an instance where it actually gained us
> anything (e.g., security update in leveldb), but I kind of doubt it.
This reminds me--we seem to still have issues with distro leveldbs, rocksdbs and clang++.
Matt
>
> sage
> --
--
Matt Benjamin
Red Hat, Inc.
315 West Huron Street, Suite 140A
Ann Arbor, Michigan 48103
http://www.redhat.com/en/technologies/storage
tel. 734-707-0660
fax. 734-769-8938
cel. 734-216-5309
next prev parent reply other threads:[~2016-04-28 23:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 22:47 building boost statically Sage Weil
2016-04-28 22:56 ` Robin H. Johnson
2016-04-28 23:14 ` Sage Weil
2016-04-28 23:45 ` Matt Benjamin [this message]
2016-04-29 7:01 ` Piotr Dałek
2016-04-28 23:05 ` Yehuda Sadeh-Weinraub
2016-04-29 2:31 ` Haomai Wang
2016-04-29 22:55 ` Ken Dreyer
2016-04-30 1:43 ` Sage Weil
2016-04-30 3:24 ` Allen Samuels
2016-05-01 15:08 ` Jesse Williamson
2016-05-01 15:14 ` Sage Weil
2016-05-02 3:28 ` Adam C. Emerson
2016-05-02 16:09 ` Jesse Williamson
2016-05-02 16:14 ` Adam C. Emerson
2016-05-02 16:18 ` Jesse Williamson
2016-05-02 16:31 ` Adam C. Emerson
2016-05-02 23:04 ` Matt Benjamin
2016-05-03 1:01 ` Jesse Williamson
2016-05-03 1:14 ` Matt Benjamin
2016-05-03 16:28 ` Robert LeBlanc
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=847912519.21444831.1461887106208.JavaMail.zimbra@redhat.com \
--to=mbenjamin@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@newdream.net \
/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.