Daniel Wheeler | 16 Jun 21:26
Gravatar

Re: Error Condition Re: Installation problems


On Mon, Jun 16, 2008 at 11:02 AM, Jonathan Guyer <guyer@...> wrote:
> Daniel,
>
> I don't know how Recif's first message got through, because he's not a list
> subscriber, but in the meantime, is pysparse supported in 64 bit?

Yes.

>> I am  having trouble installing fipy trunk (v2590) on an AMD 64 processor
>> running Ubuntu 8.04, with pysparse1.0.1.
>>
>> In ipython, when I type: run setup.py test
>>
>> I get the error:
>>
>> /home/recif/FiPy-1.2/fipy/solvers/__init__.py in <module>()

Looks like you are getting an older version of fipy, not trunk.
PYTHONPATH probably needs to point to wherever you put trunk. But this
is not actually the problem.

>>    48 from pysparse import itsolvers
>>    49
>>
>> <type 'exceptions.ImportError'>: libacml.so: cannot open shared object
>> file: No such file or directory
>> WARNING: Failure executing file: <setup.py>

What happens when you type
(Continue reading)

Daniel Wheeler | 16 Jun 22:11
Gravatar

Re: Error Condition Re: Installation problems


On Mon, Jun 16, 2008 at 3:26 PM, Daniel Wheeler
<daniel.wheeler2@...> wrote:

>
> What happens when you type
>
>             python -c "import pysparse; print pysparse.__path__"
>

Sorry, you won't be able to import pysparse. I am wondering if you are
getting different versions of pysparse confused. Did you rebuild
pysparse for 64 bit and where is it installed?

--

-- 
Daniel Wheeler

Recif | 16 Jun 22:53
Favicon

Re: Error Condition Re: Installation problems


Daniel Wheeler <daniel.wheeler2@...> writes:

> What happens when you type
> 
>              python -c "import pysparse; print pysparse.__path__"
> 
> ?
> 
> Cheers
> 

Hi,
Here's the output:
recif <at> rc-desktop:~/tmp$ python -c "import pysparse; print pysparse.__path__"
['/usr/lib/python2.5/site-packages/pysparse']

My original message seems to have got cut off, so I have copied it below.
Thanks for your help.
Recif

 Hi,
 I am  having trouble installing fipy trunk (v2590) on an AMD 64 
 processor running Ubuntu 8.04, with pysparse1.0.1.

 In ipython, when I type: run setup.py test

 I get the error:

 /home/recif/FP/trunk/fipy/models/levelSet/surfactant/
(Continue reading)

Daniel Wheeler | 16 Jun 23:35
Gravatar

Re: Error Condition Re: Installation problems


On Mon, Jun 16, 2008 at 4:53 PM, Recif <recif@...> wrote:

> Hi,
> Here's the output:
> recif <at> rc-desktop:~/tmp$ python -c "import pysparse; print pysparse.__path__"
> ['/usr/lib/python2.5/site-packages/pysparse']

So you can import pysparse. What happens with the following?

    from pysparse import precon

--

-- 
Daniel Wheeler

Recif | 17 Jun 00:16
Favicon

Re: Error Condition Re: Installation problems


Daniel Wheeler <daniel.wheeler2@...> writes:

> 
> 
> On Mon, Jun 16, 2008 at 4:53 PM, Recif <recif@...> wrote:
> 
> > Hi,
> > Here's the output:
> > recif <at> rc-desktop:~/tmp$ python -c "import pysparse; print
pysparse.__path__"
> > ['/usr/lib/python2.5/site-packages/pysparse']
> 
> So you can import pysparse. What happens with the following?
> 
>     from pysparse import precon
> 

$ python -c "import pysparse; from pysparse import precon"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ImportError: libacml.so: cannot open shared object file: 
No such file or directory

However acml.so is in opt/acml4.1.0/ifort64/lib.
I installed pysparse with (in setup.py):
library_dirs_list= ['/opt/acml4.1.0/ifort64/lib','/usr/lib']
libraries_list = ['acml', 'g2c']
superlu_defs = [('USE_VENDOR_BLAS',1)]
f77_defs = []
(Continue reading)

Recif | 17 Jun 15:05
Favicon

Re: Error Condition Re: Installation problems


Recif <recif@...> writes:

Hi,
The installation worked after I added /opt/acml4.1.0/ifort64/lib to the
LD_LIBRARY_PATH environment variable 

When I ran setup.py test, 439 passed, 130 failed

Recif

Daniel Wheeler | 17 Jun 17:29
Gravatar

Re: Error Condition Re: Installation problems


On Tue, Jun 17, 2008 at 9:05 AM, Recif <recif@...> wrote:
>
> Recif <recif@...> writes:
>
>
> Hi,
> The installation worked after I added /opt/acml4.1.0/ifort64/lib to the
> LD_LIBRARY_PATH environment variable

If you can think of a good was to automate this based on OS queries
that we can patch setup.py so that it "just works" without having to
change anything.

>
> When I ran setup.py test, 439 passed, 130 failed
>
> Recif
>
>
>
>
>

--

-- 
Daniel Wheeler

Daniel Wheeler | 17 Jun 17:29
Gravatar

Re: Error Condition Re: Installation problems


On Tue, Jun 17, 2008 at 9:05 AM, Recif <recif@...> wrote:
>
> Recif <recif@...> writes:
>
>
> Hi,
> The installation worked after I added /opt/acml4.1.0/ifort64/lib to the
> LD_LIBRARY_PATH environment variable

Great. I hadn't tried building pysparse with that configuration before.

> When I ran setup.py test, 439 passed, 130 failed

That's quite a lot of failures! Are you referring to the fipy or
pysparse tests? Can you post the test results?

Cheers

--

-- 
Daniel Wheeler

Recif | 18 Jun 15:10
Favicon

Re: Error Condition Re: Installation problems


Daniel Wheeler <daniel.wheeler2@...> writes:

> 
> 
> On Tue, Jun 17, 2008 at 9:05 AM, Recif <recif@...> wrote:
> >
> > Recif <recif@...> writes:
> >
> >
> > Hi,
> > The installation worked after I added /opt/acml4.1.0/ifort64/lib to the
> > LD_LIBRARY_PATH environment variable
> 
> Great. I hadn't tried building pysparse with that configuration before.
> 
> > When I ran setup.py test, 439 passed, 130 failed
> 
> That's quite a lot of failures! Are you referring to the fipy or
> pysparse tests? Can you post the test results?
> 
> Cheers
> 

Hi,
 I have listed the end of the output from when I run 'setup.py test' in ipython:

FAIL: Doctest: examples.levelSet.electroChem.leveler
----------------------------------------------------------------------
Traceback (most recent call last):
(Continue reading)

Daniel Wheeler | 18 Jun 17:02
Gravatar

Re: Error Condition Re: Installation problems


On Wed, Jun 18, 2008 at 9:10 AM, Recif <recif@...> wrote:
> Hi,
>  I have listed the end of the output from when I run 'setup.py test' in ipython:

I believe that ipython alters doctest results. See this thread
<http://thread.gmane.org/gmane.comp.python.ipython.user/2172> and
<http://thread.gmane.org/gmane.comp.python.ipython.user/2130/focus=2136>.
I think you can configure ipython so that it works properly with
doctest, but I don't know how.

Anyway, try running the tests at the command line using "python setup.py test"
and report the results.

Cheers

--

-- 
Daniel Wheeler


Gmane