From: Eli Zaretskii <eliz@gnu.org>
To: Van Ly <van.ly@sdf.org>
Cc: rgm@gnu.org, 53534@debbugs.gnu.org
Subject: bug#53534: 28.0.91; on netbsd 'gmake install' outputs 'find: chown: No such file or directory'
Date: Wed, 26 Jan 2022 17:14:37 +0200 [thread overview]
Message-ID: <83y232fs0y.fsf@gnu.org> (raw)
In-Reply-To: <34ea3c43-b527-eae2-9f21-404317ed6f3@SDF.ORG> (message from Van Ly on Wed, 26 Jan 2022 15:06:18 +0000 (UTC))
> Date: Wed, 26 Jan 2022 15:06:18 +0000 (UTC)
> From: Van Ly <van.ly@sdf.org>
> cc: Glenn Morris <rgm@gnu.org>, 53534@debbugs.gnu.org
>
> > In any case, I don't see any serious problem in the reported behavior,
> > those are just warnings AFAIU.
> >
>
> I hesistated before reporting this bug, thinking my storage device
> had wornout and was spewing the error. I got around to fscking then
> reported this. A better looking log trace collapses and counts the
> repeating line and explains chown is not on the path is a help to
> know. The autogen.sh script can detect chown is not on the path,
> right?
That won't help, because AFAIU when you use sudo, it changes your PATH
accordingly.
next prev parent reply other threads:[~2022-01-26 15:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 23:03 bug#53534: 28.0.91; on netbsd 'gmake install' outputs 'find: chown: No such file or directory' Van Ly
2022-01-26 3:32 ` Eli Zaretskii
2022-01-26 4:26 ` Glenn Morris
2022-01-26 12:47 ` Eli Zaretskii
2022-01-26 15:06 ` Van Ly
2022-01-26 15:14 ` Eli Zaretskii [this message]
2022-01-26 17:51 ` Glenn Morris
2022-01-26 18:02 ` Glenn Morris
2022-01-27 2:22 ` Glenn Morris
2022-01-27 7:12 ` Eli Zaretskii
2022-02-02 18:21 ` Glenn Morris
2022-02-02 18:34 ` Glenn Morris
2022-02-02 19:22 ` Eli Zaretskii
2022-02-02 18:57 ` Eli Zaretskii
2022-01-26 18:04 ` Van Ly
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83y232fs0y.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=53534@debbugs.gnu.org \
--cc=rgm@gnu.org \
--cc=van.ly@sdf.org \
/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.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).