Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ilixi: new package
Date: Wed, 6 Apr 2016 23:47:03 +0200	[thread overview]
Message-ID: <570583D7.8090202@mind.be> (raw)
In-Reply-To: <CAPWb3NQ6nw3r5YOV9pMZnu1X1tUbh9F7TTKXYBC_00KOrQBUjw@mail.gmail.com>

On 04/06/16 04:55, Justin Berger wrote:
> I didn't check it explicitly against 4.7, but I looked at the supported C++
> features in 4.7 vs 4.8 and it looked like it should work. Currently the only GCC
> options that show up in the menuconfig though are 4.8 and onwards, is the reason
> to prefer 4.7 vs 4.8 for people to backport?

  People may have a custom prebuilt toolchain using gcc 4.7.

  You can use Sourcery CodeBench SH 2012.09 or Sourcery CodeBench x86/x86_64 
2012.09 to test. Build test is probably enough, though the x86 toolchain should 
be easy to run-time test.

  Regards,
  Arnout


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2016-04-06 21:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-06  2:47 [Buildroot] [PATCH] ilixi: new package Justin Berger
2016-04-06  2:55 ` Justin Berger
2016-04-06 21:47   ` Arnout Vandecappelle [this message]
2016-04-06  4:33 ` Baruch Siach
2016-04-07 17:37   ` Justin Berger
2016-04-07 19:50     ` Baruch Siach
2016-04-07 20:10       ` Justin Berger
2016-04-07 20:24         ` Baruch Siach
2016-04-08  3:00 ` 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=570583D7.8090202@mind.be \
    --to=arnout@mind.be \
    --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