From: Roman Chertov <rchertov@cs.ucsb.edu>
To: buildroot@busybox.net
Subject: [Buildroot] uClibc kernel headers problem
Date: Tue, 20 Oct 2009 21:59:01 -0700 [thread overview]
Message-ID: <4ADE9515.5000905@cs.ucsb.edu> (raw)
In-Reply-To: <4ADE4D0C.7010101@cs.ucsb.edu>
I am starting to suspect that for whatever reason uClibc is not using
the cross compiler and is instead using the host compiler. I am just
curious on the typical debugging procedure for this. Thanks.
Roman Chertov wrote:
> I have untared a fresh copy of build root 2009.8. When I run make for
> the first time, there is an error regarding the absence of
> toolchain_build_arm/uClibc.config.arm and the process stops (see error
> log below). If I do 'touch toolchain_build_arm/uClibc.config.arm' then
> run make again, there is a series of questions which pertain to which
> configs should be used.
>
> I am using my own target/device. But that mainly defines the U-BOOT
> config variable (cs-e9302), and I don't have any uClibc configuration
> files in that directory. I am just curious if this is a bug or if I am
> doing something wrong.
>
> Roman
>
> Applying uClibc-0.9.30.1-unifdef-getline.patch using plaintext:
> patching file extra/scripts/unifdef.c
> touch
> /proj/tools/buildroot-2009.08/toolchain_build_arm/uClibc-0.9.30.1/.patched
> cp -f
> /proj/tools/buildroot-2009.08/toolchain_build_arm/uClibc.config.arm
> /proj/tools/buildroot-2009.08/toolchain_build_arm/uClibc-0.9.30.1/.oldconfig
>
> cp: cannot stat
> `/proj/tools/buildroot-2009.08/toolchain_build_arm/uClibc.config.arm':
> No such file or directory
>
> make: ***
> [/proj/tools/buildroot-2009.08/toolchain_build_arm/uClibc-0.9.30.1/.oldconfig]
> Error 1
>
>
> Roman Chertov wrote:
>> 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
>>
>> _______________________________________________
>> buildroot mailing list
>> buildroot at busybox.net
>> http://lists.busybox.net/mailman/listinfo/buildroot
>>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
next prev parent reply other threads:[~2009-10-21 4:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 16:42 [Buildroot] uClibc kernel headers problem Roman Chertov
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 [this message]
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=4ADE9515.5000905@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 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.