All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] uclibc: clean-up test suite build command
Date: Wed, 25 Mar 2015 07:49:24 +0000	[thread overview]
Message-ID: <1427269764.2718.4.camel@synopsys.com> (raw)
In-Reply-To: <20140630200719.1339a6ed@free-electrons.com>

Hi Thomas,

On Mon, 2014-06-30 at 20:07 +0200, Thomas Petazzoni wrote:
> 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.

Now when AVR32 support is finally dropped do you think this patch might
be accepted?

It still applies flawlessly on current master.

I build tested it on ARC and ARM. Note on ARM uClibc tests
(BR2_UCLIBC_INSTALL_TEST_SUITE) will be only compiled without errors
with uClibc-ng (BR2_UCLIBC_VERSION_NG), either BR2_UCLIBC_VERSION_0_9_33
or BR2_UCLIBC_VERSION_SNAPSHOT will fail on testsuite compilation but
that has nothing to do with current patch.

-Alexey

  parent reply	other threads:[~2015-03-25  7:49 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
2014-07-01 10:27   ` Alexey Brodkin
2015-03-25  7:49   ` Alexey Brodkin [this message]
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=1427269764.2718.4.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.