Thanks for your help. It turned out I was working with a 32-bit installation of python, that was the source of my trouble.

-Leland

On 2/3/2012 7:51 PM, Fausto Arinos de A. Barbuto wrote:

A question: do you have liblapack-dev and libblas-dev installed? They seemingly are essential to compiling pysparse(you may still have other unresolved dependencies, though). You might also try to compile the package as "root". Also, run "python setup.py build" first, and then
"python setup.py install".  That worked on my 64-bit architecture.

F.


    ------------------------------------------------------------------------
    *From:* Leland M Barnard <[email protected]>
    *To:* [email protected]
    *Sent:* Wednesday, February 1, 2012 7:40:22 PM
    *Subject:* Requesting help with a problem installing PySparse

    I'm trying to set up fipy to run on a 64 bit red hat linux machine
    (specifically Rocks v5.2).  We have gcc v4.1.2  We also have the
    Enthought python distribution with python 2.7.

    I'm having trouble installing pysparse v1.1.1.  When I use the command

    python setup.py install

    I receive this error message:

    running install
    running build
    running build_py
    running build_ext
    building 'pysparse.spmatrix' extension
    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -O2 -fPIC -DNUMPY=1
    -DLENFUNC_OK=1 -IInclude
    
-I/share/apps/Python2.7/epd-7.1-2-rh5-x86/lib/python2.7/site-packages/numpy/core/include

    -I/share/apps/Python2.7/epd-7.1-2-rh5-x86/include/python2.7 -c
    Src/spmatrixmodule.c -o
    build/temp.linux-x86_64-2.7/Src/spmatrixmodule.o
    In file included from
    /share/apps/Python2.7/epd-7.1-2-rh5-x86/include/python2.7/Python.h:58,
                      from Src/spmatrixmodule.c:1:
    /share/apps/Python2.7/epd-7.1-2-rh5-x86/include/python2.7/pyport.h:849:2:
    error:
    #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc
    config?)."
    error: command 'gcc' failed with exit status 1

    I also tried pysparse v1.2 with the same result (in addition to some
    library linking errors that I'll also probably have to fix).

    I was hoping there might be someone else on the mailing list that
    encountered this and might have a solution.  Please let me know if
    there
    is any more information I can supply that might be helpful in
    diagnosing
    the trouble.  Thanks!

    VTY,
    Leland Barnard

    _______________________________________________
    fipy mailing list
    [email protected] <mailto:[email protected]>
    http://www.ctcms.nist.gov/fipy
      [ NIST internal ONLY: https://email.nist.gov/mailman/listinfo/fipy ]




_______________________________________________
fipy mailing list
[email protected]
http://www.ctcms.nist.gov/fipy
   [ NIST internal ONLY: https://email.nist.gov/mailman/listinfo/fipy ]

_______________________________________________
fipy mailing list
[email protected]
http://www.ctcms.nist.gov/fipy
  [ NIST internal ONLY: https://email.nist.gov/mailman/listinfo/fipy ]

Reply via email to