search for: dependendy

...AG.ReplaceAllUsesOfValueWith(SDValue(Ld, 1), Ld->getChain()); } And here I can't understand why we should replace "the rest" of the load chains with the loads' getChain(). Why should one load be treated in one way, and the rest in some other way? I.e. if there is a chain dependendy to a load, we replace that with the load's chain. Why not replace dependencies to the old loads with dependencies to the new load, just like we do for the first load in the code above. This code was rewritten to how it looks today in a commit 2012-10-03: " Fix a cycle in the DAG. I...

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 are ok)? Cheers, Hans-Pet...

Doing the normal build process [1] for a first time with a R 2.0.0 snapshot -- the Sep 21 version I uploaded to Debian's 'experimental' section two days ago, ended in failure. The package in question is cluster 1.9.6 which should be 2.0.0-ready. The (partial) log follows: ----------------------------------------------------------------------------- [...] g77 -mieee-fp -fPIC -g -O2