similar to: Use of PKG_FFLAGS on Windows

I often use a debug flag (set to TRUE) to turn on various debugging print statements in my R scripts.  I was thinking I should create a function debugPrint(object,debugFlag), to print out the object name and contents if the debugFlag is set to TRUE.  Then I wouldn't have to make my script ugly(..er) than it already is by adding IF statements all over the place.  I've seen how ls() dumps

On Monday 21 December 2009 10:14, Török Edwin wrote: > On 2009-12-21 18:06, David Greene wrote: > > On Saturday 19 December 2009 00:16, Chris Lattner wrote: > >>> Or I think I can just assume (Yikes!) that if the signal handler is > >>> invoked it will really be a circular_raw_ostream since the handler > >>> should (!) only be set up in debug mode. >

Dear all, Please take my apologies if that has already been asked - at least I couldn't find it in the archives. When trying to specify a layout within library lattice, i.e. using xyplot, I get an error when the prepanel function tries to subscript the automatically generated x.limits. This seems to appear if the last page wouldn't be filled completely, i.e. there would be space left

Dear Fred, If x1 and x2 are *not* normally distributed, you can use independent component analysis (ICA) which is based on the idea that x will be "more normal" than either x1 and x2 following the central limit theorem. See package(fastICA) by JL Marchini, C Heaton, and BD Ripley for details. HTH Thomas > -----Original Message----- > From: Feng Zhang [mailto:f0z6305 at

Hi, I'm searching for a way to override the default CFLAGS/FFLAGS (-g -02 in my case) per package (e.g with "-g" for packages under development). PKG_CFLAGS/PKG_FFLAGS is prepended to the remaining flags, so it can't delete a globally set "-O2" flag. Of course I can edit the global Makeconf file, but I was wondering if there is a possibility to override variables from

Dear all, Maybe this has something to do with R crashing? When my R version crashes, there is Rgui.exe still running in the background (i.e. W2K's task manager recognises it only as a process, which apparently is using almost 100% of the CPU). I can reproduce that by "using" the SJava package (from Brian Ripley's homepage, as suggested on http://www.omegahat.org/RSJava/).

Chris Lattner wrote: > On Jan 19, 2009, at 7:55 AM, Andrew Haley wrote: > >> This is x86_64. I have a problem where an absolute memory load >> The current LLVM trunk does not have this bug. This seems quite a >> nasty >> bug; is there any chance of a bug-fix release for LLVM 2.4, or >> should I >> just use LLVM trunk until LLVM 2.5 ? > > As

On Saturday 19 December 2009 00:16, Chris Lattner wrote: > > Or I think I can just assume (Yikes!) that if the signal handler is > > invoked it will really be a circular_raw_ostream since the handler > > should (!) only be set up in debug mode. > > > > That scares me a bit, though. > > Why don't you just check #ifndef NDEBUG like the code that sets it up?

Hi. I am trying to run LLVM with JIT on ARM processor (Android phone). Currently I have problems using external functions. Any call to external function crashes and gives me signal 11 (SIGSEGV) at some random address. I'm trying to run following C code: *** extern void add1(int* x); int main() { int a = 10; int b = 20; add1(&b); int c = a + b; return c; } *** It gives

Hi, all: I want to call a c program in the windows version R, so I installed ActivePerl and MinGw, wrote the code below in command prompt: Rcmd SHLIB filename.c and I got the error message as follows: Error: c:/R/rw1071/src/gnuwin32/MakeDLL 16: common syntax error. ..... There are errors on line 16 18 20 22 25 28 43 44 45 47 49 50 51 52 53 79 80 81 83. Has any one met the same problem

Hello, I would like to build shared lib for R using cygwin environment. After installing needed tools (mainly perl, make and compilers), I ran R CMD SHLIB hw.c But I get the following error : $ R CMD SHLIB hw.c c:/PROGRA~1/R/R-26~1.2/src/gnuwin32/MakeDll:82: *** multiple target patterns. Stop. Google it didn't give me any hints. Thanks for your help. Sylvain Archenault.

Hi Eric and thanks for your answer, What I mean is that I want to find the number of line on the IR code of a specific instruction. I found out that I can use: DebugLoc Loc = CurrentInstruction->getDebugLoc(); unsigned Line = Loc.getLine(); But this works only if DEBUGFLAG is True. I'd like to be able to get the Line number without being on a 'Debug' mode. Is

On Dec 21, 2009, at 8:42 AM, David Greene wrote: > On Monday 21 December 2009 10:14, Török Edwin wrote: >> On 2009-12-21 18:06, David Greene wrote: >>> On Saturday 19 December 2009 00:16, Chris Lattner wrote: >>>>> Or I think I can just assume (Yikes!) that if the signal handler is >>>>> invoked it will really be a circular_raw_ostream since the

On Jan 20, 2009, at 2:10 AM, Andrew Haley wrote: > Chris Lattner wrote: >> On Jan 19, 2009, at 7:55 AM, Andrew Haley wrote: >> >>> This is x86_64. I have a problem where an absolute memory load >>> The current LLVM trunk does not have this bug. This seems quite a >>> nasty >>> bug; is there any chance of a bug-fix release for LLVM 2.4, or

Hi, All, I have come across a problem building a DLL from .f90 source (R 2.3.1, Windows XP). When using the R CMD SHLIB procedure, the DLL itself was being built, but its export table was empty. Among the output from R CMD SHLIB the following message appeared: c:\mingw\bin\nm.exe: 'a.out': No such file The reason is the empty list of dependencies in the pattern rule for DLLs

>This mean that the specs file of Cygnus gcc is different from the >mingw32 one. OK thanks (I added main() {} as per FAQ and I got the dynload to build a dll ok) I am also interested in building the R sources as per your descriptions. To simplify things, I have removed b18 cygwin and have now installed egcs-mingw32 with your djtools as recommended. Everything seems to work OK; tools that

Dear R-help, I'm having problem creating a dll using Rcmd SHLIB with R-1.3.1 on WinNT4: C:\TEMP>Rcmd SHLIB tryf.o make[1]: `libR.a' is up to date. make: *** No rule to make target `'tryf.o', needed by `tryf.a'. Stop. C:\TEMP>Rcmd SHLIB tryf.f make[1]: `libR.a' is up to date. make: *** No rule to make target `'tryf.o', needed by `tryf.a'. Stop. I

Dear R-help, I'm having problem creating a dll using Rcmd SHLIB with R-1.3.1 on WinNT4: C:\TEMP>Rcmd SHLIB tryf.o make[1]: `libR.a' is up to date. make: *** No rule to make target `'tryf.o', needed by `tryf.a'. Stop. C:\TEMP>Rcmd SHLIB tryf.f make[1]: `libR.a' is up to date. make: *** No rule to make target `'tryf.o', needed by `tryf.a'. Stop. I

Hi, I am attempting install of samba 2.2.7 on a Sequent (IBM) Dynix 4.4.6 platform. I downloaded the samba-latest.tar from the samba website: samba.mirror.ac.uk/samba/download.html Having unzipped and untarred the file, I then started as per the "how to", very first part. I ran "./configure" which generated a number of messages before failing as follows: ... ... ...

Yes, changing line 67 of SHLIB as Uwe suggested worked: C:\TEMP>Rcmd SHLIB tryf.f make[1]: `libR.a' is up to date. rm -f -f tryf.a ar cr tryf.a *.o ranlib tryf.a ------- Building tryf.dll from tryf.a -------- echo LIBRARY tryf > tryf.def echo EXPORTS >> tryf.def nm tryf.a > Defs sed -n '/^........ [BCDRT] _/s/^........ [BCDRT] _/ /p' Defs >> tryf.def rm -f Defs