[Python-Dev] extension module .o files wind up in the wrong place

[Michael Hudson]

Jack Jansen <Jack.Jansen@cwi.nl> writes:

> I am tempted to think that this problem has always existed, but has=20
> gone unnoticed until now.

It's definitely gotten worse recently.

> Now that I know about the problem it clears up some strange behaviour=20
> I've seen in the past.
> I would love to see this fixed, but I'm afraid I'm not the person to do=20=
> 
> it. Distutils
> never ceases to amaze me, and it's path-mangling tricks are beyond me.=20=
> 
> I'm pretty sure that
> if we somehow stuff "../Modules/regexmodule.c" (assuming we're building=20=
> 
> in a subdir of the main dir)
> into the list of module sources we'll get something like=20
> build/tmp.blabla/../Modules/regexmodule.o
> for the object filename.
> 
> Does anyone else feel up to fixing this?

I'll have a look, but so far I'm only confusing myself.

The first out-of-tree build I did today put one .o file in the wrong
place (bsddbmodule.o, I think).  Now all of them are ending up in the
wrong place.

Cheers,
M.

-- 
 Very clever implementation techniques are required to implement this
 insanity correctly and usefully, not to mention that code written
 with this feature used and abused east and west is exceptionally
 exciting to debug.       -- Erik Naggum on Algol-style "call-by-name"