[Biopython-dev] Notification: incoming/115

[biopython-bugs at bioperl.org]

JitterBug notification

new message incoming/115

Message summary for PR#115
	From: Thomas Hamelryck <thamelry at vub.ac.be>
	Subject: Re: [Biopython-dev] Notification: incoming/114
	Date: Fri, 10 Jan 2003 22:54:09  0100
	0 replies 	0 followups

====> ORIGINAL MESSAGE FOLLOWS <====

>From thamelry at vub.ac.be Fri Jan 10 16:47:10 2003
Received: from riker.skynet.be (riker.skynet.be [195.238.3.89])
	by pw600a.bioperl.org (8.12.6/8.12.6) with ESMTP id h0ALl8SQ028546
	for <biopython-bugs at bioperl.org>; Fri, 10 Jan 2003 16:47:09 -0500
Received: from there (165.137-200-80.adsl.skynet.be [80.200.137.165])
	by riker.skynet.be (8.11.6/8.11.6/Skynet-OUT-2.20) with SMTP id h0ALlnI23093
	for <biopython-bugs at bioperl.org>; Fri, 10 Jan 2003 22:47:49 +0100 (MET)
	(envelope-from <thamelry at vub.ac.be>)
Message-Id: <200301102147.h0ALlnI23093 at riker.skynet.be>
Content-Type: text/plain;
  charset="iso-8859-1"
From: Thomas Hamelryck <thamelry at vub.ac.be>
Organization: Vrije Universiteit Brussel
To: biopython-bugs at bioperl.org
Subject: Re: [Biopython-dev] Notification: incoming/114
Date: Fri, 10 Jan 2003 22:54:09 +0100
X-Mailer: KMail [version 1.3.2]
References: <200301100050.h0A0oASQ019775 at pw600a.bioperl.org>
In-Reply-To: <200301100050.h0A0oASQ019775 at pw600a.bioperl.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-Spam-Status: No
X-Scanned-By: MIMEDefang 2.26 (www . roaringpenguin . com / mimedefang)


> Hi. I wanted to try out your KDTree module, but the file _KDTree.py tries
> to import _KDtreec (line 2).
>
> This is not in the Win distribution, nor does it show up when I build
> biopython from the CVS under Solaris.
>
> Am I missing something obvious?

I don't know about the Win distribution. Most likely the KDTree module simply 
wasn't included. Anyone?

Under Solaris, there is some kind of problem with building the module, most 
likely due to some bug in Distutils (as far as I could see it's a problem 
with the compilation flags during the creation of the shared library). So the 
module isn't built, and you get an import error. Unfortunately, I do not have 
access to Solaris, so I cannot look into it. 

Could you send me the compilation output? Mmmrrh, I suddenly realize that the
problem is quite likely that the C++ module is being compled with gcc and not 
g++.
 
gcc    assumes preprocessed (.i) files are C and assumes C style linking.
g++    assumes preprocessed (.i) files are C++ and assumes C++ style linking.

-Thomas 

---
Thomas Hamelryck      Vrije Universiteit Brussel (VUB)
Intitute for Molecular Biology           ULTR Department
Paardenstraat 65   1640 Sint-Gensius-Rode    Belgium
              http://ultr.vub.ac.be/~thomas