Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] ARCH=ppc vs powerpc
Date: Thu, 03 Apr 2008 17:09:38 +0200	[thread overview]
Message-ID: <87bq4r0ybx.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <0e8d01c89595$e3482140$f52f9e86@LPSC0173W> (Guillaume Dargaud's message of "Thu\, 3 Apr 2008 16\:20\:32 +0200")

>>>>> "Guillaume" == Guillaume Dargaud <dargaud@lpsc.in2p3.fr> writes:

Hi,

 Guillaume> Deprecated or not, various info I have insist that I
 Guillaume> should use ARCH=ppc If I try:
 >> 
 Guillaume> $ make ARCH=ppc KERNEL_ARCH=ppc
 >> 
 >> That won't work as various other parts (E.G. kernel headers depends on
 >> KERNEL_ARCH=powerpc

 Guillaume> So how is one supposed to understand the 'use the
 Guillaume> ARCH=ppc' branch for Xilinx compilation ?!?

I'm not following you - ARCH=ppc is a kernel thing, it doesn't have
anything to do with buildroot.

 Guillaume> This morning I restarted from stratch to try to solve
 Guillaume> those ARCH vs KERNEL_ARCH issues, and now I've figured out
 Guillaume> that I can't even compile anything anymore (with the same
 Guillaume> .config files as before):

 Guillaume> $ make ARCH=ppc
 Guillaume> [...]
 Guillaume> checking whether we are cross compiling... no
 Guillaume> [...]

 Guillaume> I'm...lost and confused.

Don't set ARCH or KERNEL_ARCH on the buildroot command line, only use
it when you are compiling a kernel (outside buildroot).

 >> I normally don't compile my (ppc) kernels within buildroot. First
 >> create your rootfs and cross compiler with buildroot and then use it
 >> to compile the kernel manually (E.G. add
 >> build_powerpc/staging_dir/usr/bin to your path).

 Guillaume> OK, I think that's the straw that broke the camel's
 Guillaume> back. After a totally wasted month I'm gonna go do
 Guillaume> something else, like try OpenEmbedded or ELDK.

Suit yourself, but buildroot with Xilinx/ARCH=ppc kernels works (I use
it myself).

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2008-04-03 15:09 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
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 [this message]
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=87bq4r0ybx.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox