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 v2] glibc: fix sh4 compile issue
Date: Thu, 13 Apr 2017 21:58:10 +0200	[thread overview]
Message-ID: <20170413215810.33e7c197@free-electrons.com> (raw)
In-Reply-To: <20170413050732.GA11817@waldemar-brodkorb.de>

Hello,

On Thu, 13 Apr 2017 07:07:32 +0200, Waldemar Brodkorb wrote:
> Fixes:
>   https://bugs.busybox.net/show_bug.cgi?id=9756
> 
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>

I've applied, but there were several issues:

 - First, you still don't use Git to format patches. Please use Git to
   format patches.

 - If you had done that, then the patches would have automatically had
   the original description, which we want to have in Buildroot.

 - Finally, for the 2.23, there was already a 0001-<something> patch,
   so the numbering was wrong.

I've fixed up those issues, see
https://git.buildroot.org/buildroot/commit/?id=5f2cff973a8a64411d85ccb9d5c9a40962d67552.

> In the past I remember some discussions about removing version
> selection for all C libraries. Any idea why we still have more than
> one glibc version?

Historical reason I'd say.

Thanks!

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

  reply	other threads:[~2017-04-13 19:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-13  5:07 [Buildroot] [PATCH v2] glibc: fix sh4 compile issue Waldemar Brodkorb
2017-04-13 19:58 ` Thomas Petazzoni [this message]
2017-04-24 19:25   ` Peter Korsgaard

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=20170413215810.33e7c197@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