All of lore.kernel.org
 help / color / mirror / Atom feed
From: Erwan Velu <evelu@redhat.com>
To: Alfredo Deza <adeza@redhat.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>, ceph-maintainers@ceph.com
Subject: Re: Ceph 0.94.8 for Precise has build issues
Date: Mon, 29 Aug 2016 11:39:29 -0400 (EDT)	[thread overview]
Message-ID: <1865565590.6858495.1472485169410.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CAC-Np1yrGo-N2gFRoxRquEdFEz-+yHhNgdJDAKvjaHcHsCwvmw@mail.gmail.com>

I'm not a Ubuntu expert by I found that :

The 1.48 version of -dev package depends on libboost1.46-dev
1.48 package doesn't provide any content (http://us.archive.ubuntu.com/ubuntu/pool/main/b/boost-defaults/libboost-dev_1.48.0.2_amd64.deb)

As a result, we get a 1.46 which doesn't have the random_device.hpp.

That's very confusing and explains what you are reporting.

Anyone have ideas why it's done like that ?

----- Mail original -----
De: "Alfredo Deza" <adeza@redhat.com>
À: "ceph-devel" <ceph-devel@vger.kernel.org>, ceph-maintainers@ceph.com
Envoyé: Lundi 29 Août 2016 16:44:38
Objet: Ceph 0.94.8 for Precise has build issues

0.94.8 was released a few days ago, but Precise will refuse to build
correctly with the following error:

In file included from ./include/types.h:21:0,
                 from ./msg/msg_types.h:20,
                 from ./common/entity_name.h:24,
                 from ./common/config.h:26,
                 from ./common/dout.h:20,
                 from ./common/debug.h:18,
                 from erasure-code/jerasure/ErasureCodeJerasure.cc:18:
./include/uuid.h:14:42: fatal error: boost/random/random_device.hpp:
No such file or directory

This is not an issue specific to the environment where we try Precise
builds (Jenkins)  as it is also present in the Precise gitbuilder [0]

It looks like there is an inconsistency in the package versions for libboost.

The debian/control file specifies a version of libboost-dev >= 1.42,
but there are changes in library paths that Ceph relies that are
present in 1.47 and above [1]. Precise has a few libboost versions
including 1.46 and 1.48, since 1.46 meets the requirement in the
control file it gets installed.

I have tried changing the control file at build time (completely
non-ideal) but still facing the same issue:

-               libboost-dev (>= 1.42),
+               libboost-dev (>= 1.48),

If someone else can chime in on how to properly fix this for Precise
would be great. If it means a change in the Ceph source it will mean
that we will be required to get 0.94.9 out with that fix (0.94.8 is
already tagged)

-Alfredo

[0] http://gitbuilder.sepia.ceph.com/gitbuilder-ceph-deb-precise-amd64-basic/log.cgi?log=838cd35201e4fe1339e16d987cc33e873524af90
[1] http://www.boost.org/doc/libs/1_46_0/doc/html/boost/random_device.html
--
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

      reply	other threads:[~2016-08-29 15:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-29 14:44 Ceph 0.94.8 for Precise has build issues Alfredo Deza
2016-08-29 15:39 ` Erwan Velu [this message]

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=1865565590.6858495.1472485169410.JavaMail.zimbra@redhat.com \
    --to=evelu@redhat.com \
    --cc=adeza@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=ceph-maintainers@ceph.com \
    /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.