From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] kmsxx: not available on m68k
Date: Mon, 13 Feb 2017 13:29:25 +0100 [thread overview]
Message-ID: <20170213132925.5324f141@free-electrons.com> (raw)
In-Reply-To: <20170213093502.26507-1-peter@korsgaard.com>
Hello,
On Mon, 13 Feb 2017 10:35:02 +0100, Peter Korsgaard wrote:
> diff --git a/package/kmsxx/Config.in b/package/kmsxx/Config.in
> index 1d174c18b..3750897bb 100644
> --- a/package/kmsxx/Config.in
> +++ b/package/kmsxx/Config.in
> @@ -4,6 +4,7 @@ config BR2_PACKAGE_KMSXX
> depends on BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_8
> depends on BR2_INSTALL_LIBSTDCPP
> depends on BR2_TOOLCHAIN_HAS_THREADS # libdrm
> + depends on !BR2_m68k # gcc ice
As usual, I really prefer if we report the bug to gcc upstream, and
then do a depends on !BR2_TOOLCHAIN_HAS_GCC_BUG_xyz. Otherwise, it's
really tricky to keep track of when this or that issue gets resolved
and when we can re-enable m68k.
CC'ing Waldemar on this.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-02-13 12:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 9:35 [Buildroot] [PATCH] kmsxx: not available on m68k Peter Korsgaard
2017-02-13 12:29 ` Thomas Petazzoni [this message]
2017-02-13 14:32 ` Peter Korsgaard
2017-02-13 21:37 ` Waldemar Brodkorb
2017-02-14 10:15 ` Peter Korsgaard
2017-02-14 10:18 ` Thomas Petazzoni
2017-02-14 11:42 ` Waldemar Brodkorb
2017-02-14 11:58 ` Thomas Petazzoni
2017-02-14 12:10 ` Peter Korsgaard
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=20170213132925.5324f141@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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