From: Adrian Bunk <bunk@kernel.org>
To: "Antonio Ávila" <aavilagallego@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Error using "make KBUILD_OUTPUT=path" or "make O=path"
Date: Fri, 11 Apr 2008 16:00:56 +0300 [thread overview]
Message-ID: <20080411130056.GA3821@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <bdcb599c0804110538h6a9c0247vcfc0ae39dd55908a@mail.gmail.com>
On Fri, Apr 11, 2008 at 02:38:29PM +0200, Antonio Ávila wrote:
> First of all, I'd like to introduce myself, my name is Anthony and
> I've been using linux during the last 8 years.
> I have googled around and I haven't found anything so let's go to the question:
> It seems that when initializing either KBUILD_OUTPUT or O variables
> (make KBUILD_OUTPUT="../build/" ) there is a problem, the output is
> effectivly working, but the problem is that some files (.config) that
> has been generated at the begining of the make process, are later used
> and as a consecuence, the make is trying to read them as the file was
> created in the base path instead of $KBUILD_OUTPUT...
>
> Or maybe I'm completely wrong about the using of that variables... :)
> I've attached an output log of the error.
>
> More info:
> - The kernel has been configured
> - If I omit the O= or KBUILD_OUTPUT= initializations the kernel
> compiles wonderfull.
>...
You also have to give the O= to the make commandline when configuring
the kernel - this will put the .config to the right place.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-04-11 13:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bdcb599c0804110514y7f07bd6aqfc3cb9ce6f52b08b@mail.gmail.com>
2008-04-11 12:38 ` Antonio Ávila
2008-04-11 13:00 ` Adrian Bunk [this message]
2008-04-11 21:50 ` Antonio Ávila
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=20080411130056.GA3821@cs181133002.pp.htv.fi \
--to=bunk@kernel.org \
--cc=aavilagallego@gmail.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
all inboxes | Powered by JetHome®