search for: installc5ca415e4310

...name, 1L). That in turn calls the > C library function access(..., X_OK). The ... is the name of the file, > translated into the local encoding and expanded. As far as I can see, > that means ... should be exactly the string below. > > > > [1] "/tmp/RtmpMM6iC1/R.INSTALLc5ca415e4310/stringi" > > The only thing I can think of is that your system is protecting you from > executing a newly created file until some sort of virus or other check > is done. (This is common on Windows, but I've never heard of it before > on Linux.) Just a thought - ar...

...ilename, 1L). That in turn calls the > C library function access(..., X_OK). The ... is the name of the file, > translated into the local encoding and expanded. As far as I can see, > that means ... should be exactly the string below. > > > > [1] "/tmp/RtmpMM6iC1/R.INSTALLc5ca415e4310/stringi" > > The only thing I can think of is that your system is protecting you from > executing a newly created file until some sort of virus or other check > is done. (This is common on Windows, but I've never heard of it before > on Linux.) Just a thought - are yo...

I am using debug on the .install_packages function...stepping through. Once the temporary folder is created and the tar file expanded I run file_test and get a FALSE back indicating that the configure file is not executable. [1] "/tmp/RtmpMM6iC1/R.INSTALLc5ca415e4310/stringi" Browse[2]> dir(new) [1] "DESCRIPTION" "INSTALL" "LICENSE" "MD5" [5] "NAMESPACE" "NEWS" "R" "cleanup" [9] "configure" "configure.win" &qu...

...") calls file.access(filename, 1L). That in turn calls the C library function access(..., X_OK). The ... is the name of the file, translated into the local encoding and expanded. As far as I can see, that means ... should be exactly the string below. > > [1] "/tmp/RtmpMM6iC1/R.INSTALLc5ca415e4310/stringi" The only thing I can think of is that your system is protecting you from executing a newly created file until some sort of virus or other check is done. (This is common on Windows, but I've never heard of it before on Linux.) Hopefully someone else can help... Duncan Murdoc...

...ilename, 1L). That in turn calls the > C library function access(..., X_OK). The ... is the name of the file, > translated into the local encoding and expanded. As far as I can see, > that means ... should be exactly the string below. > > > > [1] "/tmp/RtmpMM6iC1/R.INSTALLc5ca415e4310/stringi" > > The only thing I can think of is that your system is protecting you from > executing a newly created file until some sort of virus or other check > is done. (This is common on Windows, but I've never heard of it before > on Linux.) Just a thought - are yo...

On 22/06/2017 3:42 PM, Conklin, Mike (GfK) wrote: > Not much progress..... I step through debug and it gets to the do.install() function which immediately errors with the same "configuration not executable" error. I believe that is a locally defined function, which means you can set a breakpoint within it but only if R is compiled with source info, or you can manually call

Not much progress..... I step through debug and it gets to the do.install() function which immediately errors with the same "configuration not executable" error. So, made a tempfunc that was a copy of tools:::.install_packages and edited the file_test("-x","configure") line to return a TRUE now I get a Permission Denied error (even if I run as root) >