From: Axel.Thimm@ATrpms.net (Axel Thimm)
To: lm-sensors@vger.kernel.org
Subject: Upcoming rpms: i2c headers under /usr/include/i2c
Date: Thu, 19 May 2005 06:25:28 +0000 [thread overview]
Message-ID: <20050103011512.GG7814@neu.nirvana> (raw)
In-Reply-To: <20041230173527.GF10397@neu.nirvana>
On Sun, Jan 02, 2005 at 11:26:13AM +0100, Jean Delvare wrote:
> > Where should kernel space headers for building depending kernel
> > modules go? You need the "i2c-kernheaders" at least for building
> > the lm_sensors kernel modules.
> > Perhaps /usr/include/linux is for userland
> > interfacing the kernel, but then there is no FHS place for
> > kernel-kernel headers (they are assumed to be hiding in the kernel
> > source only). Perhaps per kernel /lib/modules/.../{source,build}
> > locations would have been more appropriate.
>
> I have no idea where the correct location would be, so anything you come
> with is fine with me.
Perhaps indeed /usr/include/i2c/linux/i2c?
And I2C_HEADERS need to point (and default) to /usr/include/i2c, while
#include <linux/i2c/....>
picks the header either from a proper Linux kernel tree or from
I2C_HEADERS.
If not /usr/include/i2c then perhaps /usr/local/include/i2c to be in
sync with the other /usr/local defaults.
--
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20050103/aecfac20/attachment.bin
next prev parent reply other threads:[~2005-05-19 6:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:25 Upcoming rpms: i2c headers under /usr/include/i2c Axel Thimm
2005-05-19 6:25 ` Jean Delvare
2005-05-19 6:25 ` Axel Thimm [this message]
2005-05-19 6:25 ` Jean Delvare
2005-05-19 6:25 ` Axel Thimm
2005-05-19 6:25 ` Jean Delvare
2005-05-19 6:25 ` Axel Thimm
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=20050103011512.GG7814@neu.nirvana \
--to=axel.thimm@atrpms.net \
--cc=lm-sensors@vger.kernel.org \
/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.