From: "Andreas Färber" <afaerber@suse.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Stefan Weil <weil@mail.berlios.de>,
Jan Kiszka <jan.kiszka@web.de>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RFC][PATCH] signrom: Speed up checksum calculation
Date: Tue, 24 Jan 2012 10:43:16 +0100 [thread overview]
Message-ID: <4F1E7D34.3000501@suse.de> (raw)
In-Reply-To: <4F1DC51C.5030409@codemonkey.ws>
Am 23.01.2012 21:37, schrieb Anthony Liguori:
> On 01/23/2012 02:32 PM, Jan Kiszka wrote:
>> On 2012-01-23 21:08, Anthony Liguori wrote:
>>> I've been thinking that we could potentially rewrite a large chunk
>>> (all?) of configure in python too since we have such a hard
>>> dependency now.
>>
>> Sounds almost like a GSoC project.
>
> That's a good idea!
Having a signrom.py, driven by configure or make, is fine.
But configure should be able to run anywhere and at least report what's
missing. #!/bin/sh is the standard, highly compatible mechanism among
Unices, Posices and more to do just that. Python on the other hand is
either /usr/bin/python or /usr/bin/env python, which both don't work on
systems without /usr/bin for starters.
So please not all of configure, at least detect and/or allow to
overwrite the python path.
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-01-24 9:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 18:38 [Qemu-devel] [RFC][PATCH] signrom: Speed up checksum calculation Jan Kiszka
2012-01-23 19:16 ` Stefan Weil
2012-01-23 19:19 ` Jan Kiszka
2012-01-23 19:25 ` Stefan Weil
2012-01-23 20:08 ` Anthony Liguori
2012-01-23 20:32 ` Jan Kiszka
2012-01-23 20:37 ` Anthony Liguori
2012-01-23 21:32 ` Stefan Weil
2012-01-24 9:43 ` Andreas Färber [this message]
2012-01-24 8:18 ` Paolo Bonzini
2012-01-24 10:18 ` Christoph Egger
2012-01-24 8:39 ` Paolo Bonzini
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=4F1E7D34.3000501@suse.de \
--to=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=jan.kiszka@web.de \
--cc=qemu-devel@nongnu.org \
--cc=weil@mail.berlios.de \
/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).