mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Jan Beulich <JBeulich@novell.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] slightly enhance cross builds
Date: Tue, 8 Nov 2005 00:04:26 +0100	[thread overview]
Message-ID: <20051107230426.GD10492@mars.ravnborg.org> (raw)
In-Reply-To: <436F5D96.76F0.0078.0@novell.com>

On Mon, Nov 07, 2005 at 01:58:46PM +0100, Jan Beulich wrote:
> This adds functionality to default CROSS_COMPILE to a sensible value
> when cross-building (so one doesn't always have to specify this on the
> make command line), as well as storing ARCH and SUBARCH in the
> Makefile
> generated when building outside of the source directory (so that
> subsequent make invocations don't have to always repeat these).

This patch introduce different behaviour with and without make O=
This will result on confusion and is bad.

The right approach is to come up with a patch that works in both cases.

	Sam

  parent reply	other threads:[~2005-11-07 23:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-07 12:58 Jan Beulich
2005-11-07 14:53 ` Alexey Dobriyan
2005-11-07 23:04 ` Sam Ravnborg [this message]
2005-11-08  7:50   ` Jan Beulich
2005-11-08 21:28     ` Sam Ravnborg

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=20051107230426.GD10492@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=JBeulich@novell.com \
    --cc=linux-kernel@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

Powered by JetHome