Closed Bug 11360 Opened 25 years ago Closed 25 years ago

[PP]make realclean leaves some files behind.

Categories

(SeaMonkey :: Build Config, defect, P3)

Product:
SeaMonkey
Component:
Build Config
Platform:
x86
Linux
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED INVALID

People

(Reporter: slamm, Assigned: slamm)

Details

Comments from TenThumbs <tenthumbs@cybernex.net>:

This is not a big deal but these directories
  mozilla/widget/tests/scribble/.deps
  mozilla/widget/tests/widget/.deps
  mozilla/timer/src/unix/gtk/.deps
and their contents get left behind.
Tenthumbs, Running realclean from the top of the tree skips the "widget/tests"
directories. Do you mean the directories are left behind even if you run "make
realclean" in those directories? Would you expect realclean to clean those
directories even if it is not part of the normal build?

As for mozilla/timer/src/unix/gtk/.deps, that directory is removed when I run
gmake realclean. Is this a consitent problem for you? Can you remove the
directories by hand?
I only did realclean from the toplevel directory. Since none of the directories
was empty, I assume the build filled them. I certainly didn't. The last time I
clobbered, the directories reappeared.

Since I'm very paranoid, I have a script that runs around looking for anything
that might be a problem for a new build; then I just remove stuff by hand.
Ramiro changed widget/Makefile.in on 7/20 to not include the tests directory.
Maybe you built before that date, and updated before you cleaned. That would
explain why the directories were left behind. I am not sure about
timer/src/unix/gtk though. It could be related to the same change. Do you still
see this problem? If not, would you close the bug as invalid.
Summary: make realclean leaves some files behind. → [PP]make realclean leaves some files behind.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
I am closing this out as INVALID.
verified invalid
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.