From: Andreas Schwab <schwab@linux-m68k.org>
To: Lancelot SIX via Gdb-patches <gdb-patches@sourceware.org>
Cc: Lancelot SIX <lsix@lancelotsix.com>
Subject: Re: [PATCH] [PR gdb/27614] gdb-add-index fails on symlinks.
Date: Thu, 25 Mar 2021 10:15:26 +0100 [thread overview]
Message-ID: <87eeg3k30x.fsf@igel.home> (raw)
In-Reply-To: <20210325004358.31291-1-lsix@lancelotsix.com> (Lancelot SIX via Gdb-patches's message of "Thu, 25 Mar 2021 00:43:58 +0000")
On Mär 25 2021, Lancelot SIX via Gdb-patches wrote:
> +if test -L "$1"; then
> + # This script will most likely fail if the argument is a symlink to a
> + # program. In order to avoid that, try to follow the symlink. However,
> + # readlink is not a standard POSIX tool so we have to check if it is
> + # available.
> + if command -v readlink &>/dev/null; then
&> isn't standard shell.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2021-03-25 9:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 0:43 Lancelot SIX via Gdb-patches
2021-03-25 9:15 ` Andreas Schwab [this message]
2021-03-25 14:27 ` Lancelot SIX via Gdb-patches
2021-03-25 14:50 ` Simon Marchi via Gdb-patches
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=87eeg3k30x.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=gdb-patches@sourceware.org \
--cc=lsix@lancelotsix.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