84195 - nmake /f client.mak clobber_all doesn't remove nsprpub\WIN32*.OBJ

Status: VERIFIED WONTFIX

(SeaMonkey :: Build Config, defect, P2)

Description

[Brian Ryner (not reading)]

If I do:

nmake /f client.mak clobber_all

it doesn't remove the WIN32_[D|O].OBJ directory under nsprpub, so nspr is not 
clobbered.

Comment 1

[Wan-Teh Chang]

Worse, if WIN32_[D|O].OBJ does not exist, it creates the
directory and run NSPR's configure in it. :-)

Comment 2

[Jon Granrose]

this should be a relatively simple fix, right?  low risk, moderate return.

Comment 3

[Daniel (Leaf) Nunes]

retargeting, i'll put up a patch soon.

Comment 4

[Ken]

can you create that patch for the 0.9.4 branch?

Comment 5

[Jon Granrose]

not blocking 0.9.5, moving to 0.9.6

Comment 6

[Daniel (Leaf) Nunes]

not holding release for this, moving to 0.9.7

Comment 7

[Jon Granrose]

push it out

Comment 8

[Brian 'netdragon' Bober]

I just had this problem today and it wasted 5 hours. Will this bug be "fixed"
when the build is moved to gmake?

Comment 9

[Ken]

pinging for progress...what's this about switching to gmake? when?

Comment 10

[hacker formerly known as [e-mail]]

This is a "feature" not a bug.  A clobber_all has never caused the need for a
reconfigure.  If we removed the WIN32_[O|D].obj dirs on a clobber_all, then we
would have to recreate the dirs and re-run configure after every clobber_all. 
Instead, we run clobber_all inside those dirs so NSPR is clobbered. If you want
those dirs removed, use distclean instead.

gmake builds are a different story as you will be responsible for creating your
own objdirs.

Comment 11

[Jon Granrose]

resolving wontfix now that we're on gmake builds.

Comment 12

[Brian 'netdragon' Bober]

V