From: Arthur Reutenauer <arthur.reutenauer@normalesup.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Build for Alpine Linux
Date: Mon, 9 Apr 2018 21:35:18 +0200 [thread overview]
Message-ID: <20180409193518.GA2842220@phare.normalesup.org> (raw)
In-Reply-To: <CA+Zb4MzVeKrQRzo8wR0ivXck5Cm=7+xfj1ezrx8v=S+SiWnf+g@mail.gmail.com>
> A few notes:
> a.) On some platforms fgrep has been deprecated (in favour of `grep -F`) so
> it's not future-proof
I don’t think the aliases fgrep and egrep have ever been supposed to
be portable. POSIX has grep -F and grep -E, and that’s what we should
use.
> b.) The caret (^) passed to `grep -F` will not be interpreted as a regex,
> since -F forces non-regexp, meaning the '^' will be interpreted literally
> (and the string "^musl" is not in the ldd output).
The caret in itself was not the problem, only that it was not escaped
for the shell. Testing a regexp, with -E of course, is just as robust,
and allows us to be more specific about what we test.
> if command -v ldd >/dev/null && ldd --version 2>&1 | grep -Fq 'musl' > /dev/null
grep -E '^musl' works just as well; and as I explained, -q may return
0 even if there are errors, so should be avoided.
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
___________________________________________________________________________________
next prev parent reply other threads:[~2018-04-09 19:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-07 21:04 double followtokens? Pablo Rodriguez
2018-04-07 21:25 ` Hans Hagen
2018-04-07 22:11 ` Pablo Rodriguez
2018-04-08 14:41 ` Hans Hagen
2018-04-08 14:56 ` Build for Alpine Linux Brian Hunt
2018-04-08 20:50 ` Mojca Miklavec
2018-04-08 21:09 ` Arthur Reutenauer
2018-04-08 21:26 ` Henri Menke
2018-04-08 21:45 ` Arthur Reutenauer
2018-04-09 0:50 ` Henri Menke
2018-04-09 18:59 ` Brian Hunt
2018-04-09 19:35 ` Arthur Reutenauer [this message]
2018-04-10 11:05 ` Brian Hunt
2018-04-10 12:26 ` Brian Hunt
2018-04-10 16:27 ` Alan Braslau
2018-04-10 20:55 ` Arthur Reutenauer
2018-04-11 12:30 ` Brian Hunt
2018-04-11 20:08 ` Brian Hunt
2018-04-11 20:24 ` Aditya Mahajan
2018-04-11 20:37 ` Hans Hagen
2018-04-11 21:08 ` Brian Hunt
2018-04-13 11:14 ` Mojca Miklavec
2018-04-13 11:42 ` Henri Menke
2018-04-13 19:54 ` Henning Hraban Ramm
2018-04-13 20:02 ` Aditya Mahajan
2018-04-13 12:49 ` Hans Hagen
2018-04-11 23:13 ` Henri Menke
2018-04-13 10:37 ` Brian Hunt
[not found] ` <CALBOmsaXyTXhR=j6Ht1LwKGcfxMD4sHjQnEOxtjH-4gc3b5R8g@mail.gmail.com>
[not found] ` <20180417152547.GA1755070@phare.normalesup.org>
2018-04-17 15:54 ` Thomas A. Schmitz
2018-04-08 18:10 ` double followtokens? Pablo Rodriguez
2018-04-08 21:17 ` Hans Hagen
2018-04-09 18:25 ` Pablo Rodriguez
2019-01-01 18:17 ` Hans van der Meer
2019-01-01 20:17 ` Hans Hagen
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=20180409193518.GA2842220@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).