From: Christopher Li <sparse@chrisli.org>
To: Dan McGee <dan@archlinux.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [PATCH] Makefile: fix permissions mixup on install
Date: Tue, 27 Oct 2009 21:05:18 -0700 [thread overview]
Message-ID: <70318cbf0910272105p60bb4623td07c870c0a9bfb4a@mail.gmail.com> (raw)
In-Reply-To: <1256690768-2577-1-git-send-email-dan@archlinux.org>
On Tue, Oct 27, 2009 at 5:46 PM, Dan McGee <dan@archlinux.org> wrote:
> `install` by default uses 755 permissions; for everything but executables we
> want to use 644 permissions.
So far so good.
> -define INSTALL_CMD
> +define INSTALL_PROG
I rename it to INSTALL_EXEC and INSTALL_FILE respectively.
> $(Q)$(QUIET_INST_SH)install -v $1 $(DESTDIR)$2/$1 || exit 1;
> +endef
Your patch remove a newline which is critical here. It is very subtle when
using it inside a $(foreach ) loop. $(foreach ) blindly concatenate loop both.
'@' only have special meaning after a newline. I get "@echo" command
not found without this new line.
The others look good. I apply a version with the rename and newline
changes in chrisl branch. Let me know that works for you or not.
If you have other feed back of the change, I can still change it.
Thanks
Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-10-28 4:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 0:37 'make install' target issues Dan McGee
2009-10-28 0:46 ` [PATCH] Makefile: fix permissions mixup on install Dan McGee
2009-10-28 4:05 ` Christopher Li [this message]
2009-10-28 3:04 ` 'make install' target issues Christopher Li
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=70318cbf0910272105p60bb4623td07c870c0a9bfb4a@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=dan@archlinux.org \
--cc=linux-sparse@vger.kernel.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.
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).