From: Mike Gilbert <floppym@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Cc: soap@gentoo.org
Subject: Re: [gentoo-dev] [PATCH 1/2] cmake-utils.eclass: Make ninja default backend in EAPI >= 7
Date: Thu, 13 Sep 2018 10:25:13 -0400 [thread overview]
Message-ID: <CAJ0EP42AQVEBD=WrPJNKo-R1O3RAzYv2PwLCZd5iKhPen1ocdQ@mail.gmail.com> (raw)
In-Reply-To: <20180726063501.18702-1-soap@gentoo.org>
On Thu, Jul 26, 2018 at 2:35 AM <soap@gentoo.org> wrote:
>
> From: David Seifert <soap@gentoo.org>
>
> * Using the ninja backend as a default is the only way to
> massively improve src_compile core utilization, given that
> it seems unlikely that CMake will ever produce non-recursive
> Makefiles.
I just want to bring your attention to this bug comment, which would
indicate a regression in the kitware branch of ninja that I was asked
to merge by the Gentoo cmake maintainers.
https://bugs.gentoo.org/663384#c1
If this comment proves to have the right conclusion, I will likely
revert back to the vanilla upstream codebase until the kitware branch
can be fixed.
This may effect your plans to enable ninja by default, since it will
break any fortran package.
next prev parent reply other threads:[~2018-09-13 14:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 6:35 [gentoo-dev] [PATCH 1/2] cmake-utils.eclass: Make ninja default backend in EAPI >= 7 soap
2018-07-26 6:35 ` [gentoo-dev] [PATCH 2/2] cmake-utils.eclass: Enable BUILD_SHARED_LIBS by default " soap
2018-09-13 9:55 ` Andreas Sturmlechner
2018-07-26 7:21 ` [gentoo-dev] [PATCH 1/2] cmake-utils.eclass: Make ninja default backend " Michał Górny
2018-09-13 9:55 ` Andreas Sturmlechner
2018-09-13 14:25 ` Mike Gilbert [this message]
2018-09-13 18:55 ` Andreas Sturmlechner
2018-09-13 19:01 ` Michał Górny
2018-09-14 6:59 ` Francesco Riosa
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='CAJ0EP42AQVEBD=WrPJNKo-R1O3RAzYv2PwLCZd5iKhPen1ocdQ@mail.gmail.com' \
--to=floppym@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=soap@gentoo.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