From: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Buildslaves and C++11 support
Date: Mon, 17 Oct 2016 18:00:00 -0000 [thread overview]
Message-ID: <d0cf1fbb-4bd3-51b1-7360-b68dc13829a6@redhat.com> (raw)
In-Reply-To: <70152188-5427-1eb1-a2bf-d77251d36a78@redhat.com>
On 10/17/2016 02:51 PM, Pedro Alves wrote:
> I'd like to get this in soon to unblock Tromey's C++ series, and more.
> We can move along with the C++11 discussion / plan in parallel.
>
> Any objections?
>
> I'll be more than happy to remove this when we finally make C++11 a
> requirement. But I don't want to rush that. We should make sure that
> the buildbot's buildslaves are ready, for example.
A small update here.
I plan to use the new trybot support to test a patch
that forces the C++11 requirement, to determine which
buildbots don't have a recent enough compiler yet. Also
chatting with Sergio about getting this info written
down and visible on the buildbot web frontend or extracted
systematically out of the builds, to avoid this "in the dark"
situation.
The Debian buildslave was one I knew was old enough to not have
recent enough gcc for full C++11 support. It was running Debian
Wheezy, which comes with gcc 4.4 OOTB. After a little digging,
I found at [1] that it's easy to install Jessie's gcc 4.9
packages on Wheezy:
~~~~
This leaves the original GCC,G++ in place. If you wish to compile with
the 4.9 version, then either set the CC and CXX env vars accordingly or
invoke the compilers as gcc-4.9 or g++-4.9 explicitly.
~~~~
I pointed Mark Wielaard, the buildslave owner, at this, and he
instead upgraded the machine to Debian Jessie instead over the
weekend. :-) Many thanks Mark. One down, $N to go.
[1] - http://stackoverflow.com/questions/25147363/how-to-install-g-4-9-on-debian-wheezy-armel
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-10-17 18:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 12:29 [PATCH v2] Introduce gdb::unique_ptr Pedro Alves
2016-10-14 12:50 ` [PATCH v3] " Pedro Alves
2016-10-14 16:07 ` Simon Marchi
2016-10-14 16:11 ` Pedro Alves
2016-10-14 16:31 ` Pedro Alves
2016-10-16 7:14 ` Tom Tromey
[not found] ` <70152188-5427-1eb1-a2bf-d77251d36a78@redhat.com>
2016-10-17 18:00 ` Pedro Alves [this message]
2016-10-17 23:20 ` Buildslaves and C++11 support Pedro Alves
2016-10-19 3:23 ` John Baldwin
2016-10-19 12:50 ` Pedro Alves
2016-10-18 2:33 ` [PATCH v4] Introduce gdb::unique_ptr Tom Tromey
2016-10-18 10:45 ` Pedro Alves
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=d0cf1fbb-4bd3-51b1-7360-b68dc13829a6@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox