distclean misses generated Makefiles?

RESOLVED INVALID

Status

--
major
RESOLVED INVALID
10 years ago
8 months ago

People

(Reporter: brendan, Unassigned)

Tracking

Trunk

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

10 years ago
+++ This bug was initially created as a clone of Bug #454492 +++

I had to re-pull my m-c tree to cope with seemingly unfixable residue from srcdir build configuration, and after distclean in my old tree (mozilla-centra.bad), I found, among the diff -r output against the freshly-cloned new mozilla-central tree, the following:

Only in mozilla-central.bad/embedding/browser/chrome: Makefile
Only in mozilla-central.bad/extensions/pref/autoconfig/resources: Makefile
Only in mozilla-central.bad/js/src: Makefile.in~
Only in mozilla-central.bad/js/src: Makefile.ref~
Only in mozilla-central.bad/modules/plugin/default/mac: Makefile~
Only in mozilla-central.bad/modules/plugin/default/unix: Makefile~
Only in mozilla-central.bad/modules/plugin/sdk: Makefile
Only in mozilla-central.bad/modules/plugin/sdk/samples: Makefile
Only in mozilla-central.bad/modules/plugin/sdk/samples/basic/windows: Makefile
Only in mozilla-central.bad/modules/plugin/sdk/samples/common: Makefile
Only in mozilla-central.bad/modules/plugin/sdk/samples/winless/windows: Makefile
Only in mozilla-central.bad/netwerk/resources: Makefile
Only in mozilla-central.bad/security/manager/ssl/resources: Makefile
Only in mozilla-central.bad/xpfe/global: Makefile
Only in mozilla-central.bad/xpfe/global/resources: Makefile
Only in mozilla-central.bad/xpfe/global/resources/content: Makefile

Some or all of this may be stale due to repeated incremental pulls. Sorry if so but I thought it better to file a bug before I move on to using my new tree, and forget all about this.

/be

Comment 1

2 years ago
We no longer generate Makefile in the srcdir. So this should no longer happen.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INVALID

Updated

8 months ago
Product: Core → Firefox Build System
You need to log in before you can comment on or make changes to this bug.