From: Roman Chertov <rchertov@cs.ucsb.edu>
To: buildroot@busybox.net
Subject: [Buildroot] uClibc kernel headers problem
Date: Tue, 20 Oct 2009 09:42:38 -0700 [thread overview]
Message-ID: <4ADDE87E.1030601@cs.ucsb.edu> (raw)
Hello,
I am using the latest build root release and I am trying to build a tool
chain for CS-e9302 board which has an ARM chip. I want to use the
2.6.24.7 Linux kernel (I patched it to support click modular router). I
patched that kernel and u-boot 1.3.3 with patches from
http://dev.ivanov.eu/projects/cs-e9302/ to enable the board support. I
then renamed the tar.bz2 files into file names that buildroot supports
in the menuconfig (linux-2.6.24.tar.bz2 kernel and
u-boot-2009.06.tar.bz2) and placed the files into the dl directory.
My current trouble is with uClibc 0.9.30.1. In the buildroot menuconfig
I specified that I want to build the entire Linux kernel, so as far as I
understand there is no need to use the precompiled headers option. When
I build the tool chain, it all works up to uClibc. I get the following
error "cc1: error: unrecognized command line option "-mbig-endian"". I
have included the output log down below. I would appreciate any help
with this.
Thanks,
Roman
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
which installed: Ok
sed works: Ok (/bin/sed)
GNU make version '3.81': Ok
C compiler '/usr/lib/ccache/gcc'
C compiler version '4.4.1': Ok
C++ compiler '/usr/lib/ccache/g++'
C++ compiler version '4.4.1': Ok
awk installed: Ok
bash installed: Ok
bison installed: Ok
flex installed: Ok
gettext installed: Ok
makeinfo installed: Ok
Build system dependencies: Ok
rm -rf
/proj/tools/buildroot-2009.08/project_build_arm/uclibc/buildroot-config
mkdir -p /proj/tools/buildroot-2009.08/project_build_arm/uclibc
cp -dpRf package/config/buildroot-config
/proj/tools/buildroot-2009.08/project_build_arm/uclibc/buildroot-config
/usr/bin/make -j1 -C
/proj/tools/buildroot-2009.08/toolchain_build_arm/uClibc-0.9.30.1 \
PREFIX= \
DEVEL_PREFIX=/ \
RUNTIME_PREFIX=/ \
HOSTCC="/usr/lib/ccache/gcc" \
all
make[1]: Entering directory
`/proj/tools/buildroot-2009.08/toolchain_build_arm/uClibc-0.9.30.1'
GEN include/bits/sysnum.h
cc1: error: unrecognized command line option "-mbig-endian"
cc1: error: unrecognized command line option "-mbig-endian"
ERROR: Could not generate syscalls.
Make sure that you have proper kernel headers.
Your .config in KERNEL_HEADERS="" was set to:
/usr/include/
make[1]: *** [include/bits/sysnum.h] Error 1
make[1]: Leaving directory
`/proj/tools/buildroot-2009.08/toolchain_build_arm/uClibc-0.9.30.1'
make: ***
[/proj/tools/buildroot-2009.08/toolchain_build_arm/uClibc-0.9.30.1/lib/libc.a]
Error 2
next reply other threads:[~2009-10-20 16:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 16:42 Roman Chertov [this message]
2009-10-20 23:37 ` [Buildroot] precompiled kernel headers Roman Chertov
2009-10-21 12:15 ` Peter Korsgaard
2009-10-21 15:12 ` Roman Chertov
2009-10-21 15:41 ` Peter Korsgaard
2009-10-20 23:51 ` [Buildroot] uClibc kernel headers problem Roman Chertov
2009-10-21 4:59 ` Roman Chertov
2009-10-21 8:50 ` Bernhard Reutner-Fischer
2009-10-21 20:02 ` Roman Chertov
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=4ADDE87E.1030601@cs.ucsb.edu \
--to=rchertov@cs.ucsb.edu \
--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