Summary: | 'make clean' broken after switching to automake | ||
---|---|---|---|
Product: | Mesa | Reporter: | Tobias Droste <tdroste> |
Component: | Other | Assignee: | mesa-dev |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | ||
Version: | git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | List of .o files remaining after running 'make clean' |
Description
Tobias Droste
2012-06-24 11:04:50 UTC
This looks just like a problem caused by still having non-automake Makefiles. I'm not sure if this is realy true. Looking at the "problematic" .o files there is "src/mesa/drivers/dri/common/utils.o" metioned, which is completly handled by automake IIRC. I test this from time to time and it is still broken (same error) I can't even build with --enable-32-bit without adding -m32 to CFLAGS/CXXFLAGS manually. Yes... well I do this too (provide -m32 with CFLAGS). But this never worked and is well known (was mentioned at least a few times on the mesa-dev mailing list), that's why I did not mention it. You don't have to build a 32bit version to see that 'make clean' doesn't work. Just check if there are any *.o files left after running 'make clean'. They shouldn't be there. I tried looking at this, but automake is like black magic for me ;-) (In reply to comment #5) > You don't have to build a 32bit version to see that 'make clean' doesn't work. > Just check if there are any *.o files left after running 'make clean'. They > shouldn't be there. > > I tried looking at this, but automake is like black magic for me ;-) I don't see any *.o or *.lo files after make clean. Can you give me a list? Created attachment 65257 [details]
List of .o files remaining after running 'make clean'
Should be fixed with the full transition to automake. Please reopen the bug if you can still reproduce this. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.