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 2/2] package/glibc: bump to version 2.29
Date: Tue, 12 Mar 2019 22:34:57 +0100	[thread overview]
Message-ID: <20190312213457.GI25009@scaer> (raw)
In-Reply-To: <20190310165917.24325-2-romain.naour@gmail.com>

Romain, All,

On 2019-03-10 17:59 +0100, Romain Naour spake thusly:
[--SNIP--]
> diff --git a/package/glibc/glibc.mk b/package/glibc/glibc.mk
> index ec5b3cedc9..1437f87368 100644
> --- a/package/glibc/glibc.mk
> +++ b/package/glibc/glibc.mk
> @@ -13,7 +13,7 @@ GLIBC_SITE = $(call github,riscv,riscv-glibc,$(GLIBC_VERSION))
>  else
>  # Generate version string using:
>  #   git describe --match 'glibc-*' --abbrev=40 origin/release/MAJOR.MINOR/master
> -GLIBC_VERSION = glibc-2.28-69-g1e5c5303a522764d7e9d2302a60e4a32cdb902f1
> +GLIBC_VERSION = glibc-2.29-6-g067fc32968b601493f4b247a3ac00caeea3f3d61

I think at some point, someone suggested we drop the 'glibc-' prefix,
and jsut use e.g. 2.29-6-g067fc32968b601493f4b247a3ac00caeea3f3d61.

I just checked, and it seems to work:

    $ git show 2.29-6-g067fc32968b601493f4b247a3ac00caeea3f3d61
    commit 067fc32968b601493f4b247a3ac00caeea3f3d61 (origin/release/2.29/master)
    Author: Florian Weimer <fweimer@redhat.com>
    Date:   Fri Feb 15 21:27:01 2019 +0100

        nptl: Fix invalid Systemtap probe in pthread_join [BZ #24211]

        [...]

I think it is nicer...

Regards,
Yann E. MORIN.

>  # Upstream doesn't officially provide an https download link.
>  # There is one (https://sourceware.org/git/glibc.git) but it's not reliable,
>  # sometimes the connection times out. So use an unofficial github mirror.
> @@ -32,7 +32,7 @@ GLIBC_ADD_TOOLCHAIN_DEPENDENCY = NO
>  # Before glibc is configured, we must have the first stage
>  # cross-compiler and the kernel headers
>  GLIBC_DEPENDENCIES = host-gcc-initial linux-headers host-bison host-gawk \
> -	$(BR2_MAKE_HOST_DEPENDENCY)
> +	$(BR2_MAKE_HOST_DEPENDENCY) $(BR2_PYTHON3_HOST_DEPENDENCY)
>  
>  GLIBC_SUBDIR = build
>  
> -- 
> 2.14.5
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

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

  reply	other threads:[~2019-03-12 21:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-10 16:59 [Buildroot] [PATCH 1/2] support/dependencies: add a check for python3 Romain Naour
2019-03-10 16:59 ` [Buildroot] [PATCH 2/2] package/glibc: bump to version 2.29 Romain Naour
2019-03-12 21:34   ` Yann E. MORIN [this message]
2019-03-12 13:09 ` [Buildroot] [PATCH 1/2] support/dependencies: add a check for python3 Adam Duskett
2019-03-12 14:03   ` Romain Naour
2019-03-12 21:28 ` Yann E. MORIN

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=20190312213457.GI25009@scaer \
    --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