Hi,
there should be one more file called configure.log or so. Can you send it as well?
-M
> I just pushed so...
hm... it seems I removed the relevant parts in the log some time
ago... . One idea was that you probably don't have the full lapack
libraries installed. Atlas provides only a subset of all lapack
routines, and dsyev is meant to check that. Try also installing the
package "liblapack-dev".
> gcc -shared -o native/NativeBlas.so native/NativeBlas.o -Wl,-
> z,muldefs ./ATLAS/build/lib/liblapack.a ./ATLAS/build/lib/
> libf77blas.a ./ATLAS/build/lib/libcblas.a ./ATLAS/build/lib/libatlas.a
> -l:libgfortran.a
> /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/4.4.1/
> libgfortran.a(transfer.o): relocation R_X86_64_32 against `.bss' can
> not be used when making a shared object; recompile with -fPIC
> /usr/lib/gcc/x86_64-linux-gnu/4.4.1/libgfortran.a: could not read
> symbols: Bad value
> collect2: ld returned 1 exit status
> make: *** [native/NativeBlas.so] Error 1
Ah, I think this is an old bug I also thought I had fixed... . On
64bit, the linker is more picky with respect to -fPIC and shared
libraries (I think for 32bit, all code is basically position
independent). Can you try editing configure.out by hand and replace
"-l:libgfortran.a" with "-lgfortran" and then start again at "make
realclean all"?
-M
--
Dr. Mikio Braun, Beckerstr. 11, 12157 Berlin
Privat: 030 / 42 10 56 42, Büro: 030 / 314 78627, Handy: 0172 / 97 45 676
thanks for your kind patience! And sorry for all the hassle. Probably
the easiest thing is if I could send you a fat-jar for linux/64bit.
I'll try to compile one tomorrow for you to try. If you still want to,
there are two things, you can try: Building against your own ATLAS and
building a jar file which does not include the ATLAS routines but
links them dynamically.
Now I remembered that building against the ubuntu static libs (ending
in *.a) won't work as those are not compiled with the -fPIC flag
(position independent code). In short, you cannot build a dynamic lib
including static libs unless you compiled them with -fPIC in the first
place. Therefore, you have to use the self-compiled ones (adding -fPIC
everywhere while compiling ATLAS as well as LAPACK/BLAS, I think that
is covered in the BUILDING_ATLAS file.)
Then, you can try to do the "-l:libgfortran.a" -> "-lfortran" change
and it hopefully compiles successfully.
You can also try to run configure without options, and compile to a
jar file which still depends on atlas etc. (I called this "dynamic"
for some reason):
./configure
make realclean all
ant dynamic-lean-jar
java -jar jblas-dynamic-Linux-amd64-1.0.3.jar --debug
I put a jar with ATLAS statically compiled in here:
http://mikiobraun.de/jblas/jblas-static-Linux-amd64-1.0.3.jar
Let me know whether it works for you!
thanks for the links. By the way, if you find some specific routines
missing from jblas, just drop me a line. Usually, it's quite simple to
add it.
Best,
Mikio
> --
> 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.
Hello OP,