All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: "Davis, Michael" <michael.davis@essvote.com>,
	Joshua Lock <joshua.g.lock@linux.intel.com>,
	Richard Purdie <richard.purdie@linuxfoundation.org>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>,
	Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
Subject: Re: [PATCH 0/2] Multi-threaded RPM support
Date: Mon, 5 Jun 2017 17:00:56 +0300	[thread overview]
Message-ID: <3c4f7666-8de0-a20e-ca59-d0cf339aef1b@linux.intel.com> (raw)
In-Reply-To: <655290B7709079438B7932553958E60DA1310D09@ESS-EX01.essvote.corp.local>

On 06/05/2017 04:47 PM, Davis, Michael wrote:
> I just wanted to note that in my quest to get newer chrome to build I have used centos7 with the official devtoolset-6 scl.
> It was able to build my pyro based distro fine in gcc6.  So Centos7 has an officially supported path that may be viable if it comes down to being the last gcc 4.x distro.

I guess at some point we'll have to officially do this as well, as the 
upstream projects will adopt C/C++11 (or even newer) and otherwise 
become incompatible with 4.x.

Alex


      reply	other threads:[~2017-06-05 14:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-01 15:15 [PATCH 0/2] Multi-threaded RPM support Alexander Kanavin
2017-06-01 15:15 ` [PATCH 1/2] package_rpm.bbclass: use multithreaded xz compression Alexander Kanavin
2017-06-01 17:11   ` Mark Hatle
2017-06-01 17:44     ` Alexander Kanavin
2017-06-01 19:02   ` Andre McCurdy
2017-06-02 11:40     ` Alexander Kanavin
2017-06-02 18:33       ` Andre McCurdy
2017-06-01 15:15 ` [PATCH 2/2] rpm: run binary package generation via thread pools Alexander Kanavin
2017-06-01 16:02   ` Alexander Kanavin
2017-06-02 12:44     ` Alexander Kanavin
2017-06-01 16:52 ` [PATCH 0/2] Multi-threaded RPM support Leonardo Sandoval
2017-06-01 17:13   ` Mark Hatle
2017-06-01 17:37     ` Alexander Kanavin
2017-06-02 21:41       ` Leonardo Sandoval
2017-06-02 22:20 ` Richard Purdie
2017-06-04 14:15 ` Richard Purdie
2017-06-05 12:14   ` Alexander Kanavin
2017-06-05 12:41     ` Alexander Kanavin
2017-06-05 13:01     ` Burton, Ross
2017-06-05 13:15       ` Alexander Kanavin
2017-06-05 13:21     ` Joshua Lock
2017-06-05 13:34       ` Alexander Kanavin
2017-06-05 13:47         ` Davis, Michael
2017-06-05 14:00           ` Alexander Kanavin [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=3c4f7666-8de0-a20e-ca59-d0cf339aef1b@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=joshua.g.lock@linux.intel.com \
    --cc=leonardo.sandoval.gonzalez@linux.intel.com \
    --cc=michael.davis@essvote.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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.