Closed Bug 93491 Opened 24 years ago Closed 24 years ago

client.mk: libpr0n doesn't get reset to trunk by -PA

Categories

(SeaMonkey :: Build Config, defect, P4)

x86
All

Tracking

(Not tracked)

RESOLVED FIXED
mozilla0.9.4

People

(Reporter: jesup, Assigned: cls)

Details

Attachments

(1 file)

If you follow the direction on the mozilla.org CVS webpage to take a tarball and reset it to the trunk, you end up doing this: then run ``make -f mozilla/client.mk checkout MOZ_CO_FLAGS=-PA'' That resets Seamonkey to the trunk - but not other things, and in particular it doesn't reset modules/libpr0n. I chased this for 1 week on and off. To repeat: install 0.9.2 tarball. Use the two commands on the CVS web page to update it to the trunk. Try to build it. Fails in nsHTMLImageElement.cpp due to an interface change in libpr0n. If you force a -A checkout of libpr0n it works again. There may be other modules that aren't reset by that command; I see a number of -P's when I run the checkout command. We probably need a CO_FLAGS or GLOBAL_CO_FLAGS that gets applied to everything (or rewrite the webpage).
In the meantime, use 'make -f client.mk CVS_CO_DATE_FLAGS=-PA'
Priority: -- → P4
Target Milestone: --- → mozilla0.9.4
Accessibility and gfx2 seem to have the same problem
Hmm. Doesn't this have the side-effect of causing all modules to be pulled from MOZ_CO_TAG, if it's defined, even if you have NSPR_CO_TAG defined as well?
nevermind, i have obviously not had enough caffeine this morning. r=leaf
Patch checked in.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: