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: Wed, 22 Apr 2015 22:15:43 +0200	[thread overview]
Message-ID: <5538016F.7020308@mind.be> (raw)
In-Reply-To: <1429699622.2596.34.camel@synopsys.com>

On 04/22/15 12:47, Alexey Brodkin wrote:
[snip]
> As for remaining differences between Buildroot and ARC uClibc defconfigs
> these are ones I may see (comparing
> https://github.com/foss-for-synopsys-dwc-arc-processors/uClibc/blob/arc-mainline-dev/extra/Configs/defconfigs/arc/defconfig with "uClibc-snapshot.config" from http://patchwork.ozlabs.org/patch/462812/):
> 
>  [1] MALLOC_GLIBC_COMPAT=y
>  [2] UCLIBC_HAS_GETPT=y
>  [3] UCLIBC_HAS_CTYPE_CHECKED=y
>  [4] UCLIBC_HAS_HEXADECIMAL_FLOATS=y
>  [5] UCLIBC_HAS_GLIBC_CUSTOM_PRINTF=y
>  [6] UCLIBC_HAS_FOPEN_EXCLUSIVE_MODE=y
>  [7] UCLIBC_HAS_PRINTF_M_SPEC=y
>  [8] UCLIBC_HAS_SSP=y
>  [9] UCLIBC_BUILD_NOW=y
> 
> Most of these options enable more compatibility with glibc or even
> expand support for non-standard features like
> UCLIBC_HAS_FOPEN_EXCLUSIVE_MODE.
> 
> Do you think some of them are really important and we may want to add
> them in ARC defconfigs?

 Well, basically the uClibc configs we have are just a configuration that was
created many many years ago. Occasionally some option is added when there are
important packages that need it, but it's not as if really a lot of thought goes
into these configs nowadays.

 Since you're doing active development with uClibc, I expect that there are some
options that you encounter that actually improve the quality of the resulting
library, it would be good to get patches that enable them (of course with
sufficient explanation _why_ it's a good idea to enable it).

 Your commit 826f315d is a great example of this.


 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

  parent reply	other threads:[~2015-04-22 20:15 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
2015-04-22 10:47     ` Alexey Brodkin
2015-04-22 11:29       ` Thomas Petazzoni
2015-04-22 20:15       ` Arnout Vandecappelle [this message]
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=5538016F.7020308@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