[Python-bugs-list] [ python-Bugs-599248 ] ext module generation problem

noreply@sourceforge.net noreply@sourceforge.net
Wed, 13 Nov 2002 13:47:48 -0800


Bugs item #599248, was opened at 2002-08-23 10:01
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=599248&group_id=5470

Category: Distutils
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Stefan Seefeld (stefan)
Assigned to: A.M. Kuchling (akuchling)
Summary: ext module generation problem

Initial Comment:
when compiling an extension module, the source file
location
is not mirrored into the object file location, i.e.
subdirectories
are ignored (foo/bar/baz.c is compiled to baz.o, not
foo/bar/baz.o)

----------------------------------------------------------------------

>Comment By: A.M. Kuchling (akuchling)
Date: 2002-11-13 16:47

Message:
Logged In: YES 
user_id=11375

OK, then try the attached patch.  Does it fix the problem?



----------------------------------------------------------------------

Comment By: Stefan Seefeld (stefan)
Date: 2002-11-13 16:42

Message:
Logged In: YES 
user_id=764

yes, precisely !

----------------------------------------------------------------------

Comment By: A.M. Kuchling (akuchling)
Date: 2002-11-13 16:38

Message:
Logged In: YES 
user_id=11375

Hm.  Compiling my cryptography modules, it mirrors the location for the final source file (Crypto/Cipher/DES.so), but not for the intermediate 
.o file, which gets written to  build/temp.linux-i686-2.3/DES.o.  Is that 
the problem you're seeing?

(In any case, the temp. directory should use full paths, so this is a bug.)


----------------------------------------------------------------------

Comment By: Stefan Seefeld (stefan)
Date: 2002-11-06 10:21

Message:
Logged In: YES 
user_id=764

I experienced it with linux / gcc

----------------------------------------------------------------------

Comment By: A.M. Kuchling (akuchling)
Date: 2002-11-06 10:14

Message:
Logged In: YES 
user_id=11375

Hm, this is supposed to work, judging by the docstring of 
Compiler.compile().  Maybe some  subclass of Compiler gets it wrong; what platform are you on?


----------------------------------------------------------------------

Comment By: Stefan Seefeld (stefan)
Date: 2002-08-23 15:31

Message:
Logged In: YES 
user_id=764

precisely.

----------------------------------------------------------------------

Comment By: Fred L. Drake, Jr. (fdrake)
Date: 2002-08-23 15:26

Message:
Logged In: YES 
user_id=3066

Why is this a problem?  Are you running into name clashes?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=599248&group_id=5470