From: "Piotr Dałek" <branch@predictor.org.pl>
To: ceph-devel@vger.kernel.org
Subject: Re: building boost statically
Date: Fri, 29 Apr 2016 09:01:03 +0200 [thread overview]
Message-ID: <20160429070103.GF26146@predictor> (raw)
In-Reply-To: <alpine.DEB.2.11.1604281908430.25990@cpach.fuggernut.com>
On Thu, Apr 28, 2016 at 07:14:15PM -0400, Sage Weil wrote:
> On Thu, 28 Apr 2016, Robin H. Johnson wrote:
> > 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.
Plus, final binary sizes would be smaller if dynamic linking would succeed.
> 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.
That's bad idea, IMHO.
Why not check for features we need on configure state and use static or
dynamic accordingly?
--
Piotr Dałek
branch@predictor.org.pl
http://blog.predictor.org.pl
--
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:[~2016-04-29 7:05 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
2016-04-29 7:01 ` Piotr Dałek [this message]
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=20160429070103.GF26146@predictor \
--to=branch@predictor.org.pl \
--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.