similar to: Installation problem from R 2.8.x

Hi all, I'm having trouble getting x11 to work with R. (This is on Debian testing.) I installed r-base and r-base-dev, and then r-cran-cairodevice. I also tried installing the Cairo package within R, which appears to work fine. This what I'm seeing: > capabilities() jpeg png tiff tcltk X11 aqua http/ftp sockets TRUE TRUE TRUE TRUE

Hi - rsync newbie here. I have a situation where I have multiple instances of CMS website code living in the same root directory and having parallel dir structures, so something like this: /my_code/root_dir/instance_1 /my_code/root_dir/instance_2 /my_code/root_dir/instance_3 each instance_n has the same directory structure and owns the same files for the most part with small isolated customer

On Thu, Mar 12, 2015 at 2:25 AM, Rowland Penny <rowlandpenny at googlemail.com> wrote: >> I'm sorry for being so daft, but I am asking you if I need/want to >> join the domain. I do not know the answer. Reminder of my scenario: >> samba is sharing files and users provide their Active Directory >> usernames and passwords to log into to samba. I will call this

If it helps, to see what is involved, outside of a pure IR context, see the example code, and doc at: http://wiki.llvm.org/HowTo:_Build_JIT_based_Exception_mechanism#Source_Code:_exceptionDemo.cpp Although this is a pure example that shows several test cases, including foreign exception interaction, it is not an IR example, but rather a LLVM IR API example. It would be interesting to see a pure

Hello, I am trying to read in elements out of a very large binary file ... the total file is 4 gigs. I want to select rows out of the file, and the current procedure I run works but is prohibitively slow (takes more than a day to run and still won't complete). Is there any faster way to accomplish this? My current procedure looks like this: readHH <- function(file_name,

I am trying to write a wrapper for the last example in help(cv.glm) that deals with leave-one-out-cross-validation (LOOCV) for a logistic model. This wrapper will be used as part of a bigger program. Here is my wrapper funtion : logistic.LOOCV.err <- function( formu=NULL, data=NULL ){ cost.fn <- function(cl, pred) mean( abs(cl-pred) > 0.5 ) glmfit <- glm(

Hello, My centos is 4.8 while I need gtk 2.8 or later. How to upgrade GTK? I'm trying to upgrade manually based on RPMs on 5.X, there are too many decencies when upgrading libX. Is there anybody can give some suggestion to enlighten me? Thanks. - Tommy -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hello All, I do a 4TB filesystem for samba,but in Windows it only display 140GB,How to fix it?

On 01/13/2010 04:08 AM, Garrison Venn wrote: > If it helps, to see what is involved, outside of a pure IR context, > see the example code, and doc at: > > http://wiki.llvm.org/HowTo:_Build_JIT_based_Exception_mechanism#Source_Code:_exceptionDemo.cpp It does, although in the "let me show you why this is too much to tackle" way. > Although this is a pure example that

On Tue, May 12, 2009 at 11:55 PM, Chris Lattner <clattner at apple.com> wrote: > Dan, can you add IVUsers.cpp to the appropriate cmakefile? > > -chris > > > On May 12, 2009, at 10:54 PM, OvermindDL1 wrote: > >> On Tue, May 12, 2009 at 11:40 PM, Chris Lattner <clattner at apple.com> >> wrote: >>> >>> On May 12, 2009, at 10:24 PM,

Does not seem to be a straight error with LLVM itself, but rather the tools, linking issues, here are the errors: Opt: 30> Creating library R:\SDKs\llvm\trunk_VC8_building\lib\Debug\opt.lib and object R:\SDKs\llvm\trunk_VC8_building\lib\Debug\opt.exp 30>LLVMScalarOpts.lib(IndVarSimplify.obj) : error LNK2019: unresolved external symbol "public: bool __thiscall

> This sounds like the ADJCALLSTACK DOWN/UP 'instructions' around the call > aren't set right, or you have declared a SP offset. It doesn't look like > the ARM backend does this, so this is probably the problem. The ARM backend currently doesn't use a frame pointer. It uses the same technique of the PPC backend to avoid add/subs around calls. In the PPC backend we

I’m current debugging one of my LLVM passes which utilized inline assembly. I constantly encounter crashes related to “value materialization”, according to the error messages I received. It seems a big concept in LLVM (or maybe generally in compilation), but I cannot find any document that is comprehensive enough to help me understand what exactly materialization is for. Could someone offer some

we started using an ocfs file system about 4 months ago as the shared archived redo destination for the 4-node rac instances (HP dl380, msa1000, RH AS 2.1) . last night we are seeing some weird behavior, and my guess is the inode directory in the file system is getting corrupted. I've always had a bad feeling about OCFS not being very robust at handling constant file creation and deletion

I put invoke/unwind aside because I couldn't get them to work, but I'm working on my evaluator now and it would be nice to figure this out so I don't have to unwind the stack manually. This was the reason for my earlier question about global declarations, and as that's cleared up I can easily pass exception data...if I can make unwind return out of some deep recursion. The

In ARM the stack should be 8 bytes aligned during function calls. A function that has at least one function call then has a stack size of 8 bytes. PEI::calculateFrameObjectOffsets corretly computes this correctly. The problem is that the alignment is computed before adding space for the call frame size. This is done in emitProlog. Currently the ARM backend has a bug in that it doesn't align

> That is irrelevant. The PEI code needs to know how much stack space is > required for each call to allocate and align the stack frame properly. It > gets this info from the ADJCALLSTACK instructions. I see. Looking at PEI::calculateCalleeSavedRegisters shows that the ADJCALLSTACK instructions is used to set up MaxCallFrameSize. Adding debug prints also show that in the example code

On Aug 26, 2010, at 12:59 PMPDT, Eric Christopher wrote: > On Aug 26, 2010, at 12:25 PM, Yuri wrote: >> On 08/26/2010 11:53, Eric Christopher wrote: >>> Could you get it to print out the instruction when it happens? >>> (just change the line above the error message to print it out to >>> errs()). >>> >>> It basically means that a pseudo

On Sat, 7 Oct 2006, [UTF-8] Rafael Esp?ndola wrote: >> This sounds like the ADJCALLSTACK DOWN/UP 'instructions' around the call >> aren't set right, or you have declared a SP offset. It doesn't look like >> the ARM backend does this, so this is probably the problem. > The ARM backend currently doesn't use a frame pointer. It uses the > same technique

Hi, all: My folders are organized in such a way: root ----branch1 ---------------A -----------------------file1.txt -----------------------file2.txt ---------------B -----------------------file1.txt -----------------------file2.txt ----branch2 ---------------A -----------------------file1.txt -----------------------file2.txt ---------------B -----------------------file1.txt