From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] gdbm: use full qualified permissions for chmod operations
Date: Thu, 13 Jan 2011 19:26:07 -0800 [thread overview]
Message-ID: <4D2FC24F.8000700@gmail.com> (raw)
In-Reply-To: <1294929135-25911-1-git-send-email-enrico.scholz@sigma-chemnitz.de>
On 1/13/2011 6:32 AM, Enrico Scholz wrote:
> From: Enrico Scholz<enrico.scholz@informatik.tu-chemnitz.de>
>
> An umask of 022 can cause 'chmod' to fail in a way like
>
> | $ chmod -w X
> | chmod: X: new permissions are r--rw-r--, not r--r--r--
>
> It is better to specify 'a-w' because chmod is not affected by the
> umask then and changes all permission bits.
>
> Signed-off-by: Enrico Scholz<enrico.scholz@sigma-chemnitz.de>
Acked-by: Khem Raj <raj.khem@gmail.com>
> ---
> recipes/gdbm/gdbm-1.8.3/chmod.patch | 23 +++++++++++++++++++++++
> recipes/gdbm/gdbm_1.8.3.bb | 3 ++-
> 2 files changed, 25 insertions(+), 1 deletions(-)
> create mode 100644 recipes/gdbm/gdbm-1.8.3/chmod.patch
>
> diff --git a/recipes/gdbm/gdbm-1.8.3/chmod.patch b/recipes/gdbm/gdbm-1.8.3/chmod.patch
> new file mode 100644
> index 0000000..11c65d9
> --- /dev/null
> +++ b/recipes/gdbm/gdbm-1.8.3/chmod.patch
> @@ -0,0 +1,23 @@
> +With an umask of 022 the build might fail with
> +
> +| chmod -w gdbm.h
> +| chmod: gdbm.h: new permissions are r--rw----, not r--r-----
> +| make: *** [gdbm.h] Error 1
> +
> +Index: gdbm-1.8.3/Makefile.in
> +===================================================================
> +--- gdbm-1.8.3.orig/Makefile.in
> ++++ gdbm-1.8.3/Makefile.in
> +@@ -167,10 +167,10 @@ libgdbm_compat.la: $(C_LOBJS) gdbm.h
> + gdbm.h: gdbm.proto gdbmerrno.h gdbm.proto2
> + rm -f gdbm.h
> + cp $(srcdir)/gdbm.proto gdbm.h
> +- chmod +w gdbm.h
> ++ chmod u+w gdbm.h
> + grep _ $(srcdir)/gdbmerrno.h>> gdbm.h
> + cat $(srcdir)/gdbm.proto2>> gdbm.h
> +- chmod -w gdbm.h
> ++ chmod a-w gdbm.h
> +
> + testgdbm: testgdbm.o libgdbm.la @LIBOBJS@
> + $(LIBTOOL) $(CC) $(LDFLAGS) -o testgdbm testgdbm.o libgdbm.la @LIBOBJS@
> diff --git a/recipes/gdbm/gdbm_1.8.3.bb b/recipes/gdbm/gdbm_1.8.3.bb
> index 9c91ae9..24c541a 100644
> --- a/recipes/gdbm/gdbm_1.8.3.bb
> +++ b/recipes/gdbm/gdbm_1.8.3.bb
> @@ -8,7 +8,8 @@ PR = "r5"
>
> SRC_URI = "${GNU_MIRROR}/gdbm/gdbm-${PV}.tar.gz \
> file://makefile.patch \
> - file://libtool-mode.patch"
> + file://libtool-mode.patch \
> + file://chmod.patch"
>
> inherit autotools
>
prev parent reply other threads:[~2011-01-14 3:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 14:32 [PATCH] gdbm: use full qualified permissions for chmod operations Enrico Scholz
2011-01-14 3:26 ` Khem Raj [this message]
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=4D2FC24F.8000700@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-devel@lists.openembedded.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