From: Arthur Reutenauer <arthur.reutenauer@normalesup.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: linux binaries split?
Date: Sun, 25 Mar 2018 00:30:43 +0100 [thread overview]
Message-ID: <20180324233043.GA1389532@phare.normalesup.org> (raw)
In-Reply-To: <4251ab75-be01-2f8f-7000-2be1d9e28b49@gmail.com>
> However, I was the one who requested the musl detection in config.guess
> and the maintainer implemented the check like this for reasons of
> portability.
Without escaping the caret it’s not as portable as it could be. By
the way, I checked in the mean time, and the problem with unescaped
^musl in zsh is that it may be expanded to “any file name that is not
musl” which explains the output Thomas was getting. The grep command is
thus expanded to something like “grep -q dir1 dir2 file1 [piped output]”,
generating an error message for each directory. Mojca, if you want to
reproduce that, you need the extended glob option (setopt EXTENDED_GLOB).
See man zshexpn for details.
> Perhaps the problem is the else case in this statement. Maybe it should be:
>
> LIBC="glibc"
> if command -v ldd >/dev/null && ldd --version 2>&1 | grep -q ^musl
> then
> LIBC="musl"
> fi
That won’t help; it is logically equivalent to
if command -v ldd >/dev/null && ldd --version 2>&1 | grep -q ^musl
then
LIBC=musl
else
LIBC=glibc
fi
and doesn’t address any of problems.
Best,
Arthur
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2018-03-24 23:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-24 10:59 Thomas A. Schmitz
2018-03-24 11:14 ` luigi scarso
2018-03-24 12:30 ` Thomas A. Schmitz
2018-03-24 12:40 ` Hans Hagen
2018-03-24 12:40 ` Mojca Miklavec
2018-03-24 12:43 ` Hans Hagen
2018-03-24 11:15 ` Hans Hagen
2018-03-24 11:26 ` Hans Hagen
2018-03-24 12:32 ` Mojca Miklavec
2018-03-24 12:42 ` Hans Hagen
2018-03-24 12:57 ` Thomas A. Schmitz
2018-03-24 13:06 ` Arthur Reutenauer
2018-03-24 13:16 ` Thomas A. Schmitz
2018-03-24 16:44 ` Arthur Reutenauer
2018-03-24 16:51 ` Mojca Miklavec
2018-03-24 17:05 ` Thomas A. Schmitz
2018-03-24 18:10 ` Arthur Reutenauer
2018-03-24 23:55 ` Arthur Reutenauer
2018-03-25 16:24 ` Arthur Reutenauer
2018-03-24 17:36 ` luigi scarso
2018-03-24 17:43 ` Mojca Miklavec
2018-03-24 17:47 ` luigi scarso
2018-03-24 21:53 ` Henri Menke
2018-03-24 23:30 ` Arthur Reutenauer [this message]
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=20180324233043.GA1389532@phare.normalesup.org \
--to=arthur.reutenauer@normalesup.org \
--cc=ntg-context@ntg.nl \
/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;
as well as URLs for NNTP newsgroup(s).