* [lm-sensors] How to get patches and build with them?
@ 2011-12-01 17:28 Charles
2011-12-01 17:29 ` Jean Delvare
` (3 more replies)
0 siblings, 4 replies; 5+ messages in thread
From: Charles @ 2011-12-01 17:28 UTC (permalink / raw)
To: lm-sensors
Hello :-)
I want to build lm_sensors *3.3.1 *and see from
http://www.lm-sensors.org/wiki/Download that four patches are
recommended. How do I download the patches and incorporate them during
the build?
I appreciate this is a common procedure and there must be some
instructions somewhere; a link to instructions would be helpful.
Best
Charles
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [lm-sensors] How to get patches and build with them?
2011-12-01 17:28 [lm-sensors] How to get patches and build with them? Charles
@ 2011-12-01 17:29 ` Jean Delvare
2011-12-02 6:43 ` Charles
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: Jean Delvare @ 2011-12-01 17:29 UTC (permalink / raw)
To: lm-sensors
Hi Charles,
On Thu, 01 Dec 2011 22:46:26 +0530, Charles wrote:
> Hello :-)
>
> I want to build lm_sensors *3.3.1 *and see from
> http://www.lm-sensors.org/wiki/Download that four patches are
> recommended. How do I download the patches and incorporate them during
> the build?
Click each link, then scroll to the bottom of the page and choose
"Unified Diff". I then recommend running dos2unix on all patches as for
some strange reason trac produces DOS format text files. Then just
apply the patches in order with patch -p2.
I'll let you appreciate which of these patches you actually want. I'm
the one making the selection but it's often arbitrary and every case is
different.
> I appreciate this is a common procedure and there must be some
> instructions somewhere; a link to instructions would be helpful.
It's no so common, I think. The list of patches is mainly there for
packagers. End-users are supposed to simply install packages from their
distribution. As a matter of fact, I think you're the first one asking
for help with this since I started maintaining this list 4 years ago.
--
Jean Delvare
http://khali.linux-fr.org/wishlist.html
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [lm-sensors] How to get patches and build with them?
2011-12-01 17:28 [lm-sensors] How to get patches and build with them? Charles
2011-12-01 17:29 ` Jean Delvare
@ 2011-12-02 6:43 ` Charles
2011-12-02 7:21 ` Jean Delvare
2011-12-02 9:51 ` Charles
3 siblings, 0 replies; 5+ messages in thread
From: Charles @ 2011-12-02 6:43 UTC (permalink / raw)
To: lm-sensors
On 01/12/11 22:59, Jean Delvare wrote:
> Hi Charles,
>
> On Thu, 01 Dec 2011 22:46:26 +0530, Charles wrote:
>> Hello :-)
>>
>> I want to build lm_sensors *3.3.1 *and see from
>> http://www.lm-sensors.org/wiki/Download that four patches are
>> recommended. How do I download the patches and incorporate them during
>> the build?
>
> Click each link, then scroll to the bottom of the page and choose
> "Unified Diff". I then recommend running dos2unix on all patches as for
> some strange reason trac produces DOS format text files. Then just
> apply the patches in order with patch -p2.
>
> I'll let you appreciate which of these patches you actually want. I'm
> the one making the selection but it's often arbitrary and every case is
> different.
>
>> I appreciate this is a common procedure and there must be some
>> instructions somewhere; a link to instructions would be helpful.
>
> It's no so common, I think. The list of patches is mainly there for
> packagers. End-users are supposed to simply install packages from their
> distribution. As a matter of fact, I think you're the first one asking
> for help with this since I started maintaining this list 4 years ago.
Many thanks for the prompt reply Jean :)
I went with your recommended patches for starters. Had to use -p3 (not
in expected directory?). The build is for Slackware64 13.1, upgraded to
kernel 2.6.38.7 running on an ASUS PBH67-V motherboard which has a
Nuvoton NCT6776F -- as the newly installed lm_sensors 3.3.1
sensors-detect now reports :)
These are the download and patch commands used:
gpg --keyserver wwwkeys.pgp.net --recv-keys 38F02FC8
cd /tmp \
&& rm -fr lm_sensors-3.3.1 \
&& wget
http://dl.lm-sensors.org/lm-sensors/releases/lm_sensors-3.3.1.tar.bz2 \
&& wget
http://dl.lm-sensors.org/lm-sensors/releases/lm_sensors-3.3.1.tar.bz2.sig \
&& gpg --verify lm_sensors-3.3.1.tar.bz2.sig \
&& tar -jxvf lm_sensors-3.3.1.tar.bz2 \
&& cd lm_sensors-3.3.1 \
&& wget --output-document=patch_5991 \
'http://www.lm-sensors.org/changeset/5991?format=diff&newY91' \
&& wget --output-document=patch_5992 \
'http://www.lm-sensors.org/changeset/5992?format=diff&newY92' \
&& wget --output-document=patch_5993 \
'http://www.lm-sensors.org/changeset/5993?format=diff&newY93' \
&& wget --output-document=patch_5999 \
'http://www.lm-sensors.org/changeset/5999?format=diff&newY99' \
&& patch -p3 < patch_5991 \
&& patch -p3 < patch_5992 \
&& patch -p3 < patch_5993 \
&& patch -p3 < patch_5999
BTW, make PREFIX=/tmp/tmp installed to /usr/local
After installing to /usr/local the following symlink was required to
allow GKrellM to start:
ln -s /usr/local/lib/libsensors.so.4 /usr/lib64/libsensors.so.4
Best
Charles
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [lm-sensors] How to get patches and build with them?
2011-12-01 17:28 [lm-sensors] How to get patches and build with them? Charles
2011-12-01 17:29 ` Jean Delvare
2011-12-02 6:43 ` Charles
@ 2011-12-02 7:21 ` Jean Delvare
2011-12-02 9:51 ` Charles
3 siblings, 0 replies; 5+ messages in thread
From: Jean Delvare @ 2011-12-02 7:21 UTC (permalink / raw)
To: lm-sensors
On Fri, 02 Dec 2011 12:01:59 +0530, Charles wrote:
> Many thanks for the prompt reply Jean :)
>
> I went with your recommended patches for starters. Had to use -p3 (not
> in expected directory?).
I was no longer sure if it was -p2 or -p3. The -p3 is probably needed
because of the leading / in the file paths.
> The build is for Slackware64 13.1, upgraded to
> kernel 2.6.38.7 running on an ASUS PBH67-V motherboard which has a
> Nuvoton NCT6776F -- as the newly installed lm_sensors 3.3.1
> sensors-detect now reports :)
>
> These are the download and patch commands used:
>
> gpg --keyserver wwwkeys.pgp.net --recv-keys 38F02FC8
>
> cd /tmp \
> && rm -fr lm_sensors-3.3.1 \
> && wget
> http://dl.lm-sensors.org/lm-sensors/releases/lm_sensors-3.3.1.tar.bz2 \
> && wget
> http://dl.lm-sensors.org/lm-sensors/releases/lm_sensors-3.3.1.tar.bz2.sig \
> && gpg --verify lm_sensors-3.3.1.tar.bz2.sig \
> && tar -jxvf lm_sensors-3.3.1.tar.bz2 \
> && cd lm_sensors-3.3.1 \
> && wget --output-document=patch_5991 \
> 'http://www.lm-sensors.org/changeset/5991?format=diff&newY91' \
> && wget --output-document=patch_5992 \
> 'http://www.lm-sensors.org/changeset/5992?format=diff&newY92' \
> && wget --output-document=patch_5993 \
> 'http://www.lm-sensors.org/changeset/5993?format=diff&newY93' \
> && wget --output-document=patch_5999 \
> 'http://www.lm-sensors.org/changeset/5999?format=diff&newY99' \
> && patch -p3 < patch_5991 \
> && patch -p3 < patch_5992 \
> && patch -p3 < patch_5993 \
> && patch -p3 < patch_5999
>
> BTW, make PREFIX=/tmp/tmp installed to /usr/local
>
> After installing to /usr/local the following symlink was required to
> allow GKrellM to start:
>
> ln -s /usr/local/lib/libsensors.so.4 /usr/lib64/libsensors.so.4
This can probably be avoided by passing LIBDIR=/usr/local/lib64 to
make, and adding /usr/local/lib64 to /etc/ld.so.conf if it's not
already there. Alternatively, just adding /usr/local/lib
to /etc/ld.so.conf should work too.
--
Jean Delvare
http://khali.linux-fr.org/wishlist.html
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [lm-sensors] How to get patches and build with them?
2011-12-01 17:28 [lm-sensors] How to get patches and build with them? Charles
` (2 preceding siblings ...)
2011-12-02 7:21 ` Jean Delvare
@ 2011-12-02 9:51 ` Charles
3 siblings, 0 replies; 5+ messages in thread
From: Charles @ 2011-12-02 9:51 UTC (permalink / raw)
To: lm-sensors
On 02/12/11 12:51, Jean Delvare wrote:
>> After installing to /usr/local the following symlink was required to
>> > allow GKrellM to start:
>> >
>> > ln -s /usr/local/lib/libsensors.so.4 /usr/lib64/libsensors.so.4
> This can probably be avoided by passing LIBDIR=/usr/local/lib64 to
> make, and adding /usr/local/lib64 to /etc/ld.so.conf if it's not
> already there. Alternatively, just adding /usr/local/lib
> to /etc/ld.so.conf should work too.
Thanks for the advice, Jean :)
The advantage of the symlink technique is that it replaces the
lm_sensors libsensors.so.4 as installed by Slackware so, if the 3.3.1
installation is every replaced by a Slackware package, the available
libsensors.so.4 will automatically be changed.
BTW I forgot to mention that the dos2unix step was unnecessary because
patch strips the DOS-isms.
Best
Charles
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2011-12-02 9:51 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-12-01 17:28 [lm-sensors] How to get patches and build with them? Charles
2011-12-01 17:29 ` Jean Delvare
2011-12-02 6:43 ` Charles
2011-12-02 7:21 ` Jean Delvare
2011-12-02 9:51 ` Charles
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.