All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: Call for 2.8.0 soon
Date: Thu, 19 May 2005 06:24:02 +0000	[thread overview]
Message-ID: <20030629143729.2aa8b433.khali@linux-fr.org> (raw)
In-Reply-To: <3EE7C67A.4040703@paradyne.com>


> - GCC 3.3 warnings Khali is working?

GCC 3.2 warnings fixed.

Oh, by the way, I got this message when installing latest CVS:

***********************************************************************
*******
Warning: This is the first installation of the libsensors.so*
         library files in /usr/local/lib !!!
         You must run /sbin/ldconfig to update the library cache or
         the userspace tools may fail or have unpredictable results !!!
***********************************************************************
*******

Though I think the message can be useful in some cases, I already had
the libraries installed there, but a previous version (1.4.0 as opposed
to 2.0.0). I think the message should mention that, or it will seem to
be pointless to users in this case.

Also, why don't we run ldconfig by ourselves in this case? We could even
grep /etc/ld.so.conf for /usr/local/lib and display a warning only if
the line is not found (or add it by ourselves, but I'm not in favor of
this).

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/

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

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19  6:23 Call for 2.8.0 soon Mark D. Studebaker 
2005-05-19  6:23 ` Jean Delvare
2005-05-19  6:23 ` Philip Pokorny
2005-05-19  6:23 ` Mark D. Studebaker 
2005-05-19  6:23 ` Greg KH
2005-05-19  6:23 ` Jean Delvare
2005-05-19  6:23 ` Philip Pokorny
2005-05-19  6:24 ` Mark D. Studebaker 
2005-05-19  6:24 ` Jean Delvare
2005-05-19  6:24 ` Jean Delvare [this message]
2005-05-19  6:24 ` Jean Delvare

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=20030629143729.2aa8b433.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.