Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] uclibc: clean-up test suite build command
Date: Mon, 30 Jun 2014 20:07:19 +0200	[thread overview]
Message-ID: <20140630200719.1339a6ed@free-electrons.com> (raw)
In-Reply-To: <1404149181-18586-1-git-send-email-abrodkin@synopsys.com>

Dear Alexey Brodkin,

On Mon, 30 Jun 2014 21:26:21 +0400, Alexey Brodkin wrote:
> Starting from uClibc 0.9.32 this cleaned-up command builds tests flawlessly.
> For 0.9.31 it lead to build failure, but assuming there're close to zero
> users who is going to test outdated uClibc library on obsolete
> (in Buildroot) AVR32 architecture I thin it worth applying.
> 
> Still it's possible to have 2 variants at the same time until AVR32 is not gone:
> 1. Old implementation used strictly for uClibc 0.9.31
> 2. New implementation for all other versions
> 
> Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>

Unfortunately, unless this cleaned-up version brings significant
benefits, I believe the best option is to keep things as is until AVR32
support is really deprecated and removed from Buildroot, so that we can
drop support for 0.9.31.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-06-30 18:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-30 17:26 [Buildroot] [PATCH] uclibc: clean-up test suite build command Alexey Brodkin
2014-06-30 18:07 ` Thomas Petazzoni [this message]
2014-07-01 10:27   ` Alexey Brodkin
2015-03-25  7:49   ` Alexey Brodkin
2015-03-25 16:39     ` Thomas Petazzoni
2015-04-20  8:39       ` Alexey Brodkin
2015-04-20  8:58         ` Thomas Petazzoni
2015-04-20  9:10           ` Alexey Brodkin

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=20140630200719.1339a6ed@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