Joe schrieb:
Your installation process is botched (no idea why, you don't show us
setup.py or anything else I asked for).
Sorry, but I do know how it's currently installed is exactly the way I
need it to be installed.
It is? It wasn't working until you fiddled with sys.path - which you
neede
> Your installation process is botched (no idea why, you don't show us
> setup.py or anything else I asked for).
Sorry, but I do know how it's currently installed is exactly the way I
need it to be installed.
>
>
> All that is missing is what I've asked you now several times before:
> _moda.so
Joe wrote:
>> No, the import-mechanism of python doesn't take LD_LIBRARY_PATH into
>> account, and even if it did - _moda.la is a simple archive-file, not a
>> shared library. It can't be dynamically loaded. Something in your
>> build-process is not working.
>
> So how should my stuff find these
On Thu, Dec 10, 2009 at 9:56 AM, Joe wrote:
>> No, the import-mechanism of python doesn't take LD_LIBRARY_PATH into
>> account, and even if it did - _moda.la is a simple archive-file, not a
>> shared library. It can't be dynamically loaded. Something in your
>> build-process is not working.
>
> So
> No, the import-mechanism of python doesn't take LD_LIBRARY_PATH into
> account, and even if it did - _moda.la is a simple archive-file, not a
> shared library. It can't be dynamically loaded. Something in your
> build-process is not working.
So how should my stuff find these libs?
Here's what I
Joe wrote:
> Just to clarify, I have "_moda.la" sitting in another directory which is
> included in my LD_LIBRARY_PATH. And it is built for the 64bit arch.
No, the import-mechanism of python doesn't take LD_LIBRARY_PATH into
account, and even if it did - _moda.la is a simple archive-file, not a
s
Just to clarify, I have "_moda.la" sitting in another directory which is
included in my LD_LIBRARY_PATH. And it is built for the 64bit arch.
--
http://mail.python.org/mailman/listinfo/python-list
>
> Please verify that it exists and has the proper architecture.
>
Ah, ok, I thought those were one in the same. But I do have that file in
another directory elsewhere and I have that directory in my
LD_LIBRARY_PATH var.
Shouldn't that be enough to do it?
--
http://mail.python.org/mailman
Joe wrote:
> Diez B. Roggisch wrote:
>> Joe wrote:
>>
But it's searching for _moda.*, most probably a binary extension. Does
that exist, and if yes, has it the proper architecture or is it maybe
32 bit?
>>> I'm just going by an example script. moda is a package I was given that
>>>
Diez B. Roggisch wrote:
> Joe wrote:
>
>>> But it's searching for _moda.*, most probably a binary extension. Does
>>> that exist, and if yes, has it the proper architecture or is it maybe 32
>>> bit?
>> I'm just going by an example script. moda is a package I was given that
>> is written in C and
Joe wrote:
>> But it's searching for _moda.*, most probably a binary extension. Does
>> that exist, and if yes, has it the proper architecture or is it maybe 32
>> bit?
>
> I'm just going by an example script. moda is a package I was given that
> is written in C and has some python bindings and d
> But it's searching for _moda.*, most probably a binary extension. Does that
> exist, and if yes, has it the proper architecture or is it maybe 32 bit?
I'm just going by an example script. moda is a package I was given that
is written in C and has some python bindings and does run 64-bit. I'm on
Joe wrote:
> I am trying to write/run a python script which imports from another
> script which is located in my /usr/lib64/python2.6/site-packages/ dir,
> but getting the following error.
>
> $ python ./mytest.py
> Traceback (most recent call last):
> File "./mytest.py", line 45, in
> f
13 matches
Mail list logo
