All of lore.kernel.org
 help / color / mirror / Atom feed
From: jwa@fasytek.dk (J. W. Andersen)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] ASUS NCCH-DR confusing 83792 vs. 83627THF
Date: Wed, 14 Jun 2006 16:19:12 +0000	[thread overview]
Message-ID: <44903700.3080702@fasytek.dk> (raw)
In-Reply-To: <44901813.3080703@fasytek.dk>

Thanks, Jean, for clearing this up for me.

Joern.

Jean Delvare wrote:
>>> The other thing that puzzles me: In an X86_64 system, I would expect to
>>> find the libsensor libraries in a the /lib64 directory, but they actually
>>> get installed in /usr/local/lib. What must I do to get these libraries
>>> in the proper place ?
>>>       
>> # You should not need to change this. It is the directory into which the
>>
>> # library files (both static and shared) will be installed.
>>
>> LIBDIR := $(PREFIX)/lib
>>
>> maybe you can change this to lib64 so the dir will be /usr/local/lib64 but I
>> dont know if such directory can exist.
>>     
>
> I can't get why some distributions invented these lib64 directories. On
> 32-bit systems we have lib, not lib32, so why make it different on
> 64-bit systems? It may make sense to have a lib32 directory on 64-bit
> systems for libraries which are only available in 32-bit format, Gentoo
> is doing it almost this way (lib is a link to lib64, and there is lib32
> for the 32-bit libraries), but doing it the other way around sounds
> weird to me.
>
> However if most distributions do that... Maybe we should detect 64-bit
> systems and change the default in this case. Anyone wants to give it a
> try?
>
> At any rate, nothing will break if you install your 64-bit
> libsensors.so under /usr/local/lib, I'm doing this and it works just
> fine.
>
> I wonder why you are installing it by yourself, rather that using the
> suse package which would put everything in the right place for you?
>
>   
>> You may also change the PREFIX to / to get it to /lib64 if you like. (all in top
>> Makefile)
>>     
>
> This would be a very bad idea. /lib (and /lib64) are meant for
> libraries fundamental to the system, libsensors sure doesn't qualify.
>
>   


  parent reply	other threads:[~2006-06-14 16:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-14 14:07 [lm-sensors] ASUS NCCH-DR confusing 83792 vs. 83627THF J. W. Andersen
2006-06-14 15:07 ` Rudolf Marek
2006-06-14 16:04 ` Jean Delvare
2006-06-14 16:13 ` J. W. Andersen
2006-06-14 16:19 ` J. W. Andersen [this message]
2006-06-14 16:20 ` Henrik Brix Andersen
2006-06-26 12:01 ` Rudolf Marek

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=44903700.3080702@fasytek.dk \
    --to=jwa@fasytek.dk \
    --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.