mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Sam Ravnborg" <sam@ravnborg.org>
Cc: "Randy Dunlap" <randy.dunlap@oracle.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] decodecode: use cross-compiler/toolchain if defined
Date: Mon, 19 May 2008 22:23:02 +0200	[thread overview]
Message-ID: <19f34abd0805191323o17e9411btde5a0fa02597d7fc@mail.gmail.com> (raw)
In-Reply-To: <20080519190256.GA24599@uranus.ravnborg.org>

On Mon, May 19, 2008 at 9:02 PM, Sam Ravnborg <sam@ravnborg.org> wrote:
> On Mon, May 12, 2008 at 03:52:42PM +0200, Vegard Nossum wrote:
>>
>> From 75166add6121dbda4fad2e197d4fe6525dee580c Mon Sep 17 00:00:00 2001
>> From: Vegard Nossum <vegard.nossum@gmail.com>
>> Date: Mon, 12 May 2008 15:36:38 +0200
>> Subject: [PATCH] decodecode: use cross-compiler/toolchain if defined
>>
>> From the Makefile: "CROSS_COMPILE specify [sic] the prefix used for all
>> executables used".
>>
>> This is also very useful for decoding oopses on other archs than the
>> native one, so it seems natural to have it in the decodecode script as
>> well.
>
> I agree with the intent of this patch.
> But as it is my experience that most people use
> CROSS_COMPILE on the commandline and not as an
> environmnet variable most will not benefit from this patch.

I do use it on the command line too, it just has to come in front of
the 'make' command:

CROSS_COMPILE=x86_64-linux-unknown-gnu- make

> We should as a minimum document this use of decodecode where we
> document its usage today (oops-tracing.txt).
>
> We could also make it a Makefile target thus it is a bit
> more natural to supply the typical Makefile parameters?
>
> Please rework one way or the other.

I can try to do both those, however I don't see how this patch fails
to be an improvement in any case.

Thanks for the feedback.


Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036

      reply	other threads:[~2008-05-19 20:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-12 13:52 Vegard Nossum
2008-05-19 19:02 ` Sam Ravnborg
2008-05-19 20:23   ` Vegard Nossum [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=19f34abd0805191323o17e9411btde5a0fa02597d7fc@mail.gmail.com \
    --to=vegard.nossum@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=sam@ravnborg.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

all inboxes | Powered by JetHome®