Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Build failed with Error 1 and Error 2
Date: Wed, 21 Jul 2010 08:52:35 +0200	[thread overview]
Message-ID: <20100721085235.7f682c11@surf> (raw)
In-Reply-To: <29222293.post@talk.nabble.com>

Hello,

On Tue, 20 Jul 2010 23:23:50 -0700 (PDT)
JNY <jny0@hotmail.com> wrote:

> After many hours (around 4) of running, my buildroot ultimately
> failed with the following errors, any ideas?

Could you please post your .config ? Unless you've enabled dozens and
dozens of packages and have a slow machine, a build of four hours looks
a bit suspicious. If you're beginning with Buildroot, I would first
recommend you to build a basic system with just Busybox enabled, and
see how it works, before going on with building a more complicated
system.

> /home/JB/Apps/buildroot-2010.05/output/staging/usr/include/scsi/scsi.h:148:
> error: expected specifier-qualifier-list before 'u8'
> /home/JB/Apps/buildroot-2010.05/output/staging/usr/include/scsi/scsi.h:
> In function 'scsi_varlen_cdb_length':
> /home/JB/Apps/buildroot-2010.05/output/staging/usr/include/scsi/scsi.h:159:
> error: 'struct scsi_varlen_cdb_hdr' has no member named
> 'additional_cdb_length'

Yes, this is a breakage in the kernel headers. The
linux-*-scsi-use-__uX-types-for-headers-exported-to-user-space.patch
patch didn't get applied to your kernel headers when building the
toolchain.

Can you please post your .config so that we know which version of the
kernel headers you're using ?

Thanks,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2010-07-21  6:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-21  6:23 [Buildroot] Build failed with Error 1 and Error 2 JNY
2010-07-21  6:52 ` Thomas Petazzoni [this message]
2010-07-21  7:32   ` JNY
2010-07-21  9:38     ` Thomas Petazzoni
2010-07-21 12:44       ` JNY

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=20100721085235.7f682c11@surf \
    --to=thomas.petazzoni@free-electrons.com \
    --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