From: Brad Hubbard <bhubbard@redhat.com>
To: Samuel Just <sjust@redhat.com>, Sage Weil <sweil@redhat.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
"Deza, Alfredo" <adeza@redhat.com>
Subject: Re: c++11 merged in master
Date: Sat, 8 Aug 2015 10:03:24 +1000 [thread overview]
Message-ID: <55C5474C.6040008@redhat.com> (raw)
In-Reply-To: <CAN=+7FU_D=qcj-Ku_2JbFSZA1SM-4dBGJ6qcewmu3qnLQCGNJg@mail.gmail.com>
On 08/08/2015 04:36 AM, Samuel Just wrote:
> lambdas and autos for everyone!
\o/
> -Sam
>
> On Fri, Aug 7, 2015 at 10:52 AM, Sage Weil <sweil@redhat.com> wrote:
>> Yay! Thanks, Casey!
>>
>> This initially breaks the precise and el6 builds on master. I've fixed
>> the precise gitbuilders with
>>
>> sudo apt-get install python-software-properties
>> echo | sudo add-apt-repository ppa:ubuntu-toolchain-r/test
>> sudo apt-get update
>> sudo apt-get install -y g++-4.8
>> /srv/autobuild-ceph/gitbuilder.git/build/install-deps.sh
>> sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.6 60 --slave /usr/bin/g++ g++ /usr/bin/g++-4.6
>> sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.8 40 --slave /usr/bin/g++ g++ /usr/bin/g++-4.8
>> echo 2 | sudo update-alternatives --config gcc
>> sudo restart autobuild-ceph
>>
>> We'll need to do something similar on centos6 to get g++ 4.7 or 4.8 in
>> place, and the jenkins slaves for release builds will also need to be
>> updated.
>>
>> Assuming this doesn't cause problems (e.g., runtime issues on vanilla
>> precise) this will have no bearing on the previous discussion about
>> whether we continue supporting old distros for future releases.
>>
>> sage
>> --
>> 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
> --
> 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:[~2015-08-08 0:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 17:52 c++11 merged in master Sage Weil
2015-08-07 18:36 ` Samuel Just
2015-08-08 0:03 ` Brad Hubbard [this message]
2015-08-07 19:56 ` Ken Dreyer
2015-08-08 0:09 ` Brad Hubbard
2015-08-09 17:38 ` Sage Weil
2015-08-09 18:02 ` Dałek, Piotr
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=55C5474C.6040008@redhat.com \
--to=bhubbard@redhat.com \
--cc=adeza@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sjust@redhat.com \
--cc=sweil@redhat.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.