I used to compile r600g, like this for instance:
$ ./autogen.sh --with-gallium-drivers=r600 --with-dri-drivers= --enable-32-bit CFLAGS="-O2 -m32" CXXFLAGS="-O2 -m32" --libdir=/usr/lib
When I perform a "make clean", there is still .o some files:
$ find -name *.o
I delete them with:
$ find -name *.o -delete
but they should be deleted automatically by the make clean, no?
My guess is that make is being invoked on src/mesa/drivers/dri/common from a static Makefile in Gallium, which doesn't also have a clean rule.
When I build without any gallium drivers, I don't see this problem.
probably the same as my bug (even though I have more .o files left):
one should be marked as a duplicate (maybe mine, your title is more verbose)
Matt Turner: I leave it to you which one you would like to keep open
(In reply to comment #3)
> probably the same as my bug (even though I have more .o files left):
> one should be marked as a duplicate (maybe mine, your title is more verbose)
I'm not sure. In your report, there are lots of .o files left behind that were created by automake/libtool (as seen in the .libs/ folders). I've never seen or been able to reproduce that.
Should be fixed with the full transition to automake.
Please reopen the bug if you can still reproduce this.