Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild-run: 1/2] autobuild-run: update cs nios2 toolchain comment about PR19405.
Date: Sat,  6 May 2017 15:49:48 +0200	[thread overview]
Message-ID: <20170506134949.11995-1-romain.naour@gmail.com> (raw)

The toolchain was updated to 2017.02 but the PR19405 issue is still
present.

Signed-off-by: Romain Naour <romain.naour@gmail.com>
---
 scripts/autobuild-run | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/scripts/autobuild-run b/scripts/autobuild-run
index 20e0033..ed3ddd2 100755
--- a/scripts/autobuild-run
+++ b/scripts/autobuild-run
@@ -495,11 +495,11 @@ def fixup_config(**kwargs):
     if 'BR2_PACKAGE_WESTON=y\n' in configlines and \
        'BR2_TOOLCHAIN_EXTERNAL_URL="http://autobuild.buildroot.org/toolchains/tarballs/mipsel-ctng-linux-uclibc.tar.xz"\n' in configlines:
         return False
-    # The cs nios2 2016.05 toolchain is affected by binutils PR19405
+    # The cs nios2 2017.02 toolchain is affected by binutils PR19405
     if 'BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_NIOSII=y\n' in configlines and \
        'BR2_PACKAGE_BOOST=y\n' in configlines:
         return False
-    # The cs nios2 2016.05 toolchain is affected by binutils PR19405
+    # The cs nios2 2017.02 toolchain is affected by binutils PR19405
     if 'BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_NIOSII=y\n' in configlines and \
        'BR2_PACKAGE_QT5BASE_GUI=y\n' in configlines:
         return False
-- 
2.9.3

             reply	other threads:[~2017-05-06 13:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-06 13:49 Romain Naour [this message]
2017-05-06 13:49 ` [Buildroot] [autobuild-run: 2/2] autobuild-run: Add an exception for CS nios2 2016.05 with qt package (gui) Romain Naour
2017-05-06 13:59 ` [Buildroot] [autobuild-run: 1/2] autobuild-run: update cs nios2 toolchain comment about PR19405 Thomas Petazzoni

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=20170506134949.11995-1-romain.naour@gmail.com \
    --to=romain.naour@gmail.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