All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roman Chertov <rchertov@cs.ucsb.edu>
To: buildroot@busybox.net
Subject: [Buildroot] uClibc kernel headers problem
Date: Wed, 21 Oct 2009 13:02:14 -0700	[thread overview]
Message-ID: <4ADF68C6.7030806@cs.ucsb.edu> (raw)
In-Reply-To: <20091021085047.GA23642@mx.loc>

> 
> if the paths in the tarballs don't match the name of the tarball and the
> version in the BR config then this will not work.
> I've sent a patch to the list a couple of days ago where you can set the
> kernel version manually to ease this particular thing, fyi.
> This and a handful of other patches are still not applied yet, though.

I changed the path names by hand so that linux-2.6.24.7.tar.bz2 is
linux-2.6.24.tar.bz2 and is extracted into a 2.6.24 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.
> 
> How did you configure BR?

I specified that I have an ARM processor with EABI.  For libc, I used
the default 0.9.30.1.  For the actual device, I had to make my own entry
in device.  I copied the following into the Makefile.in

UCLIBC_CONFIG_FILE=$(TOOL_BUILD_DIR)/uClibc.config.$(ARCH) from one of
the device directories.  Once, I commented that out, the problem
disappeared.

Roman


> 
>>  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/
> 
> Even if you build on an arm box this is incorrect.
> I suggest you start from a fresh BR config:
> you at box:buildroot $ rm -f .config ; make menuconfig
> 

      reply	other threads:[~2009-10-21 20:02 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
2009-10-21  8:50 ` Bernhard Reutner-Fischer
2009-10-21 20:02   ` Roman Chertov [this message]

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=4ADF68C6.7030806@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.