From: "Jérôme Pouiller" <jezz@sysmic.org>
To: buildroot@busybox.net
Subject: [Buildroot] udev 182: scsi/scsi.h not found
Date: Mon, 24 Feb 2014 11:42:47 +0100 [thread overview]
Message-ID: <1671860.tqfC9E0M9p@sagittea> (raw)
In-Reply-To: <5307AB0F.30602@gmail.com>
Hello,
On Friday 21 February 2014 20:37:51 Marco Trapanese wrote:
> Hi all!
> I'm still learning and I was able to fix several issue by myself.
> Anyway my first buildroot compilation is not completed yet!
>
> The building of udev 182 ends with the following error:
>
> src/ata_id/ata_id.c:32:23: fatal error: scsi/scsi.h: File o directory
> non esistente
> #include <scsi/scsi.h>
I already noticed this problem. It happends when linux-headers is rebuilt
after libc (during its installation, linux-headers remove include/scsi/).
You can simply rebuild your toolchain or just do a "make clean".
--
J?r?me Pouiller, Sysmic
Embedded Linux specialist
http://www.sysmic.fr
next prev parent reply other threads:[~2014-02-24 10:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 19:37 [Buildroot] udev 182: scsi/scsi.h not found Marco Trapanese
2014-02-21 21:01 ` Peter Korsgaard
2014-02-21 21:17 ` Marco Trapanese
2014-02-21 22:59 ` Thomas Petazzoni
2014-02-24 10:42 ` Jérôme Pouiller [this message]
2014-02-24 11:18 ` Marco Trapanese
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=1671860.tqfC9E0M9p@sagittea \
--to=jezz@sysmic.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