Setting up optional OpenMP support with RcppArmadillo

[This article was first published on Posts on GGVY, and kindly contributed to R-bloggers]. (You can report issue about the content on this page here)
Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.

Setting up an R package that supports OpenMP can be a bit awkward. While systems like Ubuntu with g++ have straight forward support for -fopenmp flags, the same may not be true un MacOS’s clang, since the latter is not shipped with it.

In order to solve this, it is necesary to have different src/Makevars file depending on whether the compiler supports OpenMP or not. This can be solved using a configure file, more over, autoconf.

Autoconf is “an extensible package of M4 macros that produce shell scripts to automatically configure software source code packages”. Among the (cool) things that we can use it for is creating tailored src/Makevars files (and furthermore, any other files… even R/*.r source code can be modified with this, just take a look at Writing R Extensions). The workflow of R CMD+autoconf follows:

  1. The configure file is executed and performs the requested checks (like having OpenMP) and modifies/creates the configuration files that will be used to compile the package, like src/Makevars, src/makefile, etc. Furthermore, it can use “templates” to create such files, which have the suffix .in, for example, src/

  2. R CMD will compile the package using all the inputs (src/Makevars, src/makefile) that were created, and

  3. In the case of R CMD build, R CMD will call cleanup (they require you to do so) to remove the config.* files and src/Makevars so these are not shipped with the package file.

The next section describes the files that you need to include in your project to set it up using RcppArmadillo with OpenMP support depending on whether it is available with the compiler. This example is from the R package netdiffuseR.

Configuration Files

In order to use autoconf to optionally include OpenMP with your R package, you need to have the following files in your system:

  1. Need a file. This is what autoconf uses as input.

    #                                               -*- Autoconf -*-
    # netdiffuseR
    # (with some code borrowed from RcppArmadillo
    # and ARTP2
    # Process this file with autoconf to produce a configure script.

    This line can be replaced by whatever the name of your package is (here is netdiffuseR)

    AC_INIT(netdiffuseR, m4_esyscmd_s([awk '/^Version:/ {print $2}' DESCRIPTION]))

    These couple of lines set up the path to R.

    # Set R_HOME, respecting an environment variable if one is set 
    : ${R_HOME=$(R RHOME)}
    if test -z "${R_HOME}"; then
        AC_MSG_ERROR([Could not determine R_HOME.])   
    # Use R to set CXX and CXXFLAGS
    CXX=$(${R_HOME}/bin/R CMD config CXX)
    CXXFLAGS=$("${R_HOME}/bin/R" CMD config CXXFLAGS)
    # We are using C++

    This are the lines that actually do the job on setting OpenMP. I copied this from the ARTP2 R Package.

    dnl this the meat of R's m4/openmp.m4
        [AS_HELP_STRING([--disable-openmp], [do not use OpenMP])])
      if test "$enable_openmp" != no; then
        AC_CACHE_CHECK([for $[]_AC_CC[] option to support OpenMP],
         [ac_cv_prog_[]_AC_LANG_ABBREV[]_openmp='none needed'],
          for ac_option in -fopenmp -xopenmp -qopenmp \
                               -openmp -mp -omp -qsmp=omp -homp \
                   -fopenmp=libomp \
                               -Popenmp --openmp; do
            _AC_LANG_PREFIX[]FLAGS="$[]_AC_LANG_PREFIX[]FLAGS $ac_option"
            if test "$ac_cv_prog_[]_AC_LANG_ABBREV[]_openmp" != unsupported; then
        case $ac_cv_prog_[]_AC_LANG_ABBREV[]_openmp in #(
          "none needed" | unsupported)
        ;; #(
        OPENMP_[]_AC_LANG_PREFIX[]FLAGS=$ac_cv_prog_[]_AC_LANG_ABBREV[]_openmp ;;
  2. A src/ file which will be modified by configure. The most important part here is the @OPENMP_CXXFLAGS@ tag, which will be replaced accordingly:

    # 1.2.4 Using C++11 code
    CXX_STD = CXX11
    # Besides of the -fopenmp flag, here I'm telling armadillo to use
    # 64BIT_WORD which removes the matrix size limit constraint.
  3. A cleanup file (with execution permissions) that R CMD build will call after building the package. Again, this is a requirement.

    rm -f config.* src/Makevars

Once you have all these files in order, you have to run autoconf so that the configure file is created, i.e.

$ autoconf

If you happen to use travis.yml, you need to specify a more modern distribution so that RcppArmadillo can built with a more modern compiler. In order to do so, put the dist: trusty option in the yml file. Here is an example travis file from netdiffuseR:

dist: trusty
language: r
sudo: required

  - release
  - devel # Not working
  - oldrel

  - linux
  - osx

osx_image: xcode7.3

   - CRAN:

  - ape
  - covr
  - testthat
  - knitr
  - rmarkdown
  - RSiena
  - igraph
  - survival

  - if [ $TRAVIS_OS_NAME == "linux" ]; then Rscript -e 'covr::codecov()'; fi

  - ./ dump_logs

    on_success: change
    on_failure: change

Finally, you’ll need to add/keep the following files to your repository: configure,, src/, src/, and cleanup. Otherwise you’ll find yourself scratching your head and asking why is travis failing… belive me.

See also

To leave a comment for the author, please follow the link and comment on their blog: Posts on GGVY. offers daily e-mail updates about R news and tutorials about learning R and many other topics. Click here if you're looking to post or find an R/data-science job.
Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.

Never miss an update!
Subscribe to R-bloggers to receive
e-mails with the latest R posts.
(You will not see this message again.)

Click here to close (This popup will not appear again)