All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timo.Bolse@SerNet.DE (Timo.Bolse@SerNet.DE)
To: lm-sensors@vger.kernel.org
Subject: bug report?!
Date: Thu, 19 May 2005 06:25:08 +0000	[thread overview]
Message-ID: <E1Bt0wR-0002TF-00@intern.SerNet.DE> (raw)

Dear LM-Sensors Team,

I tried to compile i2c and lm_sensors on this machine: 

Linux dhcp230 2.4.21-99-athlon #1 Wed Sep 24 13:34:32 UTC 2003 i686 athlon i386
 GNU/Linux).
gcc version 3.3.1 (SuSE Linux)

While compilation i get on both i2c and lm_sensors the following error:

kernel/i2c-pport.c:154: error: initializer element is not constant
kernel/i2c-pport.c:154: error: (near initialization for `bit_pport_data.timeout'

Not only for i2c-pport.c. I spent some time covering this bug. I found out that
you take the HZ Value out of asm/param.h for the timeouts in many of your 
modules. For me i switch to a hardcoded value so that the element is constant.
I took the value defined for userspace in asm/param.h. (On my system 100) and
everything compiled fine. I'am not a very good c programmer so i don't know how
to cover this i think you need this timeout HZ definition because param.h makes
a difference between kernelmode and userspace.

The other problem i spotted is that your tar.gz archive of i2c-2.8.7 is not a
gzip archive.

dhcp230:~ # file i2c-2.8.7.tar.gz
i2c-2.8.7.tar.gz: POSIX tar archive

A not that much confidant user could be very confused if he is downloading a
tar.gz from you website which is a tar.

Regards,
Timo Bolse

             reply	other threads:[~2005-05-19  6:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19  6:25 Timo.Bolse [this message]
2005-05-19  6:25 ` bug report?! Jean Delvare
2005-05-19  6:25 ` Jean Delvare
  -- strict thread matches above, loose matches on Subject: below --
2004-05-21 18:41 bug report? Xuan Baldauf
2004-05-21 19:11 ` Jeff Mahoney

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=E1Bt0wR-0002TF-00@intern.SerNet.DE \
    --to=timo.bolse@sernet.de \
    --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.