From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCHv3 2/2] rpm: run binary package generation via thread pools
Date: Fri, 9 Jun 2017 23:58:34 +0300 [thread overview]
Message-ID: <e8331cde-c735-e18f-05cf-dc2a03a94359@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LakpwMpac5hsJzxMEWWQyBVb4HqQkFpL0OpzNbWn702kw@mail.gmail.com>
On 06/09/2017 07:32 PM, Burton, Ross wrote:
>
> On 9 June 2017 at 12:13, Alexander Kanavin
> <alexander.kanavin@linux.intel.com
> <mailto:alexander.kanavin@linux.intel.com>> wrote:
>
> This greatly reduces build times when there is a large amount of small
> rpm packages to produce. The patches are rather invasive,
> and so will be submitted upstream.
>
>
> Sorry but I broke this in the same way as I did before...
Needless to say, this worked flawlessly here, many times over. It seems
that failures might be specific to gcc 4.x (I have 6.x here), so I'll
try to get a failure using that. The nasty bit about openmp is that
#pragma omp unsupported_directive_from_latest_standard
will trigger nothing with compilers that are too old to support it.
Alex
prev parent reply other threads:[~2017-06-09 20:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 11:13 [PATCHv3 0/2] Multi-threaded RPM support Alexander Kanavin
2017-06-09 11:13 ` [PATCHv3 1/2] package_rpm.bbclass: use multithreaded xz compression Alexander Kanavin
2017-06-09 11:13 ` [PATCHv3 2/2] rpm: run binary package generation via thread pools Alexander Kanavin
2017-06-09 16:32 ` Burton, Ross
2017-06-09 20:58 ` 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=e8331cde-c735-e18f-05cf-dc2a03a94359@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox