mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "John Stoffel" <john@stoffel.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>, Alain Knaff <alain@knaff.lu>,
	Tvrtko Ursulin <tvrtko.ursulin@sophos.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: 2.6.33-rc1: LZMA kernel fails to decompress
Date: Mon, 28 Dec 2009 17:15:41 -0500	[thread overview]
Message-ID: <19257.11789.248634.904859@stoffel.org> (raw)
In-Reply-To: <4B390836.70100@zytor.com>

>>>>> "H" == H Peter Anvin <hpa@zytor.com> writes:

H> On 12/27/2009 12:19 PM, Michael Tokarev wrote:
>> 
>> What I think should be done here is to revert my patch (that replaces
>> /bin/echo with printf, so that /bin/echo will be used) and test the
>> real solution, which is to stop doing all this hackery altogether,
>> and calculate the size the right way instead.  Sam already posted a
>> possible solution, and it seems to be correct.
>> 

H> Yes, but it moves the calculation from generic to x86-specific code,
H> which makes it problematic.

H> I never figured out how to make a generic rule in Kbuild (unlike in
H> standard GNU make) depend on a helper application, but doing a
H> helper application for this is probably the sane thing.

H> Either this, or use Perl, which handles this kind of crap sanely.
H> I'm really less than half joking.

Yeah, I've never understood this mania to purge the build process of
any and all use of perl.  If anything, it should *all* be perl so as
to simplify the maint since it's all the same, no matter where you run
perl.

And for those who say "but I need to compile the kernel in my
miniscule, locked down environment" my reply is "cross-compile".

Heck, even pure C code would do the trick here.

John

  reply	other threads:[~2009-12-28 22:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-21 16:43 Tvrtko Ursulin
2009-12-21 16:45 ` Tvrtko Ursulin
2009-12-21 21:43 ` Michael Tokarev
2009-12-27 18:50   ` Alain Knaff
2009-12-27 20:19     ` Michael Tokarev
2009-12-28 19:34       ` H. Peter Anvin
2009-12-28 22:15         ` John Stoffel [this message]
2009-12-28 23:05           ` H. Peter Anvin

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=19257.11789.248634.904859@stoffel.org \
    --to=john@stoffel.org \
    --cc=alain@knaff.lu \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    --cc=torvalds@linux-foundation.org \
    --cc=tvrtko.ursulin@sophos.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®