From: Pavel Roskin <proski@gnu.org>
To: buildroot@busybox.net
Subject: [Buildroot] Built mipsel cross-compiler error on buildroot
Date: Wed, 29 Nov 2006 00:31:55 -0500 [thread overview]
Message-ID: <1164778315.4016.99.camel@dv> (raw)
In-Reply-To: <b2ec5cad0611282111tabfe302ve509e5c15b859048@mail.gmail.com>
On Wed, 2006-11-29 at 13:11 +0800, Doug Brewer wrote:
> I tried to use buildroot snpashots(20061128) to build mipsel cross-compiler,
> I got the following errors;
> /home/brewer/buildroot/toolchain_build_mipsel/uClibc_dev//usr/include/asm/sigcon
> text.h:12:25: asm/sgidefs.h: No such file or directory
This looks like an inconsistency in the kernel headers.
asm/sigcontext.h is present, but asm/sgidefs.h is not (at least where
it's expected to be).
Make sure you have unifdef installed. Try varying the version of the
kernel headers (e.g if it's 2.4.x, try 2.6.x and vice versa). If it
doesn't help, try the released version of uClibc. Also try another
compiler version (I would start with gcc 4.1.1).
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2006-11-29 5:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 5:11 [Buildroot] Built mipsel cross-compiler error on buildroot Doug Brewer
2006-11-29 5:31 ` Pavel Roskin [this message]
2006-11-30 6:17 ` Doug Brewer
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=1164778315.4016.99.camel@dv \
--to=proski@gnu.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