From ramonfallon at gmail.com  Fri Sep  9 13:21:48 2016
From: ramonfallon at gmail.com (=?UTF-8?Q?Ram=C3=B3n_Fallon?=)
Date: Fri, 9 Sep 2016 12:21:48 +0100
Subject: [Rd] forgive possible repost: alternate bzip2 library
Message-ID: <CA+WKpEvm9LaErgWygwmSm3i5g9AxK=XUQHknp66rh6292o_u6w@mail.gmail.com>

Hi,

I am resubmitting a question, mainly because I suspect I may have
inadvertently cancelled it, while it was awaiting moderator approval.

It's about manually compiling R-3.3.1 and using, not the standard system's
(ver 1.0.5), but an alternate a bzip2 (v1.0.6) which is located in a
non-standard location.

I usually lean on pkg-config to deal with issues like this. I've create an
appropriate bzip2.pc file for bzip2 for this purpose.

I've been focusing on the configure script, which at 50K lines is quite
hefty and my initial question was whether the R compile configure script
used pkg-config for locating headers and libraries.

My feeling now is that the answer is "sometimes". In locating
cairographics, it says it does, but for bzip2 I think it uses autoconf's
dubious magic. Don't know if anybody can confirm this.

I could modify the configure so that it looks for bzip2 via pkg-config but
manual modification of this script is probably not proper practice, as well
as being very time consuming.

Any guidance appreaicted. Many thanks.

	[[alternative HTML version deleted]]



[Rd] forgive possible repost: alternate bzip2 library
=?UTF-8?Q?Ram=C3=B3n_Fallon?=