search for: xerblas

Ok, moved to R-devel. I tried to build R-2.3.1. Since I intent to distribute this tuned R to all other who have a computer like mine here at work I thought it was best to stay with the latest stable release. About your suggestion, I could'n find xerblas.o file. And I don't know how to edit libf77blas.a. I tried to open it with VIM (http://vim.sf.net/) but there was a lot of strange symbols (expected, I think), either way I found a reference to xerblas.o inside it but didn't know what to do with this reference. Thanks, Giuseppe Antonaci On...

Full_Name: G?ran Brostr?m Version: R-2.1.1, 2.2.0 OS: Debian unstable Submission from: (NULL) (213.65.9.59) Some BLAS routines call xerbla for error messages, which results in a message like "LAPACK routine DGER gave error code -9". Suggested solution: In void F77_NAME(xerbla)(char *srname, int *info) { /* srname is not null-terminated. It should be 6 characters. */ char

On Mon, Aug 29, 2005 at 11:48:23AM +0100, Prof Brian Ripley wrote: > On Mon, 29 Aug 2005, G?ran Brostr?m wrote: > >LAPACK/BLAS routines call xerbla "if an input parameter has an > >invalid value" (exact quote from XERBLA at Netlib). Other types of errors > >are not printed (by xerbla), but it is up to the user to check the return > >value of the argument

I think this is not a R-devel question. Sorry to all if I'm wrong, please let me know. I managed to build R successfully with the default BLAS but when I change the MKRULES to use ATLAS BLAS and set the path to "C:/cygwin/home/Administrador/ATLAS/lib/WinNT_ATHLONSSE2" I got the following error message (I'm posting only the final part, there was a lot of compilation before this):

We are trying to install R2.2.1 on a IBM P655 Cluster, SuSE LE 9.1 We are using gcc v 3.3.3 and we are getting this error on make g77 -fPIC -g -O2 -ffloat-store -c dlamc.f -o dlamc.lo g77 -fPIC -g -O2 -c dlapack0.f -o dlapack0.lo g77 -fPIC -g -O2 -c dlapack1.f -o dlapack1.lo g77 -fPIC -g -O2 -c dlapack2.f -o dlapack2.lo g77 -fPIC -g -O2 -c dlapack3.f -o dlapack3.lo g77 -fPIC -g

Good afternoon. I am trying to compile a version of Rblas.dll based on ATLAS for the Corei7. I had remembered that there was mention of which file to adjust and that "xerbla" needed to be removed from one of the outputs from the last time I tried a few years ago. The most recent version of the R Installation manual does not say anything about this. An older version (2.10 I believe) has

Hi, I have tried to pinpoint potential problems which could lead to the LAPACK issues that are currently seen in R. I built the current R trunk using AR=gcc-ar RANLIB=gcc-ranlib ./configure --prefix=$HOME --enable-lto --enable-BLAS-shlib=no --without-recommended-packages and used this to find problem areas. There are quite a few warnings that were flagged, due to mismatches in function

While builds and validations of R-1.6.2beta_2002-12-20 were successful on several systems, there were a few failures: ------------------------------------------------------------------------ Apple Darwin 6.2 (MacOS 10.2.2) with gcc-3.2.1: gcc -dynamiclib -flat_namespace -undefined suppress -o .libs/libgslcblas.0.0.0.dylib sasum.lo saxpy.lo ... isamax.lo izamax.lo xerbla.lo -lc -install_name

Using ATLAS with R is an old topic quite covered in the "R Administration" manual (and by R's "configure" script collection). I still do not easily manage to build R properly on our new AMD Opteron (2-processor). I did work with the current Atlas 3.6.0, configured manually (but "express" version) to build a threaded ATLAS version, and successfully ran Atlas'

Hello I'm trying to run a fortran code which use LAPACK subroutines. I think I should use some points shown in the manual 5.5 Creating shared objects but it is too technical for me :-(... Could anyone help me for the procedure to do: -which part of the manual is relevant for this type of question? actually I'm speaking from writing R extensions, should I read R admin? -point 1.2

> From: Douglas Bates > > How does the Opteron perform on floating point? Can you try something > like > > > mm = matrix(rnorm(1e6), nc = 1e3) > > system.time(crossprod(mm)) > [1] 0.51 0.02 0.53 0.00 0.00 > > system.time(crossprod(mm)) > [1] 0.37 0.03 0.40 0.00 0.00 > > system.time(crossprod(mm)) > [1] 0.38 0.02 0.40 0.00 0.00 > >

Dear Thomas, thank you for your input. I've debugged one of the packages and I confirm that the breakage is related to passing of strings from C to Fortran. Indeed, BLAS and LAPACK define a large number of subroutines that take one or more explicit single-character strings as arguments. Other than that, BLAS has only one function (xerbla), which takes a string of unspecified length,

Hi all, i am trying to compile a test, calling from C code R Lapack shared libraries. In particular, i am calling simple LAPACK driver dposv for solving linear equation system A*x=B with positive definite A. My code looks like the following in solve.c ========================== #include<stdio.h> #include <R_ext/BLAS.h> #include <R_ext/Lapack.h> int main(){

Hi all, I'm stuck in the installation of R. When I run configure, I got the error: configure: error: --with-readline=yes (default) and headers/libs are not available I followed one answer in some post and use this: ./configure --with-prefix=/home/user/R-2.2.1 --with-readline=no It successfully configured but I encountered another problem while make: gcc -shared -L/usr/local/lib64 -o

I'm sorry for having to post this, but I've run out of ideas. I've been trying to build R-2.8.1 from source for installation on FreeBSD 6.4 (seems to be working fine on osx) and keep getting the same results, regardless of how I set ./configure $ ./configure --enable-R-shlib --with-x=no --with-blas FFLAGS="-fpic" R is now configured for x86_64-unknown-freebsd6.0 Source

I am trying to install R-2.3.0 on a 64bit linux box and encounter several error during the make step. I'd appreciate any help. Error messages follow: [root at calculon R-2.3.0]# make make[4]: Entering directory `/state/partition1/apps/packages/R-2.3.0/src/modules/lapack' gcc -shared -L/usr/local/lib64 -o libRlapack.so dlamc.o dlapack0.o dlapack1.o dlapack2.o dlapack3.o cmplx.o

Is there a way to exit gracefully from dynamically loaded Fortran, (several layers down), if an error condition is detected? I.e. suppose I'm within a subroutine called by a subroutine, ..., called by .Fortran(); I want to give up gracefully if an error condition is detected. If I say something like if(x .gt. 42.d0) stop then indeed everything stops, i.e. R falls over. I'd