From: Sam Ravnborg <sam@ravnborg.org>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: lkml <linux-kernel@vger.kernel.org>, linux-kbuild@vger.kernel.org
Subject: Re: kbuild problem
Date: Thu, 1 Nov 2007 06:21:45 +0100 [thread overview]
Message-ID: <20071101052145.GA31445@uranus.ravnborg.org> (raw)
In-Reply-To: <20071031183900.46a0b529.rdunlap@xenotime.net>
On Wed, Oct 31, 2007 at 06:39:00PM -0700, Randy Dunlap wrote:
> Hi Sam,
>
> I have daily/nightly builds + test runs that use something like:
> (but more complicated than this)
>
> cp saved.config.file arch/$ARCH/config.default
> EXPORT KBUILD_DEFCONFIG=config.default
> make defconfig
KBUILD_DEFCONFIG is supposed to point out a file located in
arch/$(ARCH)/configs.
I assume you copy the file to that directory.
Browsing the changes to scripts/kconfig/Makefile
nothing says 'this is the bug' but I suggest you to look there
first of all.
I do not have -git2 and -git3 handy to do a diff between.
Sam
next prev parent reply other threads:[~2007-11-01 5:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-01 1:39 kbuild problem Randy Dunlap
2007-11-01 5:21 ` Sam Ravnborg [this message]
2007-11-01 17:11 ` Randy Dunlap
2007-11-01 17:59 ` Sam Ravnborg
-- strict thread matches above, loose matches on Subject: below --
2007-02-15 21:56 [2.6 patch] drivers/isdn/gigaset/: build asyncdata.o into the gigaset module Adrian Bunk
2007-02-16 0:17 ` Tilman Schmidt
2007-02-16 8:33 ` Adrian Bunk
2007-02-17 0:04 ` Kbuild problem (was: [2.6 patch] drivers/isdn/gigaset/: build asyncdata.o into the gigaset module) Tilman Schmidt
2007-02-17 10:52 ` Adrian Bunk
2007-02-17 18:36 ` Kbuild problem Tilman Schmidt
2007-02-18 5:22 ` Kai Germaschewski
2007-02-18 10:40 ` Adrian Bunk
2007-02-20 13:56 ` Tilman Schmidt
2007-02-20 14:12 ` Joerg Dorchain
2007-02-20 14:59 ` Adrian Bunk
2007-02-20 21:55 ` Tilman Schmidt
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=20071101052145.GA31445@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.