search for: biarch

I'm experimenting with 6.2 now. Things seem to be really great so far! Distribution closure is one of my favourite pets. So I tried to install everything. I found only one problem, but that's another (minor) thing. But I found almost nothing under /usr/lib. So, Biarch is really dead? Funny! A couple of years back, I finally opted for CentOS instead of Debian just because of Biarch ... I'm getting real old ... -Michael

I'm having problems getting R CMD check to work correctly on Windows 7 (64 bit) in a package that uses C code. What I want to do is to be able to pass the equivalent of the "--force-biarch" option to check, but this is only supported for INSTALL. Background: I'm writing a package (RNetica) which forms a link between R and a third-party library (Netica.dll). The vendor supplies this library in both a 32 bit and a 64 bit version. Under Linux, I use configure to link against...

I'm having problems getting R CMD check to work correctly on Windows 7 (64 bit) in a package that uses C code. What I want to do is to be able to pass the equivalent of the "--force-biarch" option to check, but this is only supported for INSTALL. Background: I'm writing a package (RNetica) which forms a link between R and a third-party library (Netica.dll). The vendor supplies this library in both a 32 bit and a 64 bit version. Under Linux, I use configure to link against...

...Hal Finkel wrote: > By default it should build for > whatever the current host is (no special flags required). To > specifically build for something else, use: > -ccc-host-triple powerpc64-unknown-linux-gnu > or > -ccc-host-triple powerpc-unknown-linux-gnu So LLVM isn't biarch capable? Meaning one LLVM compiler cannot generate both 32-bit and 64-bit binaries? Peter

On Tue, 01 May 2012 17:23:07 -0500 Peter Bergner <bergner at vnet.ibm.com> wrote: > On Tue, 2012-05-01 at 16:06 -0500, Hal Finkel wrote: > > LLVM/clang now will build in the normal way (./configure; make > > install) on PPC (you'll need at least the 3.1 release candidate (or > > trunk)). I generally build on my PPC64 hosts with: > > make ENABLE_OPTIMIZED=1

...librdmac * librdmac-devel * sanlock-libs * sanlock-devel and maybe others. Is this on purpose (I don't know if upstream has removed or updated the 32-bit rpms, but the old ones are still in C6.3/x86_64), or is it just the usual sloppyness (I've been told here on previous occasions the biarch is a pain in the ass to maintain, nobody cares anyway, it's not 'plain', and no sensible man should be using it). -Michael

...it should build for > > whatever the current host is (no special flags required). To > > specifically build for something else, use: > > -ccc-host-triple powerpc64-unknown-linux-gnu > > or > > -ccc-host-triple powerpc-unknown-linux-gnu > > So LLVM isn't biarch capable? Meaning one LLVM compiler cannot > generate both 32-bit and 64-bit binaries? Sorry for replying to my own message, but... Oh, -ccc-host-triple is a compiler option and not a configure option. That does work, though it seems I have to link with gcc, since llvm still wants to link agai...

...e differently did not come from better compilation - it is in 3 unrelated areas, one of the problematic: - the snowleopard builds come the manuals in pdf's, mavericks don't. That's about 14MB. - a few bundled gcc runtime libraries (libgcc/libfortran...) are quad arch in the former, and biarch in the latter. That's another 6 MB. - the missing tiff functionality. That affects both R_X11.so and cairo.so, and add up to about 1.5MB. And the 18-20MB difference compress down to 14MB. I don't know whether it actually offers any speed advantage, but I'd probably suggest stay away...

...whatever the current host is (no special flags required). To > > > specifically build for something else, use: > > > -ccc-host-triple powerpc64-unknown-linux-gnu > > > or > > > -ccc-host-triple powerpc-unknown-linux-gnu > > > > So LLVM isn't biarch capable? Meaning one LLVM compiler cannot > > generate both 32-bit and 64-bit binaries? > > Sorry for replying to my own message, but... > > Oh, -ccc-host-triple is a compiler option and not a configure option. > That does work, though it seems I have to link with gcc, since...

Hi, I think I've found a bug in R CMD INSTALL. When it tries to parse a DESCRIPTION file with an invalid LazyData field, it errors out while trying to print the correct error message: > R CMD INSTALL . * installing to library ?/home/example/R/x86_64-pc-linux-gnu-library/3.4? * installing *source* package ?samplepackage? ... ** data Error in errmsg("invalid value of ", field,

I've been developing a package to use S3 bucket on AWS by using libs3 code. I have two problems. The first is, by standard, it will attempt to install i386 and x64 if I don't have a configure.win. The problem with this is that while everything appears to compile correctly, I get this error when trying to load the x64 library: "LoadLibrary error: %1 is not a valid Win32

On biarch kernels, it is not safe to do copy from/to user, even with use_mm, unless we checked the address range with access_ok previously. Implement these checks to enforce safe memory accesses. Reported-by: Al Viro <viro at zeniv.linux.org.uk> Signed-off-by: Michael S. Tsirkin <mst at redhat.com...

On biarch kernels, it is not safe to do copy from/to user, even with use_mm, unless we checked the address range with access_ok previously. Implement these checks to enforce safe memory accesses. Reported-by: Al Viro <viro at zeniv.linux.org.uk> Signed-off-by: Michael S. Tsirkin <mst at redhat.com...

...fail), and a .First.lib() function in a package will be ignored (with an installation warning for now). As an exception, packages without a R directory and no NAMESPACE file can still be installed. o Packages can specify in their DESCRIPTION file a line like Biarch: yes to be installed on Windows with --force-biarch. o Package vignettes can now be processed by other engines besides Sweave; see 'Writing R Extensions' and the tools::vignetteEngine help topic for details. o The *.R tangled source code for vignettes is now inc...

...fail), and a .First.lib() function in a package will be ignored (with an installation warning for now). As an exception, packages without a R directory and no NAMESPACE file can still be installed. o Packages can specify in their DESCRIPTION file a line like Biarch: yes to be installed on Windows with --force-biarch. o Package vignettes can now be processed by other engines besides Sweave; see 'Writing R Extensions' and the tools::vignetteEngine help topic for details. o The *.R tangled source code for vignettes is now inc...

This patch set should make it easier to maintain PV-GRUB2 installations. The general idea is based on discussions I had with Xen developers (mainly Ian Jackson) at the Ubuntu Developer Summit in May 2011; though I never did manage to get the core port done and Vladimir beat me to that, I think the configuration approach we discussed there is still valid and useful. The idea here is that people