similar to: R 4.0.2 is released

The build system rolled up R-4.0.1.tar.gz (codename "See Things Now") this morning. The list below details the changes in this release. You can get the source code from http://cran.r-project.org/src/base/R-4/R-4.0.1.tar.gz or wait for it to be mirrored at a CRAN site nearer to you. Binaries for various platforms will appear in due course. For the R Core Team, Peter Dalgaard

The build system rolled up R-4.0.1.tar.gz (codename "See Things Now") this morning. The list below details the changes in this release. You can get the source code from http://cran.r-project.org/src/base/R-4/R-4.0.1.tar.gz or wait for it to be mirrored at a CRAN site nearer to you. Binaries for various platforms will appear in due course. For the R Core Team, Peter Dalgaard

The build system rolled up R-4.0.1.tar.gz (codename "See Things Now") this morning. The list below details the changes in this release. You can get the source code from http://cran.r-project.org/src/base/R-4/R-4.0.1.tar.gz or wait for it to be mirrored at a CRAN site nearer to you. Binaries for various platforms will appear in due course. For the R Core Team, Peter Dalgaard

The build system rolled up R-4.0.3.tar.gz (codename "Bunny-Wunnies Freak Out") this morning. The list below details the changes in this release. You can get the source code from https://cran.r-project.org/src/base/R-4/R-4.0.3.tar.gz or wait for it to be mirrored at a CRAN site nearer to you. Binaries for various platforms will appear in due course. For the R Core Team, Peter

The build system rolled up R-4.0.3.tar.gz (codename "Bunny-Wunnies Freak Out") this morning. The list below details the changes in this release. You can get the source code from https://cran.r-project.org/src/base/R-4/R-4.0.3.tar.gz or wait for it to be mirrored at a CRAN site nearer to you. Binaries for various platforms will appear in due course. For the R Core Team, Peter

The build system rolled up R-4.0.3.tar.gz (codename "Bunny-Wunnies Freak Out") this morning. The list below details the changes in this release. You can get the source code from https://cran.r-project.org/src/base/R-4/R-4.0.3.tar.gz or wait for it to be mirrored at a CRAN site nearer to you. Binaries for various platforms will appear in due course. For the R Core Team, Peter

The build system rolled up R-4.0.0.tar.gz (codename "Arbor Day") this morning. The list below details the changes in this release. You can get the source code from http://cran.r-project.org/src/base/R-4/R-4.0.0.tar.gz or wait for it to be mirrored at a CRAN site nearer to you. Binaries for various platforms will appear in due course. For the R Core Team, Peter Dalgaard These are

The build system rolled up R-4.0.0.tar.gz (codename "Arbor Day") this morning. The list below details the changes in this release. You can get the source code from http://cran.r-project.org/src/base/R-4/R-4.0.0.tar.gz or wait for it to be mirrored at a CRAN site nearer to you. Binaries for various platforms will appear in due course. For the R Core Team, Peter Dalgaard These are

The build system rolled up R-4.0.0.tar.gz (codename "Arbor Day") this morning. The list below details the changes in this release. You can get the source code from http://cran.r-project.org/src/base/R-4/R-4.0.0.tar.gz or wait for it to be mirrored at a CRAN site nearer to you. Binaries for various platforms will appear in due course. For the R Core Team, Peter Dalgaard These are

I know that binary packages are R-version specific, but it was a bit surprising that Rcpp 1.0.5 built with R-4.0.2 cannot be loaded into R-4.0.0. % R-4.0.0 --quiet > library(Rcpp, lib="lib-4.0.2") Error: package or namespace load failed for ?Rcpp? in dyn.load(file, DLLpath = DLLpath, ...): unable to load shared object '/tmp/bill/lib-4.0.2/Rcpp/libs/Rcpp.so':

My system is a dual Xeon E5540 (Nehalem) HP Proliant DL380G6. When switching between Xen 4.0.2-rc1-pre and Xen 4.1-unstable I noticed that the NUMA info as shown by the Xen ''u'' debug-key is different. More specifically, the CPU to node mapping is alternating for 4.0.2 and grouped sequentially for 4.1. This difference affects the allocation (wrt node/socket) of pinned VCPUs to the

I'm preparing a pair of Red Hat Enterprise Linux 3 servers on which to test RAC. Currently they are running the 2.4.21-4.0.2 kernel. I saw that the 1.0.9-9 OCFS binaries are tied to the 4.0.1 kernel, and confirmed that myself. The 1.0.9-12 packages are dated a few days later and don't refer to a specific kernel version, so I assumed they would work with 4.0.2. However, when I try to

> > according to the documentation the option ucode=scan should tell XEN to > > look for a microcode update in an uncompressed initrd. > > > > While I don?t use the Debian kernel the tools to generate the initrd are > > part of Debian. The command ?cpio -i < /boot/initrd.img-4.0.2-Dom0? > > creates the directory structure

On Sat, Jun 16, 2012 at 08:20:23PM +0900, Journeyer J. Joh wrote: > If the cross compiling is supported, is there any documentation on how to > do it? The short version is: assuming you have a cross-binutils installation using e.g. x86_64--netbsd-as and x86_64--netbsd-ld, you add a symlink called x86_64--netbsd-clang to clang and just call that with an appropiate --sysroot to make it find

Dear all, just a little problem report for R 2.2.0 on OpenSuse 10.0-64. Gcc version is 4.0.2 Installing fortran packages runs into: 'cc1' command not found. I apparently got away with: sudo ln -s /usr/bin/cc /usr/bin/cc1 which causes other warnings but the packages seem to function well. Obviously cc1 does no longer exist in gcc 4.0.2. Stefan

So, I have "working" builds of Samba 3.6.10, and 4.0.2 using the traditional build system on AIX, both built with XLC. For historical reasons, we're needing to use 'encrypt passwords = no', so that Samba uses the OS password. The odd thing, is, the 3.6.10 Samba works just fine, but the 4.0.2 doesn't allow connections. Here's the Samba config I'm using on both:

Hello Jeremy & Keir, sorry to be persistent, but the problem that pvops0 kernel 2.6.32.x still does not boot if x > 18 on my machines (and on many other machines, see this mailing list) is not solved yet. Shouldn''t this be a great focus of debugging and fixing? What is the point of having releases for 4.0.2 or 4.1 if I don''t have a dom0 kernel? The last time I tried

Hello, Today I tried to upgrade from samba 4.0.0 to 4.0.3 on my test environment. I patched the source with the diffs patch-4.0.0-4.0.1.diffs, patch-4.0.1-4.0.2.diffs, patch-4.0.2-4.0.3.diffs , then make, make install. # samba-tool dbcheck Checking 807 objects Not fixing nTSecurityDescriptor on CN=Performance Monitor Users,CN=Builtin,DC=inview,DC=local <--- all errors were

I've just updated to R 4.0.2 but am unsure how to get packages from the COPR repository to update to those built under the new version of R. FI - I'm not currently using CoprManager just trying to update/install from terminal. Regards Tim [[alternative HTML version deleted]]

Hello list, I wonder if llvm/Clang can compile C or C++ for ARM from on x86. http://comments.gmane.org/gmane.comp.compilers.clang.devel/8896 The talk above answered 'NO' to my question, which means Clang is not yet able to cross compile for ARM on X86. Is the answer still correct for my question? I saw somewhere that Clang supports ARM on Darwin only. Then is the cross compiling