From: Arnd Bergmann <arnd@arndb.de>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-kbuild@vger.kernel.org, sam@ravnborg.org
Subject: Re: "make config" to another architecture doesn't relink include/asm
Date: Sat, 23 May 2009 13:22:15 +0200 [thread overview]
Message-ID: <200905231322.16154.arnd@arndb.de> (raw)
In-Reply-To: <alpine.LFD.2.00.0905221219500.13933@localhost.localdomain>
On Friday 22 May 2009, Robert P. J. Day wrote:
> shouldn't it be sufficient that, if i do another "make ??_defconfig"
> to another architecture, all traces of the previous configure are
> erased and include/asm should be relinked automatically?
In 2.6.30, the symlink is finally no longer needed, so maybe we
should simply drop it to solve this problem as well.
Arnd <><
next parent reply other threads:[~2009-05-23 11:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LFD.2.00.0905221219500.13933@localhost.localdomain>
2009-05-23 11:22 ` Arnd Bergmann [this message]
2009-05-23 11:35 ` "make config" to another architecture doesn't relink include/asm Michael S. Zick
2009-05-23 14:11 ` Robert P. J. Day
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=200905231322.16154.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
--cc=sam@ravnborg.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