Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #4432

Re: Compile 32bit C-lib on 64 bit

From Nobody <nobody@nowhere.com>
Subject Re: Compile 32bit C-lib on 64 bit
Date 2011-05-02 03:20 +0100
Message-Id <pan.2011.05.02.02.20.19.656000@nowhere.com>
Newsgroups comp.lang.python
References <mailman.1045.1304280864.9059.python-list@python.org>
Organization Zen Internet

Show all headers | View raw


On Sun, 01 May 2011 22:14:14 +0200, Hegedüs Ervin wrote:

> When I'm compiling it on 64bit, gcc says:
> 
> /usr/bin/ld: skipping incompatible /lib32/lib3rdpartyCrypt.so when
> searching for -l3rdpartyCrypt
> 
> There _is_ the .so in /lib32 directory:
> 
> ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically
> linked, stripped
> 
> 
> What is the correct solution?

You need to build your module for a 32-bit version of Python.

On a 64-bit system, each process is either 32-bit or 64-bit process. You
can't mix 32-bit code and 64-bit code in a single process. If you have to
use that library and you only have a 32-bit version of it, then everything
else must also be 32-bit: the Python interpreter, your binary module, and
all of the libraries which it uses.

Back to comp.lang.python | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

Compile 32bit C-lib on 64 bit Hegedüs Ervin <airween@gmail.com> - 2011-05-01 22:14 +0200
  Re: Compile 32bit C-lib on 64 bit Nobody <nobody@nowhere.com> - 2011-05-02 03:20 +0100
    Re: Compile 32bit C-lib on 64 bit Hegedüs, Ervin <airween@gmail.com> - 2011-05-02 08:43 +0200
  Re: Compile 32bit C-lib on 64 bit Jorgen Grahn <grahn+nntp@snipabacken.se> - 2011-05-02 08:31 +0000

csiph-web