From tom@@@k@||ber@ @end|ng |rom gm@||@com  Fri Mar  1 09:19:13 2019
From: tom@@@k@||ber@ @end|ng |rom gm@||@com (Tomas Kalibera)
Date: Fri, 1 Mar 2019 09:19:13 +0100
Subject: [Rd] pcre problems
In-Reply-To: <CAHHjBM4OoWRukaS_u=F6ecVmWi3Kqz=8QRA4nNGCtzSOJHOxOg@mail.gmail.com>
References: <CAHHjBM7CJa6un7Up6nM4NHZjn17MdXFjRPxkYvkv+V2F6d4hDA@mail.gmail.com>
 <2a6d5ab9-ccfd-c522-5718-baf270e098b5@gmail.com>
 <CAHHjBM5hQ0bmFNaO3QOOO7napLDM5n+5PvJxgG275K07JwL9tg@mail.gmail.com>
 <db7ce85b-50a9-1745-10f9-b88b2252a150@gmail.com>
 <CAHHjBM4OoWRukaS_u=F6ecVmWi3Kqz=8QRA4nNGCtzSOJHOxOg@mail.gmail.com>
Message-ID: <cdbe3889-53df-be5b-3e33-86487070623e@gmail.com>

On 3/1/19 9:03 AM, robin hankin wrote:
> OK thanks Tomas, but I get
>
>
> OK~ sudo apt-get build-dep r-base
> Reading package lists... Done
> E: Unable to find a source package for r-base
> OK~

It seems you need to enable source code? repositories on your system 
(and then run apt-get update).
You can enable them in /etc/apt/sources.list, uncomment all lines 
starting with deb-src.

Best
Tomas

>
>
> hankin.robin at gmail.com
>
>
> On Fri, Mar 1, 2019 at 8:47 PM Tomas Kalibera <tomas.kalibera at gmail.com> wrote:
>> On 3/1/19 7:10 AM, robin hankin wrote:
>>> thanks for this guys.
>>>
>>> I only compiled pcre myself as a last resort,  because of the
>>> ./configure failure.  But AFAICS  apt-get reports correct
>>> installation:
>>>
>>> OK~/Downloads/R-devel sudo apt-get install r-base-dev
>>> Reading package lists... Done
>>> Building dependency tree
>>> Reading state information... Done
>>> r-base-dev is already the newest version (3.5.2-1cosmic).
>>> 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
>>> OK~/Downloads/R-devel
>> I would just run this
>>
>> apt-get build-dep r-base
>>
>> that will install all packages needed to _build_ r-base, so including PCRE.
>>
>> Best
>> Tomas
>>
>>> config.log gives me:
>>>
>>> configure:42208: $? = 0
>>> configure:42208: result: yes
>>> configure:42208: checking for pcre.h
>>> configure:42208: result: yes
>>> configure:42208: checking pcre/pcre.h usability
>>> configure:42208: gcc -c  -g -O2 -I/usr/local/include  conftest.c >&5
>>> conftest.c:289:10: fatal error: pcre/pcre.h: No such file or directory
>>>    #include <pcre/pcre.h>
>>>             ^~~~~~~~~~~~~
>>> compilation terminated.
>>> configure:42208: $? = 1
>>> configure: failed program was:
>>> | /* confdefs.h */
>>> | #define PACKAGE_NAME "R"
>>> | #define PACKAGE_TARNAME "R"
>>> | #define PACKAGE_VERSION "3
>>>
>>> and
>>>
>>> HAVE_UNISTD_H
>>> | # include <unistd.h>
>>> | #endif
>>> | #include <pcre/pcre.h>
>>> configure:42208: result: no
>>> configure:42208: checking pcre/pcre.h presence
>>> configure:42208: gcc -E -I/usr/local/include  conftest.c
>>> conftest.c:256:10: fatal error: pcre/pcre.h: No such file or directory
>>>    #include <pcre/pcre.h>
>>>             ^~~~~~~~~~~~~
>>> compilation terminated.
>>> configure:42208: $? = 1
>>> configure: failed program was:
>>> | /* confdefs.h */
>>> | #define PACKAGE_NAME "R"
>>> | #define PACKAGE_TARNAME "R"
>>> | #define PACKAGE_VERSION "3.6.0"
>>> | #define PACKAGE_STRING "R 3.6.0"
>>> | #define PACKAGE_BUGREPOR
>>>
>>>
>>>
>>> hankin.robin at gmail.com
>>>
>>>
>>>
>>>
>>> On Mon, Feb 25, 2019 at 9:39 PM Tomas Kalibera <tomas.kalibera at gmail.com> wrote:
>>>> On 2/25/19 6:25 AM, robin hankin wrote:
>>>>> Hi there, ubuntu 18.04.2, trying to compile R-devel  3.6.0,  svn 76155.
>>>>>
>>>>> I am having difficulty compiling R. I think I have pcre installed correctly:
>>>> You can use
>>>>
>>>> apt-get build-dep r-base
>>>>
>>>> to install binary Ubuntu packages needed to build R from source,
>>>> including PCRE, so there should be no need to compile PCRE from source.
>>>> If you need for some special reason to compile PCRE from source, please
>>>> see R Admin Manual, section A.1 on how to configure PCRE. The manual
>>>> also says how to set compilation flags for R to look for headers in
>>>> other directories. Sometimes it helps to search the config.log when
>>>> configure fails. If still in trouble, please report how you built PCRE
>>>> and how you told R where to find it, and the relevant part of
>>>> config.log, to maximize chances people could offer useful advice.
>>>>
>>>> Best,
>>>> Tomas
>>>>
>>>>> OK~/Downloads/R-devel pcretest -C
>>>>> PCRE version 8.41 2017-07-05
>>>>> Compiled with
>>>>>      8-bit support
>>>>>      UTF-8 support
>>>>>      No Unicode properties support
>>>>>      No just-in-time compiler support
>>>>>      Newline sequence is LF
>>>>>      \R matches all Unicode newlines
>>>>>      Internal link size = 2
>>>>>      POSIX malloc threshold = 10
>>>>>      Parentheses nest limit = 250
>>>>>      Default match limit = 10000000
>>>>>      Default recursion depth limit = 10000000
>>>>>      Match recursion uses stack
>>>>> OK~/Downloads/R-devel
>>>>>
>>>>>
>>>>> But ./configure gives me this:
>>>>>
>>>>> [snip]
>>>>> checking for pcre.h... yes
>>>>> checking pcre/pcre.h usability... no
>>>>> checking pcre/pcre.h presence... no
>>>>> checking for pcre/pcre.h... no
>>>>> checking if PCRE version >= 8.20, < 10.0 and has UTF-8 support... no
>>>>> checking whether PCRE support suffices... configure: error: pcre >=
>>>>> 8.20 library and headers are required
>>>>> OK~/Downloads/R-devel
>>>>>
>>>>> can anyone advise?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> hankin.robin at gmail.com
>>>>>
>>>>> ______________________________________________
>>>>> R-devel at r-project.org mailing list
>>>>> https://stat.ethz.ch/mailman/listinfo/r-devel



[Rd] pcre problems
Tomas Kalibera