Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH V2 7/9] package/glibc: Add C-SKY support
Date: Sun, 26 May 2019 22:57:15 +0200	[thread overview]
Message-ID: <20190526225715.5c05bd21@windsurf> (raw)
In-Reply-To: <1557305915-11247-7-git-send-email-guoren@kernel.org>

Hello,

On Wed,  8 May 2019 16:58:33 +0800
guoren at kernel.org wrote:

> From: Guo Ren <ren_guo@c-sky.com>
> 
> Add glibc build for C-SKY Architecture.
> 
> Signed-off-by: Guo Ren <ren_guo@c-sky.com>
> ---
>  package/glibc/glibc.hash                | 2 ++
>  package/glibc/glibc.mk                  | 3 +++
>  toolchain/toolchain-buildroot/Config.in | 2 +-
>  3 files changed, 6 insertions(+), 1 deletion(-)
> 
> diff --git a/package/glibc/glibc.hash b/package/glibc/glibc.hash
> index 5316f03..6e47559 100644
> --- a/package/glibc/glibc.hash
> +++ b/package/glibc/glibc.hash
> @@ -1,2 +1,4 @@
>  # This hash file is not used; instead, update the
>  # hash files in the per-version sub-directories.

Well, did you see this comment ? If you did, why did you add some
hashes to this file ? :-)

> +# Locally calculated (fetched from https://github.com/c-sky/glibc)
> +sha512 9deb2deceefe347d72de13510a5baa3de00f94c684f3b25e136ca3660f61e65a69f2115abb488c2ab0fa93cda8535853ce1e13e186efcc8434ecc4049efd82b5  glibc-7630ed2fa60caea98f500e4a7a51b88f9bf1e176.tar.gz

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-05-26 20:57 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-08  8:58 [Buildroot] [PATCH V2 1/9] arch/csky: Add VDSP and FLOAT_ABI compiler options guoren at kernel.org
2019-05-08  8:58 ` [Buildroot] [PATCH V2 2/9] arch/csky: Add ck860 and -mcpu " guoren at kernel.org
2019-05-26 20:43   ` Thomas Petazzoni
2019-05-27  6:43     ` Guo Ren
2019-05-08  8:58 ` [Buildroot] [PATCH V2 3/9] arch/csky: Add toolchain build framework guoren at kernel.org
2019-05-26 20:44   ` Thomas Petazzoni
2019-05-27  6:52     ` Guo Ren
2019-05-08  8:58 ` [Buildroot] [PATCH V2 4/9] package/binutils: Add C-SKY support guoren at kernel.org
2019-05-26 20:52   ` Thomas Petazzoni
2019-05-27  7:23     ` Guo Ren
2019-05-08  8:58 ` [Buildroot] [PATCH V2 5/9] package/gcc: " guoren at kernel.org
2019-05-26 20:53   ` Thomas Petazzoni
2019-05-27  7:27     ` Guo Ren
2019-05-08  8:58 ` [Buildroot] [PATCH V2 6/9] package/gdb: " guoren at kernel.org
2019-05-26 20:56   ` Thomas Petazzoni
2019-05-27  8:08     ` Guo Ren
2019-05-08  8:58 ` [Buildroot] [PATCH V2 7/9] package/glibc: " guoren at kernel.org
2019-05-26 20:57   ` Thomas Petazzoni [this message]
2019-05-27  8:11     ` Guo Ren
2019-05-08  8:58 ` [Buildroot] [PATCH V2 8/9] support/config.sub: " guoren at kernel.org
2019-05-27 20:30   ` Thomas Petazzoni
2019-05-27 22:00     ` Peter Korsgaard
2019-05-28  6:55       ` Thomas Petazzoni
2019-06-06 15:19     ` Peter Korsgaard
2019-05-08  8:58 ` [Buildroot] [PATCH V2 9/9] configs/qemu_cskyXXX_virt: new defconfig guoren at kernel.org
2019-05-13  5:46 ` [Buildroot] [PATCH V2 1/9] arch/csky: Add VDSP and FLOAT_ABI compiler options Guo Ren
2019-05-26 20:39 ` Thomas Petazzoni
2019-05-26 20:40 ` Thomas Petazzoni
2019-05-27 11:35   ` Guo Ren

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=20190526225715.5c05bd21@windsurf \
    --to=thomas.petazzoni@bootlin.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