All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sandon Van Ness <sandon@inktank.com>
To: ceph-devel@vger.kernel.org
Cc: ben@inktank.com
Subject: Master needs newer version of boost on centos?
Date: Fri, 14 Feb 2014 15:39:53 -0800	[thread overview]
Message-ID: <52FEA949.4090801@inktank.com> (raw)


The last couple builds of master have been failing on the centos 
gitbuilder. here is the build log:

http://gitbuilder.sepia.ceph.com/gitbuilder-centos6-amd64/log.cgi?log=f47062d8a66b94743888aaea13e0766579379395

Its running into:

CXX mds/Capability.lo
CXX mds/Dumper.lo
In file included from client/Client.h:38,
from libcephfs.cc:21:

      error: client/barrier.h:25:38: boost/icl/interval_set.hpp: No such
      file or directory 


It looks like its not effecting fedora gitbuilders that have a newer 
version of boost but on centos/rhel the version is only 1.41.0-18. Is 
there something we can do to get around this without back-porting or 
will backporting a newer boost for rhel/centos be necessary?

             reply	other threads:[~2014-02-14 23:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-14 23:39 Sandon Van Ness [this message]
2014-02-14 23:48 ` Master needs newer version of boost on centos? Sage Weil
2014-02-15  0:06   ` Matt W. Benjamin
2014-02-15  0:09     ` Matt W. Benjamin
2014-02-15  0:13       ` Sage Weil
2014-02-15  0:26         ` Matt W. Benjamin
2014-02-15  0:28           ` Josh Durgin
2014-02-15  0:44             ` Matt W. Benjamin
2014-02-17 17:35               ` Sage Weil
2014-02-17 17:38                 ` Matt W. Benjamin
2014-02-17 17:41                   ` Sage Weil
2014-02-17 17:47                     ` Matt W. Benjamin
2014-02-17 18:01                       ` Sage Weil
     [not found] <1438949751.95.1392660473769.JavaMail.root@thunderbeast.private.linuxbox.com>
2014-02-17 18:10 ` Matt W. Benjamin
2014-02-17 18:34   ` Sage Weil
2014-02-17 18:39     ` Matt W. Benjamin

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=52FEA949.4090801@inktank.com \
    --to=sandon@inktank.com \
    --cc=ben@inktank.com \
    --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.