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, Roman Zippel <zippel@linux-m68k.org>
Subject: Re: [PATCH] slightly enhance cross builds
Date: Tue, 8 Nov 2005 22:28:00 +0100	[thread overview]
Message-ID: <20051108212800.GB8256@mars.ravnborg.org> (raw)
In-Reply-To: <437066EC.76F0.0078.0@novell.com>

On Tue, Nov 08, 2005 at 08:50:52AM +0100, Jan Beulich wrote:
> 
> Though I admit that I never build inside the source tree, I can't see
> what you apparently do. Where/how would the behavior differ? If you just
> mean the fact that in-source-tree builds will need to continue to
> specify ARCH/SUBARCH on the make command line, then of course yes, this
> is going to be different. But building in the source tree is a bad idea
> in general in my opinion, and hence I would view this as the price you
> pay.
That's anyway how most users builds kernel.

> Of course this information could be stored in a hidden file in the
> output tree (rather than in mkmakefile itself) if that's more
> desirable...
Plan has been to add this during *config step to .config.
But I have been sidetracked the few times I looked at it.

Having it as part of *config process is good because
- this is when you configure the kernel
- .config is a natural file to keep configuration within
- and then we have same functionality with and without O=...

	Sam

      reply	other threads:[~2005-11-08 21:27 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
2005-11-08  7:50   ` Jan Beulich
2005-11-08 21:28     ` Sam Ravnborg [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=20051108212800.GB8256@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=JBeulich@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zippel@linux-m68k.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®