All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
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: <20050103134007.40395a37.khali@linux-fr.org> (raw)
In-Reply-To: <20041230173527.GF10397@neu.nirvana>

> > 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.

Since the includes actually are <linux/...>, not <linux/i2c/...>, that
would be /use/include/i2c/linux. It is obviously important to have the
same include "tree" (even if it has just a depth of 1) in /usr/include
(or wherever it'll end) than we have in the Linux kernel source tree.

> If not /usr/include/i2c then perhaps /usr/local/include/i2c to be in
> sync with the other /usr/local defaults.

i2c and lm_sensors default to /usr/local for everything they install
(except for the libsensors configuration file) and I don't think we will
change this now. Thus I would go for /usr/local/include/i2c, but of
course you could do /usr/include/i2c on your RPM packages if it fits the
Red Hat/Fedora policy better.

Anyway, before going there, we'd better fix i2c 2.9.0 so that if does
install the header files at the old location again, so that people can
compile lm_sensors.

-- 
Jean Delvare
http://khali.linux-fr.org/

  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
2005-05-19  6:25 ` Jean Delvare
2005-05-19  6:25 ` Jean Delvare [this message]
2005-05-19  6:25 ` Axel Thimm
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=20050103134007.40395a37.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --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.