From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: Ticket 1319 - lm_sensors-2.8.0-cvs linux-2.4.20-smp-i386
Date: Thu, 19 May 2005 06:24:04 +0000 [thread overview]
Message-ID: <20030710091255.444264b4.khali@linux-fr.org> (raw)
In-Reply-To: <20030710085158.42e68c95.zdavatz@ywesee.com>
> I followed your advice and compiled again with the CVS-Version, both
> i2c and lm-sensors.
>
> Before I done make I done cvs update -d
>
> i2c goes grest but lm-sensors gives me:
>
> kernel/busses/i2c-nforce2.c: In function `nforce2_access':
> kernel/busses/i2c-nforce2.c:154: `I2C_CLIENT_PEC' undeclared (first
> use in this function) kernel/busses/i2c-nforce2.c:154: (Each
> undeclared identifier is reported only once
> kernel/busses/i2c-nforce2.c:154: for each function it appears in.)
> (...)
CVS is known to compile great, so you must have done a mistake
somewhere, or your system is special (or broken).
Remember you have to *install* i2c before trying to *compile*
lm_sensors2. I would do a fresh CVS checkout and reinstall everything
from scratch, just to make sure no file was accidentally modified in
your local directories.
--
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/
next prev parent reply other threads:[~2005-05-19 6:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:24 Ticket 1319 - lm_sensors-2.8.0-cvs linux-2.4.20-smp-i386 Zeno R.R. Davatz
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Zeno R.R. Davatz
2005-05-19 6:24 ` Zeno R.R. Davatz
2005-05-19 6:24 ` Zeno R.R. Davatz
2005-05-19 6:24 ` Jean Delvare [this message]
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Zeno R.R. Davatz
2005-05-19 6:24 ` Zeno R.R. Davatz
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Zeno R.R. Davatz
2005-05-19 6:24 ` Zeno R.R. Davatz
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=20030710091255.444264b4.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.