[Python-bugs-list] [ python-Bugs-458343 ] distutils should zap .o as well as .so

[noreply@sourceforge.net]

Bugs item #458343, was opened at 2001-09-04 04:26
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=458343&group_id=5470

Category: Distutils
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Skip Montanaro (montanaro)
Assigned to: A.M. Kuchling (akuchling)
Summary: distutils should zap .o as well as .so

Initial Comment:
Just rebuilt from CVS and got this toward the end:

  skipping 'pyexpat' extension (up-to-date)
  WARNING: removing "pyexpat" since importing it failed

It would have been nice to know why the import failed.
Also, instead of just deleting the .so file it should
delete the .o file as well.  In this case, deleting the
.o file to force recompilation instead of just
relinking solved the problem.

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

>Comment By: Skip Montanaro (montanaro)
Date: 2001-09-04 13:20

Message:
Logged In: YES 
user_id=44345

> what did you use to clean up *.so files that didn't clean
> up *.o files?

The usual:

    cvs up .
    cd build
    ../configure
    make

Maybe this won't be a problem for people who routinely
download tarballs and build afresh, but when working from
CVS it doesn't seem to me like I should always need to "make
clean", presuming the make dependencies are done right.

The only thing I'm suggesting is that if distutils performs
an import to see if the newly built .so file is okay and
finds that it isn't, it should delete both the .so file and
the .o file from which it was built.  The message it emits
indicates that it is already zapping the .so file.

Skip



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

Comment By: A.M. Kuchling (akuchling)
Date: 2001-09-04 12:46

Message:
Logged In: YES 
user_id=11375

I'm not clear on the problem here; what did you use to 
clean up *.so files that didn't clean up *.o files?  "make 
clean" runs rm `find -name *.o`, and "python setup.py 
clean" blows away an entire directory under build/, so 
both of those seem to be correct.  What were you using?



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

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