compilation problem

[U]

Hi Users,

I installed ATLAS libraries in /usr/lib64 library(libatlas.so.3.0,
libclapack.so.3.0, liblapack.so.3.0, libptf77blas.so.3.0,
libcblas.so.3.0, libf77blas.so.3.0 and libptcblas.so.3.0) and I am
using Fedora core 14. After execution command ./configure --libpath=/
usr/lib64 --ptatlas I got next error message:
Configuration failed!

Reason: Could not locate libraries for the following symbols: dsyev_,
ATL_dgemm, dgemm_, daxpy_, cblas_daxpy, ATL_caxpy.

Any help will appreciated.

Thanks,

U.

[Mikio Braun]

Hi U,

There should be a file called configure.log. Can you send it, too?

-M

--
You received this message because you are subscribed to the Google Groups "jblas-users" group.
To post to this group, send email to jblas...@googlegroups.com.
To unsubscribe from this group, send email to jblas-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/jblas-users?hl=en.

[U]

Hi Mikkio,

Searching for command java
Searching for command javac
Setting FOUND_JAVA to true
Setting OS_NAME to Linux
Setting OS_ARCH to amd64
Searching for command gcc
Setting OS_ARCH_WITH_FLAVOR to amd64/sse3
Searching for command nm
Setting NM to nm
Setting FOUND_NM to true
Searching for file /usr/java/jdk1.6.0_27/include/jni.h
Setting JAVA_HOME to /usr/java/jdk1.6.0_27
Searching for command gcc
Searching for command make
Searching for command ld
Setting CC to gcc
Setting CFLAGS to -fPIC
Setting INCDIRS to -Iinclude -I/usr/java/jdk1.6.0_27/include -I/usr/
java/jdk1.6.0_27/include/linux
Setting SO to so
Setting LIB to lib
Setting RUBY to ruby
Setting LDFLAGS to -shared
Setting LD to g77
Setting F77 to g77
Setting CCC to f2c
Setting MAKE to gmake
Searching for file ./lapack-lite-3.1.1/BLAS/SRC/dgemm.f
Setting LAPACK_HOME to
Setting LAPACK_HOME to ./lapack-lite-3.1.1
Setting LINKAGE_TYPE to dynamic
Setting libpath to /usr/lib64/atlas/
Setting BUILD_TYPE to atlas

I also compiled and installed ATLAS library in my home directory, and
after that successfully installed jblas with configuration ./configure
--libpath=/home/u/ATLAS/build/lib/ --ptatlas
But when I had tried java -server -jar jblas-dynamic-Linux-
amd64-1.2.1.jar I got next error message:

Simple benchmark for jblas

Running sanity benchmarks.

checking vector addition... ok
-- org.jblas CONFIG BLAS native library not found in path. Copying
native library from the archive. Consider installing the library
somewhere in the path (for Windows: PATH, for Linux: LD_LIBRARY_PATH).
-- org.jblas CONFIG ArchFlavor native library not found in path.
Copying native library libjblas_arch_flavor from the archive. Consider
installing the library somewhere in the path (for Windows: PATH, for
Linux: LD_LIBRARY_PATH).
-- org.jblas CONFIG Loading libjblas_arch_flavor.so from /lib/dynamic/
Linux/amd64/.
-- org.jblas CONFIG Loading libjblas.so from /lib/dynamic/Linux/amd64/
sse3/.
checking matrix multiplication... ok
checking existence of dsyev...... ok
[-0.21065603010602588, -0.6404447607135406, -0.5071295294530739;
-0.5090854060895623, -0.11644450194791618, 0.7626214072101205;
-0.8075147820730988, 0.40755575681770734, -0.3813107036050603;
0.21065603010602574, 0.64044476071354, -0.12581882584801418]
[17.23368793961409; 1.4142135623730951; 1.2819751242557092E-16]
[-0.47060485181697004, 0.7822176211129874, 0.40824829046386313;
-0.571448748634892, 0.08233869695926208, -0.8164965809277259;
-0.6722926454528144, -0.6175402271944637, 0.408248290463863]
[17.23368793961409; 1.414213562373095; 1.2819751242557092E-16]
checking existence of dgesvd...... ok
Checking complex return values... (z = 6.90529260448504E-310 +
6.9052926045815E-310i)
Check whether we're catching XERBLA errors. If you see something like
"** On entry to DGEMM parameter number 4 had an illegal value", it
didn't work!
** On entry to DGEMM parameter number 4 had an illegal value

Thank you,

U.

On Mar 19, 5:27 pm, Mikio Braun <mikiobr...@googlemail.com> wrote:
> Hi U,
>
> There should be a file called configure.log. Can you send it, too?
>
> -M

[Mikio Braun]

Hi U,

I think your build is ok. The only thing that doesn't work is catching
XERBLA errors (that is, error checking code in the Fortran libraries)
in Java, which means that a basic error in the parameters (for
example, dimensions don't match) won't be converted into a Java
exception but instead crashes the program. Unfortunately, I don't
exactly remember when this did or didn't work as it depends on the
compiler, the linker and a number of other things... .

But the routines themselves seem ok!

-M

--
Dr. Mikio Braun, Beckerstr. 11, 12157 Berlin
Privat: 030 / 42 10 56 42, Büro: 030 / 314 78627, Handy: 0172 / 97 45 676

[Mikio Braun]

Hi U,

I just checked, you're not the first to run into this problem. I'll
put it on my list and will look into it. Currently I don't have that
much time though. I'd suggest that you use the library as is. The
kinds of errors which lead to crashes are more like syntactic errors,
not numerical errors so it is unlikely that your application will
crash if the parameters are generally ok.

I'll let you know when I find something.

-M

[doglic]

I have had the same issue and fixed it by running `make lib' in the lapack folder together with the specified `make -k ...'. After it you have to rebuild the atlas using the just compiled lapack.

It worked for me, hope it works for you too.