similar to: Will Devtools-1.1 or later become part of SCL?

Hi! I want to make the default environment for users the environment of devtoolset .. and i am thinking to do it this way: 1. make /bin/bash-devtools with the content scl enable devtoolset-2 bash "$@" 2. change for the prospective users the shell from /bin/bash to /bin/bash-devtoolset Is this the best way? Do anyone see or know of any pitfalls with this? Thanks a lot! Adrian

Just in case someone is having similar problems and/or following this thread, here's my final "solution" (at least, for now). In my bash build script, prior to configure, I set the C_INCLUDE_PATH and CPLUS_INCLUDE_PATH to empty strings, and then set some other environment variables instead: export C_INCLUDE_PATH= export CPLUS_INCLUDE_PATH=

Is there a way to install devtoolset packages without the bloat of eclipse? I just want the new compiler and toolchain, not a big IDE. BTW devtoolset-3 dependencies are broken in yum with C6 yum install devtoolset-3 ... ---> Package devtoolset-3-perftools.x86_64 0:3.1-12.el6 will be installed --> Processing Dependency: devtoolset-3-dyninst for package:

This question was posed on SO : https://stackoverflow.com/questions/58118495/passing-extra-argumenets-to-devtoolsbuild but there has been no useful reply. Something seems to have changed in the |devtools|package, so that the following commands, that used to run now give an error I can't decipher: |>Sys.setenv(R_GSCMD="C:/Program

I'm attempting to build a native build of clang from the 3.2 source distribution tarballs, but I ran into this build error that's got me really puzzled. My platform is Linux - 32-bit Ubuntu (12.04) running on a PC. Here's the (abbreviated) output from make: *************************************** ... make[3]: Entering directory

Hola a todos. Estoy intentando instalar el paquete likert utilizando devtools y obtengo el siguiente error library(devtools) install_github('likert','jbryer') Installing github repo(s) likert/master from jbryer Downloading likert.zip from https://github.com/jbryer/likert/archive/master.zip Error en function (type, msg, asError = TRUE) : <not set> Me pasa también con

I recently tried to submit a package to CRAN using the release function in the devtools package and got the response: > The policies asked you to use the webform: do so in future. I think that the relevant line in the policies are: > When submitting a package to CRAN you should use the submission form at > http://CRAN.R-project.org/submit.html (and not send an email). You will be sent

Hello, Please try this: > library(devtools) > create("mdaa") > setwd("mdaa") > dev_mode() d> install() Produces ...* DONE (mdaa) Reloading installed mdaa But when I then try to build documentation d> document() devtools/roxygen just hangs with a "?" like so: Updating mdaa documentation Loading mdaa ? I know this scenario is strange as

Si. Pero no funciona. En ordenador curro si funciona y tb tiene linux. Seguiré investigando has probado con: install_github('paquete",username='usuario')? 2013/12/20 Jose Luis Cañadas Reche <canadasreche@gmail.com>: > Hola a todos. > > Estoy intentando instalar el paquete likert utilizando devtools y obtengo el > siguiente error > > library(devtools) >

> Date: Tuesday, September 08, 2015 15:24:50 -0700 > From: Robert Arkiletian <robark at gmail.com> > >> On Tue, Sep 8, 2015 at 3:11 PM, Richard wrote: >> >> >> > Date: Tuesday, September 08, 2015 14:57:22 -0700 >> > From: Robert Arkiletian <robark at gmail.com> >> > >> > I was able to get h.264 support on

On Mon, Jan 12, 2015 at 6:22 PM, Robert Arkiletian <robark at gmail.com> wrote: > On Mon, Jan 5, 2015 at 1:13 PM, Robert Arkiletian <robark at gmail.com> > wrote: > > > Johnny, > > > > Any ETA on version 39.0.2171.95 > > > > cheers > > > > > > bump > _______________________________________________ > CentOS mailing list

Hi, checking my package with check from devtools leads to the output Functions with \usage entries need to have the appropriate \alias entries, and all their arguments documented. The \usage entries must correspond to syntactically valid R code. See chapter ?Writing R documentation files? in the ?Writing R Extensions? manual. * checking Rd contents ... OK * checking for unstated dependencies in

On Mon, Jan 19, 2015 at 12:24 PM, Johnny Hughes <johnny at centos.org> wrote: > On 01/19/2015 12:23 PM, Phelps, Matthew wrote: > > On Mon, Jan 12, 2015 at 6:22 PM, Robert Arkiletian <robark at gmail.com> > wrote: > > > >> On Mon, Jan 5, 2015 at 1:13 PM, Robert Arkiletian <robark at gmail.com> > >> wrote: > >> > >>> Johnny,

On Mon, Jan 19, 2015 at 05:55:44PM -0600, Johnny Hughes wrote: > On 01/19/2015 04:10 PM, Robert Arkiletian wrote: > > On Mon, Jan 19, 2015 at 12:24 PM, Johnny Hughes <johnny at centos.org> wrote: > > > >> On 01/19/2015 12:23 PM, Phelps, Matthew wrote: > >>> On Mon, Jan 12, 2015 at 6:22 PM, Robert Arkiletian <robark at gmail.com> > >> wrote:

Latest chromium-el6 at http://people.centos.org/hughesjr/chromium/6/x86_64/RPMS/ is chromium-28.0.1500.95-213514.x86_64.rpm but latest chromium stable is 29.0.1547.xx wondering if there are any problems building version 29?

On Mon, 19 Jan 2015, Johnny Hughes wrote: > On 01/19/2015 06:49 PM, Fred Smith wrote: >> On Mon, Jan 19, 2015 at 05:55:44PM -0600, Johnny Hughes wrote: >>> On 01/19/2015 04:10 PM, Robert Arkiletian wrote: >>>> On Mon, Jan 19, 2015 at 12:24 PM, Johnny Hughes <johnny at centos.org> wrote: >>>> >>>>> On 01/19/2015 12:23 PM, Phelps,

# devtools The aim of `devtools` is to make your life as a package developer easier by providing R functions that simplify many common tasks. Devtools is opinionated about how to do package development, and requires that you use `roxygen2` for documentation and `testthat` for testing. Future version will relax these opinions - patches are welcome! You can track (and contribute to) development of

# devtools The aim of `devtools` is to make your life as a package developer easier by providing R functions that simplify many common tasks. Devtools is opinionated about how to do package development, and requires that you use `roxygen2` for documentation and `testthat` for testing. Future version will relax these opinions - patches are welcome! You can track (and contribute to) development of

# devtools The aim of `devtools` is to make your life as a package developer easier by providing R functions that simplify many common tasks. Devtools is opinionated about how to do package development, and requires that you use `roxygen2` for documentation and `testthat` for testing. Future version will relax these opinions - patches are welcome! You can track (and contribute to) development of

# devtools The aim of `devtools` is to make your life as a package developer easier by providing R functions that simplify many common tasks. Devtools is opinionated about how to do package development, and requires that you use `roxygen2` for documentation and `testthat` for testing. Future version will relax these opinions - patches are welcome! You can track (and contribute to) development of