I acknowledge what Sage says about most of boost being header only but I still feel compelled to offer some input here. https://www.akkadia.org/drepper/no_static_linking.html https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7-Beta/html-single/Developer_Guide/index.html#lib.compatibility.static I guess we are aware of these pain points and have decided "it's worth it"? -- Cheers, Brad On Fri, Sep 30, 2016 at 10:42 PM, Matt Benjamin <mbenjamin@xxxxxxxxxx> wrote: > Hi Ken, > > I'm doubtful that case will arise in practice? > > Matt > > ----- Original Message ----- >> From: "Ken Dreyer" <kdreyer@xxxxxxxxxx> >> To: "Sage Weil" <sweil@xxxxxxxxxx> >> Cc: "ceph-devel" <ceph-devel@xxxxxxxxxxxxxxx> >> Sent: Thursday, September 29, 2016 6:42:48 PM >> Subject: Re: boost submodule update >> >> On Thu, Sep 29, 2016 at 10:00 AM, Sage Weil <sweil@xxxxxxxxxx> wrote: >> > * There is still the option to use a system boost via a cmake option. I >> > doubt anyone will opt for this in practice given the distros tend to lag, >> > but they can if they want. >> >> Can we have it automatically enable the system boost if it's > 1.6.1? >> Otherwise I'm afraid no one will set WITH_SYSTEM_BOOST :) >> >> Fedora 26 or 27 will probably have Boost 1.6.2+ >> (https://bugzilla.redhat.com/1374088) >> >> - Ken >> -- >> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in >> the body of a message to majordomo@xxxxxxxxxxxxxxx >> More majordomo info at http://vger.kernel.org/majordomo-info.html >> > > -- > 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 > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html