Closed Bug 652263 Opened 14 years ago Closed 13 years ago

[Firefox] Remove now useless WIN32_REDIST_DIR env var

Categories

(Release Engineering :: General, defect, P5)

x86
Windows Server 2003
defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: sgautherie, Unassigned)

References

Details

(Whiteboard: [superseded by bug 678161])

Examples: http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1303493909.1303502325.7070.gz&fulltext=1 WINNT 5.2 mozilla-central build on 2011/04/22 10:38:29 { WIN32_REDIST_DIR=d:/msvs8/VC/redist/x86/Microsoft.VC80.CRT } http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1303493910.1303500915.774.gz&fulltext=1 WINNT 5.2 mozilla-central leak test build on 2011/04/22 10:38:30 { WIN32_REDIST_DIR=d:/msvs8/VC/redist/x86/Microsoft.VC80.CRT } Bug 565774 comment 7: { Serge Gautherie (:sgautherie) 2011-02-16 05:42:38 PST Ben, could you tell us where the Firefox WIN32_REDIST_DIR setting comes from? (Afaics, not from build nor mozilla-central repositories...) } On debug builds, this has never been useful (and has been misused until bug 650699). On optimized builds, this is useless on all builds with jemalloc enabled, which is the case since mozilla-1.9.1 (Firefox 3.5), except for valgrind builds [I don't know much about these...]. http://mxr.mozilla.org/build/search?string=able-jemalloc&case=1
Priority: -- → P5
Whiteboard: [simple]
Bug 678161 (& Co) made WIN32_REDIST_DIR useful again.
Status: NEW → RESOLVED
Closed: 13 years ago
Depends on: 678161
Resolution: --- → INVALID
Whiteboard: [simple] → [superseded by bug 678161]
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.