public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: "make config" to another architecture doesn't relink include/asm
Date: Fri, 22 May 2009 15:36:17 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.00.0905221533550.5168@localhost.localdomain> (raw)
In-Reply-To: <4A16F2C9.1000600@tmr.com>

On Fri, 22 May 2009, Bill Davidsen wrote:

> Robert P. J. Day wrote:
> >   should i expect this with a fresh tree on x86_64?
> >
> > $ make distclean
> > $ make defconfig
> > $ make modules_prepare
> > $ ls -l include/asm
> > lrwxrwxrwx    1 rpjday rpjday     7 2009-05-22 12:24 asm -> asm-x86
> > $
> >
> >   oh, wait, i changed my mind, i want to switch architectures so start
> > over:
> >
> > $ make clean
> > $ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- omap3_beagle_defconfig
> > $ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- uImage
> > scripts/kconfig/conf -s arch/arm/Kconfig
> > include/config/auto.conf:15:warning: symbol value
> > 'arch/x86/configs/x86_64_defconfig' invalid for ARCH_DEFCONFIG
> >   CHK     include/linux/version.h
> > make[1]: `include/asm-arm/mach-types.h' is up to date.
> >   CHK     include/linux/utsrelease.h
> >   UPD     include/linux/utsrelease.h
> > ERROR: the symlink include/asm points to asm-x86 but asm-arm was expected
> >        set ARCH or save .config and run 'make mrproper' to fix it
> > make: *** [include/asm] Error 1
> >
> > $ ls -l include/asm
> > lrwxrwxrwx 1 rpjday rpjday 7 2009-05-22 12:24 include/asm -> asm-x86
> > $
> >
> >   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?
> >
> Does "make distclean" (or maybe "make mrproper") get you to really clean
> status?

  yes, but the issue is that "make clean" should still have the same
effect WRT to resetting that symlink, especially since the error
message tells the user to set ARCH and the user (i.e., me) *has* set
ARCH.  put another way, if i do a config with a specific setting for
ARCH, it seems non-intuitive to *not* reset the symlink representing
that architecture.

rday
--

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

        Linux Consulting, Training and Annoying Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Linked In:                             http://www.linkedin.com/in/rpjday
Twitter:                                       http://twitter.com/rpjday
========================================================================

  reply	other threads:[~2009-05-22 19:37 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 [this message]
2009-05-23 11:22 ` Arnd Bergmann
2009-05-23 11:35   ` 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=alpine.LFD.2.00.0905221533550.5168@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --cc=davidsen@tmr.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