search for: dependendi

Hi, I'm quite puzzled by a little bit of code in the DAGCombiner where it merges loads in MergeConsecutiveStores. Two 16bit loads have been merged to one 32bit load, and two 16bit stores have been combined to one 32bit store. And then the code goes like this: // Replace one of the loads with the new load. LoadSDNode *Ld = cast<LoadSDNode>(LoadNodes[0].MemNode);

On an (Intel Leopard) Mac I try to build a package (mxFinance) which depends on another package (mxGraphics). The dependendy is 1) a 'Depends:' in DESCRIPTION and 2) an import in NAMESPACE. - The build fails if the dependent package (mxGraphics) is not installed in the R.framework Do I need to have installed all packages which are required by packages to be built binary (source builds

...------------------------- The 'make' and 'pbuilder' messages come from the build environment. Any idea what is wrong here, and what I'd need to change? Dirk [1] This happens in a chroot(8) ennvironment, from a well-defined and very basic Debian base system. "Build Dependendies" are then installed -- which in this case includes the R 2.0.0 beta from two days ago, as well a large number of other things given all the various header and libs R needs. This process is very close, but not identical to, what the Debian autobuilders use. -- Those are my pr...