From: Andreas Schwab <schwab@suse.de>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch 2/3] ia64: don't assume that unwcheck.py is executable
Date: Wed, 05 Dec 2007 23:43:50 +0000 [thread overview]
Message-ID: <je63zcogg9.fsf@sykes.suse.de> (raw)
In-Reply-To: <200712052232.lB5MWE3W028394@imap1.linux-foundation.org>
Andrew Morton <akpm@linux-foundation.org> writes:
> On Thu, 06 Dec 2007 00:06:14 +0100
> Andreas Schwab <schwab@suse.de> wrote:
>
>> akpm@linux-foundation.org writes:
>>
>> > diff -puN arch/ia64/Makefile~ia64-dont-assume-that-unwcheckpy-is-executable arch/ia64/Makefile
>> > --- a/arch/ia64/Makefile~ia64-dont-assume-that-unwcheckpy-is-executable
>> > +++ a/arch/ia64/Makefile
>> > @@ -77,7 +77,7 @@ vmlinux.gz: vmlinux
>> > $(Q)$(MAKE) $(build)=$(boot) $@
>> >
>> > unwcheck: vmlinux
>> > - -$(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.
s/$(CONFIG_SHELL)/python/
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2007-12-05 23:43 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 [this message]
2007-12-06 7:45 ` Christoph Hellwig
2007-12-06 8:03 ` Andrew Morton
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=je63zcogg9.fsf@sykes.suse.de \
--to=schwab@suse.de \
--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