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
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