All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Zick" <lkml@morethan.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Robert P. J. Day" <rpjday@crashcourse.ca>,
	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 06:35:50 -0500	[thread overview]
Message-ID: <200905230635.52650.lkml@morethan.org> (raw)
In-Reply-To: <200905231322.16154.arnd@arndb.de>

On Sat May 23 2009, Arnd Bergmann wrote:
> 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.
>

With the note to set ARCH='<whatever>' either in the environment
or on the command line beforehand.
Sort of a "belt and suspenders" suggestion.

Mike 
> 	Arnd <><
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 
> 



  reply	other threads:[~2009-05-23 11:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-22 16:31 "make config" to another architecture doesn't relink include/asm Robert P. J. Day
2009-05-22 18:45 ` Bill Davidsen
2009-05-22 19:36   ` Robert P. J. Day
2009-05-23 11:22 ` Arnd Bergmann
2009-05-23 11:35   ` Michael S. Zick [this message]
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=200905230635.52650.lkml@morethan.org \
    --to=lkml@morethan.org \
    --cc=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 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.