From: Andrew Morton <akpm@linux-foundation.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch 2/3] ia64: don't assume that unwcheck.py is executable
Date: Thu, 06 Dec 2007 08:03:00 +0000 [thread overview]
Message-ID: <20071206000300.4138e247.akpm@linux-foundation.org> (raw)
In-Reply-To: <200712052232.lB5MWE3W028394@imap1.linux-foundation.org>
On Thu, 6 Dec 2007 07:45:57 +0000 Christoph Hellwig <hch@infradead.org> wrote:
> On Wed, Dec 05, 2007 at 03:17:33PM -0800, Andrew Morton wrote:
> > > > - -$(Q)READELF=$(READELF) $(srctree)/arch/ia64/scripts/unwcheck.py $<
> > > > + -$(Q)READELF=$(READELF) $(CONFIG_SHELL) $(srctree)/arch/ia64/scripts/unwcheck.py $<
> > >
> > > unwcheck.py is not a shell script.
> > >
> >
> > Oh well, whatever. Please treat this as a bug report.
> >
> > ie: someone please fix it.
>
> Best would be to get rid of python. Having another scripting language
> as built requirement, and that only on ia64 doesn't sound like a
> particularly good idea.
It's probably not a big deal - especially as ia64 kernels are presuably not
as likely to be built in wild and whacky enviroments like some other
architectures.
afacit the script is optional anyway - it "check and verifies unwind info".
If python isn't available, just skip it..
next prev parent reply other threads:[~2007-12-06 8:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 22:32 [patch 2/3] ia64: don't assume that unwcheck.py is executable akpm
2007-12-05 23:06 ` Andreas Schwab
2007-12-05 23:17 ` Andrew Morton
2007-12-05 23:25 ` Luck, Tony
2007-12-05 23:40 ` Andrew Morton
2007-12-05 23:43 ` Andreas Schwab
2007-12-06 7:45 ` Christoph Hellwig
2007-12-06 8:03 ` Andrew Morton [this message]
2007-12-06 21:34 ` Sam Ravnborg
2007-12-06 22:05 ` Luck, Tony
2007-12-06 22:28 ` Sam Ravnborg
2007-12-06 22:44 ` Luck, Tony
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=20071206000300.4138e247.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-ia64@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