From: Markus Elfring <Markus.Elfring@web.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Check handling of kernel build output directory
Date: Fri, 26 Oct 2007 21:25:14 +0200 [thread overview]
Message-ID: <ffteuq$n3b$1@ger.gmane.org> (raw)
In-Reply-To: <20071026190500.GA23480@uranus.ravnborg.org>
> So here you do not have a .config file in the directory: /usr/src/obj/linux/2.6.23.1/x86_64/adjusted
> So you are told to create one using some of the available methods.
The README contains the following description.
"...
"make oldconfig" Default all questions based on the contents of
your existing ./.config file and asking about
new config symbols.
"make silentoldconfig"
Like above, but avoids cluttering the screen
with questions already answered.
..."
I did not expect that there are more differences besides the "silence".
> The suggested way to fix it is to run "make mrproper"
I did that clean-up step.
> but in your case you would then delete all the output files of your vendor supplied kernel.
I hope not because I've setup symbolic links to point to the current release as far I know
instead of the release "2.6.22.9-0.4-default" that I am using at the moment.
> This is something internal make stuff that is irrelevant in this case.
It is relevant in my case if I want to use different output directories for parallel
builds from the same source directory.
Regards,
Markus
next prev parent reply other threads:[~2007-10-26 19:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 17:31 Check handling of kernel build output directory Markus Elfring
2007-10-26 17:36 ` Vegard Nossum
2007-10-26 18:40 ` Markus Elfring
2007-10-26 19:05 ` Markus Elfring
2007-10-27 11:32 ` Jan Engelhardt
2007-10-27 12:21 ` Sam Ravnborg
2007-10-26 19:05 ` Sam Ravnborg
2007-10-26 19:25 ` Markus Elfring [this message]
2007-10-26 19:47 ` Sam Ravnborg
2007-10-27 5:07 ` Markus Elfring
2007-10-27 7:23 ` Sam Ravnborg
2007-10-27 12:30 ` Markus Elfring
2007-10-27 16:00 ` Markus Elfring
2007-10-27 11:33 ` Jan Engelhardt
2007-10-27 12:41 ` Markus Elfring
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='ffteuq$n3b$1@ger.gmane.org' \
--to=markus.elfring@web.de \
--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