Received: (at submit) by bugs.debian.org; 7 Mar 1997 02:33:40 +0000 Received: (qmail 23253 invoked from network); 7 Mar 1997 02:33:40 -0000 Received: from A-abe.resnet.ucsb.edu (graham@128.111.31.63) by master.debian.org with SMTP; 7 Mar 1997 02:33:40 -0000 Received: (from graham@localhost) by A-abe.resnet.ucsb.edu (8.8.5/8.8.5) id SAA01246; Thu, 6 Mar 1997 18:24:41 -0800 Date: Thu, 6 Mar 1997 18:24:41 -0800 From: "Graham C. Hughes" <graham.hughes@resnet.ucsb.edu> Message-Id: <199703070224.SAA01246@A-abe.resnet.ucsb.edu> To: graham@A-abe.resnet.ucsb.edu, submit@bugs.debian.org Subject: python-mpz: Incorrect library settings when compiling Python Package: python-mpz Version: 1.4.0-4 I've seen this before, from when I administrated a Slackware machine: graham@A-abe:~$ python Python 1.4 (Mar 4 1997) [GCC 2.7.2.1 Objective-C snapshot 960906] Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam >>> import mpz python: can't resolve symbol 'mpz_powm' python: can't resolve symbol 'mpz_com' python: can't resolve symbol 'mpz_get_ui' python: can't resolve symbol 'mpz_sqrt' python: can't resolve symbol 'mpz_abs' ... python: can't resolve symbol 'mpz_mul' python: can't resolve symbol 'mpz_set_ui' python: can't resolve symbol 'mpz_mmod' python: can't resolve symbol 'mpz_ior' Traceback (innermost last): File "<stdin>", line 1, in ? ImportError: Unable to resolve symbol >>> The problem is that somebody somewhere isn't sticking a -lgmp line when they were compiled. I'm pretty sure it doesn't have to be the main Python interpreter, as Tkinter shows. BTW, this would compile without a hitch and not show up until I try to load the library, so you might look at the compile settings for mpzmodule. I haven't compiled Python again for a while, but we're definitely not seeing libgmp. -- System Information Debian Release: 1.2 Kernel Version: Linux A-abe 2.0.28 #11 Fri Feb 28 10:05:06 PST 1997 i586 unknown Versions of the packages python-mpz depends on: python-base Version: 1.4.0-4 gmp Version: 1.3.2-8 libc5 Version: 5.4.23-2