mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Ariadne Conill <ariadne@dereferenced.org>
To: musl@lists.openwall.com, Jeffrey Walton <noloader@gmail.com>
Subject: Re: [musl] Re: [platform-testers] new snapshot available: grep-3.4-almost.19-ff30
Date: Sat, 19 Sep 2020 15:00:58 -0600	[thread overview]
Message-ID: <9188925c-52df-c21f-71ca-e002d9ed3a2d@dereferenced.org> (raw)
In-Reply-To: <CAH8yC8kuy4FDCZUa8RLtHzr57QFy5Oq_r8fZz4+=pfaOvkS+zQ@mail.gmail.com>

Hello,

On 2020-09-19 08:12, Jeffrey Walton wrote:
> Hi Everyone,
> 
> An FYI from testing a grep release candidate. The RC experienced 3
> failures on Alpine Linux.
> 
> Bruno Haible tracked down the cause.
> 
> I usually update a package's config.guess and config.sub according to
> https://www.gnu.org/software/gettext/manual/html_node/config_002eguess.html.
> I may have contributed to the problem by using the latest config.guess
> and config.sub.
> 
> I'm not sure if there is anything actionable for Musl or Alpine.

This was curious, so I looked into it.

/usr/bin/ldd was changed to be a shell script in the Alpine musl 
1.1.22-r1 package.  This was done to improve the output of the ldd command.

The problem with this package is that shell script was:

exec /lib/ld-musl-$ARCH.so.1 --list -- "$@"

In Alpine musl 1.1.22-r3, the shell script was changed to:

exec /lib/ld-musl-$ARCH.so.1 --list "$@"

This allowed --version to work again as expected.

I don't think that GNU needs to have a workaround for this.  We can 
simply backport 1.1.22-r3 to Alpine 3.10 to resolve the bug.

Ariadne

  reply	other threads:[~2020-09-19 21:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m2imce1gpu.fsf@meyering.net>
     [not found] ` <CAH8yC8mn1YMN+fgzJBKEk9+y0qTqfO2zHbWUyO2ekVq-PimX3Q@mail.gmail.com>
     [not found]   ` <4884197.be5NI9L3Sv@omega>
2020-09-19 14:12     ` Jeffrey Walton
2020-09-19 21:00       ` Ariadne Conill [this message]
2020-09-19 21:05         ` Ariadne Conill

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=9188925c-52df-c21f-71ca-e002d9ed3a2d@dereferenced.org \
    --to=ariadne@dereferenced.org \
    --cc=musl@lists.openwall.com \
    --cc=noloader@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).