similar to: Help with libiconv problem

Displaying 20 results from an estimated 800 matches similar to: "Help with libiconv problem"

2016 Mar 14
0
Help with libiconv problem
On 3/14/16 1:49 PM, Mick Jordan wrote: > A couple of my colleagues are having problems building R-3.2.4 on Mac > OS X El Capitan somehow related to libiconv. I personally don't have > any problems on either of my Macs. I'm hoping thie make log might > trigger something in the readers of this list: > > gcc -dynamiclib -Wl,-headerpad_max_install_names -undefined >
2015 Oct 09
2
R 3.2.2 64 bit compilation error on AIX
Dear list, I'm following the instructions provided here to compile R 64 bit on AIX 6.1. I did export OBJECT_MODE=64 export CC="gcc -maix64 -pthread" export CXX="g++ -maix64 -pthread" export FC="gfortran -maix64 -pthread" export F77="gfortran -maix64 -pthread" export CFLAGS="-O2 -g -mcpu=power6" export FFLAGS="-O2 -g -mcpu=power6"
2015 Aug 31
2
R doesn't compile on FreeBSD 10.2
On FreeBSD 10.2, I get the following error when compiling R from the Subversion trunk (with "configure && make"): cc -shared -L/usr/local/lib -o tools.so text.o init.o Rmd5.o md5.o signals.o install.o getfmts.o http.o gramLatex.o gramRd.o mkdir ../../../../library/tools/libs installing 'sysdata.rda' Error in dyn.load(file, DLLpath = DLLpath, ...) :
2015 Dec 16
2
Building R in 64-bit mode
Hope I am not sounding too much like a broken record - as far as 64-bit build on AIX is concerned. ** Short - 32-bit builds complete normally, 64-bit builds stop at "installing 'sysdata.rda'" with message: Error: Line starting 'Package: tools ...' is malformed! Execution halted *** Longer... I could file a bug - Importance, showstopper - but I would prefer to better
2015 Aug 31
2
R doesn't compile on FreeBSD 10.2
Prof Brian Ripley writes: > Second, we don't have all the pertinent information such as the > configure options used and the architecture (x86_64?). I am going to > have to guess none as none were mentioned, but using --enable-R-shlib > would be pertinent. > > On 31/08/2015 05:47, Davor Cubranic wrote: >> On FreeBSD 10.2, I get the following error when compiling R
2016 May 03
2
vignette/knitr help
On 5/3/16 11:29 AM, Thierry Onkelinx wrote: > Dear Mick, > > Note that both knitr and rmarkdown are listed under Suggests: both are > required to compile the vignette. Installing rmarkdown should solve > the problem. If not, please provide more information. OS, R version, > digest version, ... > > This is occurring in the context of an automated testing environment that
2016 Mar 15
4
Regression in strptime
>>>>> peter dalgaard <pdalgd at gmail.com> >>>>> on Sat, 12 Mar 2016 19:11:40 +0100 writes: > OK, .Internal is not necessary to reproduce oddity in this area. I also see things like (notice 1980) >> strptime(paste0(sample(1900:1999,80,replace=TRUE),"/01/01"), "%Y/%m/%d", tz="CET") ............... >
2015 Sep 01
2
R doesn't compile on FreeBSD 10.2
I tried compiling using GCC. First, I changed config.site to: ~/R-3.2.2$ svn diff config.site Index: config.site =================================================================== --- config.site (revision 69236) +++ config.site (working copy) @@ -278,3 +278,8 @@ ## Path to the version of pkg-config to be used for locating cairographics. ## PKGCONF = +F77=gfortran48 +FC=${F77} +CC=gcc48
2015 Dec 17
5
Assistance much appreciated
I have been struggling with this error message - and think I finally understand it's context. Start Line by line debugging shows me the function works: ... > saveRDS(val, mapfile) > val $variables $variables$IANA_HTTP_status_code_db [1] 0 1256 $variables$IANA_URI_scheme_db [1] 1256 3458 $variables$table_of_HTTP_status_codes [1] 4714 830 $references named list() $compressed
2015 Oct 09
0
R 3.2.2 64 bit compilation error on AIX
Please note that if I don't specify those variables, then R 32 bit compiles fine. Thanks. -- Vinh On Thu, Oct 8, 2015 at 6:50 PM, Vinh Nguyen <vinhdizzo at gmail.com> wrote: > Dear list, > > I'm following the instructions provided here to compile R 64 bit on > AIX 6.1. I did > > export OBJECT_MODE=64 > export CC="gcc -maix64 -pthread" > export
2015 Dec 16
0
Building R in 64-bit mode
I have been looking further and need some help with: tools:::sysdata2LazyLoadDB("/data/prj/cran/R-3.2.3/src/library/tools/R/sysdata.rda","../../../library/tools/R") Error: Line starting 'Package: tools ...' is malformed! Details: root at x065:[/data/prj/cran/64/R-3.2.3/src/library/tools]export | egrep "PATH|HOME" HOME=/
2014 Jan 18
1
Error when making R in Windows
Hi all, I¡¯m trying to build R (32-bit) under Windows 7 (64-bit). To do so, I just use ¡±make all recommended¡± as mentioned in the documents and it does work for R 2.15.2. However, for R 3.0.2, I get the following error message, gcc -shared -s -static-libgcc -o tools.dll tmp.def text.o init.o Rmd5.o md5.o signals.o install.o getfmts.o http.o
2014 Oct 24
1
Error: Line starting 'Package: tools ...' is malformed!
I'm building R-3.1.1 (64 bit) from source on AIX 7.1. It was going well until I hit this: xlc_r -q64 -Wl,-brtl -Wl,-G -Wl,-bexpall -Wl,-bnoentry -lc -L/opt/freeware/lib64 -L/opt/freeware/lib -Wl,-blibpath:/opt/freeware/lib64:/opt/freeware/lib:/usr/lib:/lib -Wl,-bmaxdata:0x80000000 -o tools.so text.o init.o Rmd5.o md5.o signals.o install.o getfmts.o http.o gramLatex.o gramRd.o -lm make[6]:
2015 Aug 31
0
R doesn't compile on FreeBSD 10.2
First, this there is no evidence here of a 'compilation' failure: it seems to be about installation, and more specifically about loading dynamic libs. Second, we don't have all the pertinent information such as the configure options used and the architecture (x86_64?). I am going to have to guess none as none were mentioned, but using --enable-R-shlib would be pertinent. On
2015 Dec 18
1
Assistance much appreciated
On 2015-12-18 02:29, Simon Urbanek wrote: > Michael, > > I got access to PDP AIX so I can try to replicate your problem. Can you, please, share exactly your setup - AIX version and well as how exactly you installed the compilers (=where from)? I can then try to replicate it. AFAICS there is no official binary for gfortran nor gcc 4.7 so it must be some 3rd party - which could also be a
2015 Sep 01
0
R doesn't compile on FreeBSD 10.2
On 31/08/2015 16:26, Davor Cubranic wrote: > Prof Brian Ripley writes: > >> Second, we don't have all the pertinent information such as the >> configure options used and the architecture (x86_64?). I am going to >> have to guess none as none were mentioned, but using --enable-R-shlib >> would be pertinent. >> >> On 31/08/2015 05:47, Davor Cubranic
2016 Jan 30
4
Sulong
Hi everyone, we started a new open source project Sulong: https://github.com/graalvm/sulong. Sulong is a LLVM IR interpreter with JIT compilation running on top of the JVM. By using the Truffle framework, it implements speculative optimizations such as inlining of function pointer calls through AST rewriting. One area of our research is to provide alternative ways of executing LLVM bitcode that
2015 Sep 01
0
R doesn't compile on FreeBSD 10.2
The datetime.R issue looks familiar. Darwin (the basis for OS X) copied a lot of things from FreeBSD, bugs and all. So I expect the same remedy applies (http://cran.r-project.org/doc/manuals/r-patched/R-admin.html#OS-X): 'Configure option --with-internal-tzcode is the default on OS X, as the system implementation of time zones does not work correctly for times before 1902 or after 2037
2016 May 03
2
vignette/knitr help
I need some help understanding a problem running the tests on the 'digest' package. Initially, I got the message that the 'knitr' package was needed to run vignettes: Running vignettes for package ?digest? Error in loadVignetteBuilder(vigns$pkgdir) : vignette builder 'knitr' not found So I installed the knitr package and all its dependents (?mime?, ?stringi?,
2015 Apr 29
2
--interactive and -f/-e
I was surprised by this: R --interactive -e 'interactive()' bash-3.2$ R -q -e 'interactive()' --interactive > interactive() [1] FALSE > as the command options document says that --interactive should force interactive=TRUE: " When *R* is run in a terminal (via |Rterm.exe| on Windows), it assumes that it is interactive if ?stdin? is connected to a (pseudo-)terminal