From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] i2c-tools: Add i2c-dev.h to staging directory for userspace i2c drivers.
Date: Tue, 24 Sep 2013 18:55:15 +0300 [thread overview]
Message-ID: <20130924155515.GD4838@tarshish> (raw)
In-Reply-To: <20130924172041.57ec6b88@skate>
Hi Thomas,
On Tue, Sep 24, 2013 at 05:20:41PM +0200, Thomas Petazzoni wrote:
> On Tue, 24 Sep 2013 13:18:43 +0300, Jouko Nikula wrote:
> > +define I2C_TOOLS_INSTALL_STAGING_CMDS
> > + $(INSTALL) -D -m644 $(@D)/include/linux/i2c-dev.h $(STAGING_DIR)/usr/include/linux/
> > +endef
>
> This header is already part of the kernel headers, so it should already
> be part of the toolchain. Do you have a specific case where this header
> is missing?
This is a different header than the kernel one, although confusingly named
identically. On my Debian system the libi2c-dev package provides i2c-dev.h,
and diverts the kernel header to i2c-dev.h.kernel.
$ dpkg -S /usr/include/linux/i2c-dev.h
diversion by libi2c-dev from: /usr/include/linux/i2c-dev.h
diversion by libi2c-dev to: /usr/include/linux/i2c-dev.h.kernel
linux-libc-dev:amd64, libi2c-dev: /usr/include/linux/i2c-dev.h
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2013-09-24 15:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 10:18 [Buildroot] [PATCH] i2c-tools: Add i2c-dev.h to staging directory for userspace i2c drivers Jouko Nikula
2013-09-24 10:18 ` [Buildroot] [PATCH] Update config.guess to version 2013-06-10 Jouko Nikula
2013-09-24 10:27 ` Nikula Jouko
2013-09-24 15:20 ` [Buildroot] [PATCH] i2c-tools: Add i2c-dev.h to staging directory for userspace i2c drivers Thomas Petazzoni
2013-09-24 15:55 ` Baruch Siach [this message]
2013-09-24 16:46 ` Will Wagner
2013-09-25 5:14 ` Nikula Jouko
2014-03-03 21:10 ` Thomas Petazzoni
2014-03-04 18:14 ` Thomas Petazzoni
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=20130924155515.GD4838@tarshish \
--to=baruch@tkos.co.il \
--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.