Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Romain Naour <romain.naour@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH next 2/2] package/glibc: bump to 2.39
Date: Sun, 3 Mar 2024 10:17:42 +0100	[thread overview]
Message-ID: <ZeRANiTB3lbbJ5MB@landeda> (raw)
In-Reply-To: <20240303083314.156042-3-thomas.petazzoni@bootlin.com>

Thomas, all,

On 2024-03-03 09:33 +0100, Thomas Petazzoni via buildroot spake thusly:
[--SNIP--]
> diff --git a/package/glibc/glibc.mk b/package/glibc/glibc.mk
> index d198d6f04c..96a850516f 100644
> --- a/package/glibc/glibc.mk
> +++ b/package/glibc/glibc.mk
> @@ -7,7 +7,7 @@
>  # Generate version string using:
>  #   git describe --match 'glibc-*' --abbrev=40 origin/release/MAJOR.MINOR/master | cut -d '-' -f 2-
>  # When updating the version, please also update localedef
                                       ^^^^^^^^^^^^^^^^^^^^^
You forgot to ------------------------'

Regards,
Yann E. MORIN.

> -GLIBC_VERSION = 2.38-44-gd37c2b20a4787463d192b32041c3406c2bd91de0
> +GLIBC_VERSION = 2.39-5-ge0910f1d3278f05439fb434ee528fc9be1b6bd5e
>  # 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.
> @@ -195,7 +195,6 @@ define GLIBC_CONFIGURE_CMDS
>  		--without-gd \
>  		--with-headers=$(STAGING_DIR)/usr/include \
>  		$(if $(BR2_aarch64)$(BR2_aarch64_be),--enable-mathvec) \
> -		--enable-crypt \
>  		$(GLIBC_CONF_OPTS))
>  	$(GLIBC_ADD_MISSING_STUB_H)
>  endef
> @@ -206,7 +205,7 @@ endef
>  #
>  
>  GLIBC_LIBS_LIB = \
> -	ld*.so.* libanl.so.* libc.so.* libcrypt.so.* libdl.so.* libgcc_s.so.* \
> +	ld*.so.* libanl.so.* libc.so.* libdl.so.* libgcc_s.so.* \
>  	libm.so.* libpthread.so.* libresolv.so.* librt.so.* \
>  	libutil.so.* libnss_files.so.* libnss_dns.so.* libmvec.so.*
>  
> -- 
> 2.43.0
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/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.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-03-03  9:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-03  8:33 [Buildroot] [PATCH next 0/2] Upgrade to glibc 2.39 Thomas Petazzoni via buildroot
2024-03-03  8:33 ` [Buildroot] [PATCH next 1/2] package/gcc: add patches to remove crypt()/crypt_r() libsanitizer interceptors Thomas Petazzoni via buildroot
2024-04-01  9:27   ` Yann E. MORIN
2024-03-03  8:33 ` [Buildroot] [PATCH next 2/2] package/glibc: bump to 2.39 Thomas Petazzoni via buildroot
2024-03-03  9:17   ` Yann E. MORIN [this message]
2024-04-01  9:30   ` 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=ZeRANiTB3lbbJ5MB@landeda \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=romain.naour@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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