Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Disabling Synopsys ARC pre-built toolchains in Buildroot
Date: Fri, 17 Apr 2015 21:47:26 +0200	[thread overview]
Message-ID: <5531634E.5070104@mind.be> (raw)
In-Reply-To: <1429260577.2846.27.camel@synopsys.com>

On 17/04/15 10:49, Alexey Brodkin wrote:
>  [1] Buildroot defconfigs for uClibc are not generated by "make
> savedefconfig" which makes it very hard to understand which options are
> enabled and which are disabled compared to defaults.

 I think the only reason why this is the case is that uClibc didn't use to
support savedefconfig. AFAICS 0.9.33.2 still doesn't.


>  [2] Buildroot defconfig may contain options (disabled or enabled
> compared to defaults) that might be harmful (in run-time issues like
> performance degradation etc). Remember missing
> UCLIBC_HAS_STRING_GENERIC_OPT. This is I think a reminder of early days
> of Buildroot. And so blind use of Buildroot defconfig as defconfig for
> ARC might not work well enough.

 We're certainly open to improving the BR defconfigs!


 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:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2015-04-17 19:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-10  9:21 [Buildroot] Disabling Synopsys ARC pre-built toolchains in Buildroot Thomas Petazzoni
2015-04-17  8:49 ` Alexey Brodkin
2015-04-17 19:47   ` Arnout Vandecappelle [this message]
2015-04-22 10:47     ` Alexey Brodkin
2015-04-22 11:29       ` Thomas Petazzoni
2015-04-22 20:15       ` Arnout Vandecappelle
2015-04-23 15:26       ` Waldemar Brodkorb

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=5531634E.5070104@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