From: Guillaume Dargaud <dargaud@lpsc.in2p3.fr>
To: buildroot@busybox.net
Subject: [Buildroot] ARCH=ppc vs powerpc
Date: Thu, 3 Apr 2008 14:09:03 +0200 [thread overview]
Message-ID: <0ddc01c89583$84ecb960$f52f9e86@LPSC0173W> (raw)
In-Reply-To: 20080402164154.GE9436@mx.loc
>>> 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).
So, how does one go to compile for a Xilinx ppc ?
Deprecated or not, various info I have insist that I should use ARCH=ppc
If I try:
$ make ARCH=ppc KERNEL_ARCH=ppc
Checking build system dependencies:
BUILDROOT_DL_DIR clean: Ok
CC clean: Ok
CXX clean: Ok
CPP clean: Ok
CFLAGS clean: Ok
INCLUDES clean: Ok
CXXFLAGS clean: Ok
LD_LIBRARY_PATH sane: Ok
which installed: Ok
sed works: Ok (/bin/sed)
GNU make version '3.81': Ok
C compiler '/usr/bin/gcc'
C compiler version '3.4.6': Ok
C++ compiler '/usr/bin/g++'
C++ compiler version '3.4.6': Ok
bison installed: Ok
flex installed: Ok
gettext installed: Ok
makeinfo installed: Ok
Build system dependencies: Ok
rm -rf /home/guinevere/buildroot/project_build_ppc/genepy/buildroot-config
mkdir -p /home/guinevere/buildroot/project_build_ppc/genepy
cp -dpRf package/config/buildroot-config
/home/guinevere/buildroot/project_build_ppc/genepy/buildroot-config
(cd /home/guinevere/buildroot/toolchain_build_ppc/linux-2.6.24; \
/usr/bin/make -j1 ARCH=ppc \
HOSTCC="/usr/bin/gcc" HOSTCFLAGS="" \
HOSTCXX="/usr/bin/g++" \
INSTALL_HDR_PATH=/home/guinevere/buildroot/toolchain_build_ppc/linux
headers_install; \
)
make[1]: Entering directory
`/home/guinevere/buildroot/toolchain_build_ppc/linux-2.6.24'
CHK include/linux/version.h
*** Error: Headers not exportable for this architecture (ppc)
make[1]: *** [headers_install] Error 1
make[1]: Leaving directory
`/home/guinevere/buildroot/toolchain_build_ppc/linux-2.6.24'
make: *** [/home/guinevere/buildroot/toolchain_build_ppc/linux/.configured]
Error 2
Am I supposed to try and edit some of the makefile to get them to use
ARCH=ppc for the kernel ? I can't believe I'm the first one to use buildroot
on a Xilinx board, so what am I doing wrong...?
--
Guillaume Dargaud
http://www.gdargaud.net/
next prev parent reply other threads:[~2008-04-03 12: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 [this message]
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='0ddc01c89583$84ecb960$f52f9e86@LPSC0173W' \
--to=dargaud@lpsc.in2p3.fr \
--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