All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] ARCH=ppc vs powerpc
Date: Wed, 2 Apr 2008 18:41:54 +0200	[thread overview]
Message-ID: <20080402164154.GE9436@mx.loc> (raw)
In-Reply-To: <8763v071sq.fsf@macbook.be.48ers.dk>

On Wed, Apr 02, 2008 at 04:45:57PM +0200, Peter Korsgaard wrote:
>>>>>> "Guillaume" == Guillaume Dargaud <dargaud@lpsc.in2p3.fr> writes:
>
> Guillaume> Anyone care to comment on that:
> Guillaume> $ make ARCH=ppc linux26-menuconfig
> Guillaume> [ -f
> Guillaume> /home/guinevere/buildroot/project_build_ppc/genepy/linux-2.6.24/.config ] |
> Guillaume> | cp local/genepy/linux-2.6.24.config
> Guillaume> /home/guinevere/buildroot/project_build_pp
> Guillaume> c/genepy/linux-2.6.24/.config
> Guillaume> /usr/bin/make -j1 HOSTCC="/usr/bin/gcc" HOSTCFLAGS="" ARCH=powerpc
> Guillaume> [...]
>
> Guillaume> Why does ARCH change ?!?
>
>Because target/linux/Makefile.in uses KERNEL_ARCH for ARCH setting,
>and not what you have set ARCH to on the cmdline.
>
>KERNEL_ARCH is calculated in
>toolchain/kernel-headers/kernel-headers.mk - Notice that arch/ppc is
>deprecated, you should use arch/powerpc nowadays.

Somebody did IMHO the Wrong Thing by silently unset'ing ARCH in the
toplevel Makefile. The proper thing to do is either $(error ARCH is set)
or, preferably, check that $ARCH is clean via dependencies.sh
Silently unseting ARCH is error-prone and misleading (as you see).

  parent reply	other threads:[~2008-04-02 16:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-02 14:16 [Buildroot] ARCH=ppc vs powerpc Guillaume Dargaud
2008-04-02 14:45 ` Peter Korsgaard
2008-04-02 16:23   ` Guillaume Dargaud
2008-04-02 16:41   ` Bernhard Fischer [this message]
2008-04-03 12:09     ` Guillaume Dargaud
2008-04-03 12:24       ` Peter Korsgaard
2008-04-03 14:20         ` Guillaume Dargaud
2008-04-03 15:09           ` Peter Korsgaard
2008-04-03 15:34             ` Guillaume Dargaud
2008-04-04  8:03               ` Peter Korsgaard
2008-04-04  9:02                 ` Guillaume Dargaud
2008-04-04  9:37                   ` Peter Korsgaard
2008-04-04 10:28                     ` Guillaume Dargaud
2008-04-04 11:07                       ` Peter Korsgaard
2008-04-04 12:30                         ` Guillaume Dargaud
2008-04-04 13:37                           ` Peter Korsgaard
2008-04-04 14:10                           ` Bernhard Fischer
2008-04-04 14:18                             ` Peter Korsgaard
2008-04-04 16:00                             ` Guillaume Dargaud
2008-04-04 18:02                               ` Peter Korsgaard

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=20080402164154.GE9436@mx.loc \
    --to=rep.dot.nop@gmail.com \
    --cc=buildroot@busybox.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.