Fredrik Lundh wrote:
> if you do, it's a SuSE problem (this wouldn't be the first time SuSE
> ships broken Python software)
Thanks for the input .
Following your message I reinstalled python2.4 and the modules
I want to use and now everything is fine.
--
http://mail.python.org/mailman/list
DarkBlue wrote:
> and that's all I did. The suse10.1 installation is pristine
> only auto updated with the latest patches of the day.
if you're using a SuSE-provided python interpreter, you should make to
use the right development files (python-dev, or whatever that's called
over in SuSE land).
Sybren Stuvel wrote:
> file /path/to
I installed the package on other 64 machines running
suse9.2 64 and 9.3 64 without trouble
That's the way :
python setup.py build
result: successfull
python setup.py install
result: successfull
then tried to import and I get the elfclass32 error
and that'
Hello
Suse10.1 64 new install
if I try to import anything into python2.4.2
like : python - c "import kinterbasdb"
I get this : wrong ELF class: ELFCLASS32
Before doing anything wrong , what would be the right thing
to do to get rid of this error ?
Thanks.
--
http://mail.python
