From: David Laight <David.Laight@ACULAB.COM>
To: 'Nicolas Cavallari' <nicolas.cavallari@green-communications.fr>,
"Markus Mayer" <mmayer@broadcom.com>,
Arnout Vandecappelle <arnout@mind.be>,
"Petr Vorel" <petr.vorel@gmail.com>
Cc: Buildroot Mailing List <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 0/1] Build issue related to "command -v"
Date: Wed, 29 Sep 2021 16:14:20 +0000 [thread overview]
Message-ID: <515fab0378614d93821aed6a95cbd16e@AcuMS.aculab.com> (raw)
In-Reply-To: <a3acad98-edb0-1ac7-8d84-a3937a405646@green-communications.fr>
...
> Meanwhile, 'which' is not standard, and right now, it misbehaves on
> Debian by filling the screen with warnings.
'which' is a shell script that is trying to emulate a csh builtin.
I've NFI why people keep using it :-)
The equivalent bourne shell command is 'type'.
As for 'command -v' no idea what the POSIX committee had
for lunch that day :-)
It was probably they same day they added 'fc' (from ksh??)
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-09-29 16:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 19:55 [Buildroot] [PATCH 0/1] Build issue related to "command -v" Markus Mayer via buildroot
2021-09-28 19:55 ` [Buildroot] [PATCH 1/1] Makefile: set HOST*_NOCCACHE variables only if unset Markus Mayer via buildroot
2021-09-29 19:27 ` Petr Vorel
2021-12-28 21:18 ` Thomas Petazzoni
2021-12-28 21:26 ` Nicolas Cavallari
2021-12-29 9:00 ` Thomas Petazzoni
2021-12-29 9:12 ` Thomas Petazzoni
2021-09-29 8:24 ` [Buildroot] [PATCH 0/1] Build issue related to "command -v" Nicolas Cavallari
2021-09-29 16:14 ` David Laight [this message]
2021-09-29 17:30 ` Petr Vorel
2021-09-29 19:59 ` Arnout Vandecappelle
2021-09-29 20:11 ` Petr Vorel
2021-10-01 17:53 ` Markus Mayer via buildroot
2021-10-01 18:17 ` Yann E. MORIN
2021-10-02 19:23 ` Petr Vorel
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=515fab0378614d93821aed6a95cbd16e@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=arnout@mind.be \
--cc=buildroot@buildroot.org \
--cc=mmayer@broadcom.com \
--cc=nicolas.cavallari@green-communications.fr \
--cc=petr.vorel@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.