Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] glibc: add version 2.21
Date: Sun, 8 Feb 2015 16:39:17 +0100	[thread overview]
Message-ID: <20150208153917.GH4028@free.fr> (raw)
In-Reply-To: <1423408027-49694-2-git-send-email-Vincent.Riera@imgtec.com>

Vicente, All,

On 2015-02-08 15:07 +0000, Vicente Olivert Riera spake thusly:
> - Add version 2.21
> - Add a hash value for it
> 
> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>

Manually downloaded, and manually checked the hash: OK! :-)

Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>

Regards,
Yann E. MORIN.

> ---
>  package/glibc/Config.in  |    3 +++
>  package/glibc/glibc.hash |    1 +
>  2 files changed, 4 insertions(+), 0 deletions(-)
> 
> diff --git a/package/glibc/Config.in b/package/glibc/Config.in
> index 8c033f2..37e108e 100644
> --- a/package/glibc/Config.in
> +++ b/package/glibc/Config.in
> @@ -38,6 +38,9 @@ config BR2_GLIBC_VERSION_2_19
>  config BR2_GLIBC_VERSION_2_20
>  	bool "2.20"
>  
> +config BR2_GLIBC_VERSION_2_21
> +	bool "2.21"
> +
>  endchoice
>  
>  endif
> diff --git a/package/glibc/glibc.hash b/package/glibc/glibc.hash
> index 094bbda..f194de4 100644
> --- a/package/glibc/glibc.hash
> +++ b/package/glibc/glibc.hash
> @@ -6,3 +6,4 @@ md5	197836c2ba42fb146e971222647198dd	eglibc-2.19-svnr25243.tar.bz2
>  sha1	8013c1935b46fd50d2d1fbfad3b0af362b75fb28	eglibc-2.19-svnr25243.tar.bz2
>  sha256	2d3997f588401ea095a0b27227b1d50cdfdd416236f6567b564549d3b46ea2a2	glibc-2.19.tar.xz
>  sha256	f84b6d42aecc288d593c397b0a3d02260a33ee686bce0c634eb9b32798f36ba5	glibc-2.20.tar.xz
> +sha256  aeeb362437965a5d3f40b151094ca79def04a115bd363fdd4a9a0c69482923b8  glibc-2.21.tar.xz
> -- 
> 1.7.1
> 

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2015-02-08 15:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-08 15:07 [Buildroot] [PATCH 0/3] glibc: bump version to 2.21 Vicente Olivert Riera
2015-02-08 15:07 ` [Buildroot] [PATCH 1/3] glibc: add version 2.21 Vicente Olivert Riera
2015-02-08 15:39   ` Yann E. MORIN [this message]
2015-02-08 17:20   ` Baruch Siach
2015-02-08 17:29     ` Yann E. MORIN
2015-02-08 22:55   ` Peter Korsgaard
2015-02-09 10:39     ` Markos Chandras
2015-02-09 12:26       ` Peter Korsgaard
2015-02-09 23:37     ` Ezequiel Garcia
2015-02-10  0:07   ` Ezequiel Garcia
2015-02-10  6:05     ` Peter Korsgaard
2015-02-08 15:07 ` [Buildroot] [PATCH 2/3] glibc: set version 2.20 as default Vicente Olivert Riera
2015-02-08 15:40   ` Yann E. MORIN
2015-02-08 15:07 ` [Buildroot] [PATCH 3/3] glibc: remove version 2.19 Vicente Olivert Riera
2015-02-08 15:41   ` Yann E. MORIN
2015-02-08 22:52 ` [Buildroot] [PATCH 0/3] glibc: bump version to 2.21 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=20150208153917.GH4028@free.fr \
    --to=yann.morin.1998@free.fr \
    --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