[Numpy-discussion] Building Numpy: could not read symbols Bad value error

Charles R Harris charlesr.harris@gmail....
Sat Jun 19 17:19:33 CDT 2010


On Sat, Jun 19, 2010 at 4:01 PM, Michael Green <mishagreen@gmail.com> wrote:

> Well I used the instructions found here
> <
> http://www.scipy.org/Installing_SciPy/Linux#head-eecf834fad12bf7a625752528547588a93f8263c
> >
>
> I started by building lapack and it built successfully.
>
> I then proceeded with ATLAS using the following configure line (that
> does contain -fPIC):
> ../configure -Fa alg -fPIC -Ss flapack
> /usr/local/src/lapack-3.1.1/lapack_LINUX.a
>
> and then
> make
> cd lib
> make shared
>
> I'm getting
> [root@localhost lib]# make shared
> rm -f libatlas.so liblapack.so
> make libatlas.so libf77blas.so libcblas.so liblapack.so
> make[1]: Entering directory `/usr/local/src/ATLAS/ATLAS_LINUX/lib'
> ld -melf_x86_64 -shared -soname /usr/local/atlas/lib/libatlas.so -o
> libatlas.so \
>           -rpath-link /usr/local/atlas/lib \
>           --whole-archive libatlas.a --no-whole-archive -lc -lm
> ld: libatlas.a(ATL_dger2k__2.o): relocation R_X86_64_32 against `a
> local symbol' can not be used when making a shared object; recompile
> with -fPIC
> libatlas.a(ATL_dger2k__2.o): could not read symbols: Bad value
> make[1]: *** [libatlas.so] Error 1
> make[1]: Leaving directory `/usr/local/src/ATLAS/ATLAS_LINUX/lib'
> make: *** [shared] Error 2
>
> This error looks similar to the one I've been getting with numpy.
> Please help.
>
>
Have you checked the actual configuration that was used to compile lapack,
*not* the command line flags. I never had with success with the automatic
builds using the compressed files. Also check the actual installed libraries

<snip>

Chuck
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.scipy.org/pipermail/numpy-discussion/attachments/20100619/87993116/attachment-0001.html 


More information about the NumPy-Discussion mailing list