From: Joshua Brindle <method@manicmethod.com>
To: Manoj Srivastava <srivasta@golden-gryphon.com>
Cc: selinux@tycho.nsa.gov, Manoj Srivastava <srivasta@debian.org>
Subject: Re: [PATCH] [topic--exception-fix] exception.sh contains bashisms
Date: Fri, 27 Nov 2009 15:03:33 -0500 [thread overview]
Message-ID: <4B103095.6000607@manicmethod.com> (raw)
In-Reply-To: <1256052880-9147-1-git-send-email-srivasta@golden-gryphon.com>
Manoj Srivastava wrote:
> From: Manoj Srivastava<srivasta@debian.org>
>
> Hi folks,
>
> The script, src/exception.sh, contains so called bashisms
> (constructs not supported by POSIX, but present as bash
> extensions). This means when trying to build on systems where /bin/sh
> is not bash, the build fails with an error. This patch uses bash to
> run exception.sh. This bug affects a significant subset of Debian and
> Debian derivative machines.
>
> manoj
>
> Signed-off-by: Manoj Srivastava<srivasta@debian.org>
> ---
> libselinu/xsrc/Makefile | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/libselinux/src/Makefile b/libselinux/src/Makefile
> index 74b1e6a..d0fb0e3 100644
> --- a/libselinux/src/Makefile
> +++ b/libselinux/src/Makefile
> @@ -83,7 +83,7 @@ $(LIBSO): $(LOBJS)
> ln -sf $@ $(TARGET)
>
> selinuxswig_python_exception.i: ../include/selinux/selinux.h
> - sh exception.sh> $@
> + bash exception.sh> $@
>
> audit2why.lo: audit2why.c
> $(CC) $(CFLAGS) -I$(PYINC) -fPIC -DSHARED -c -o $@ $<
Merged in libselinux 2.0.90
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
prev parent reply other threads:[~2009-11-27 20:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 15:34 [PATCH] [topic--exception-fix] exception.sh contains bashisms Manoj Srivastava
2009-11-27 20:03 ` Joshua Brindle [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=4B103095.6000607@manicmethod.com \
--to=method@manicmethod.com \
--cc=selinux@tycho.nsa.gov \
--cc=srivasta@debian.org \
--cc=srivasta@golden-gryphon.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.