448871 - MsVC 2005 (v8.0) does not support /PDB:NONE

Status: RESOLVED DUPLICATE of bug 232600

(NSS :: Build, defect)

Description

[Serge Gautherie (:sgautherie)]

a.k.a.
|Bug 232600 – MSVC .NET 2003 (7.1) does not support /PDB:NONE| yet

***

[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1a2pre) Gecko/2008080216 Minefield/3.1a2pre] (home, optim) (W2Ksp4)

No bug.

[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1a2pre) Gecko/2008080217 Minefield/3.1a2pre] (home, debug) (W2Ksp4)

|hg status| reports
{{
? security\nss\cmd\shlibsign\NONE
? security\nss\cmd\shlibsign\mangle\NONE
? security\nss\lib\ckfw\builtins\NONE
? security\nss\lib\ckfw\capi\NONE
? security\nss\lib\freebl\NONE
? security\nss\lib\nss\NONE
? security\nss\lib\smime\NONE
? security\nss\lib\softoken\NONE
? security\nss\lib\softoken\legacydb\NONE
? security\nss\lib\ssl\NONE
? security\nss\lib\util\NONE
}}

Don't want to have pdb files named NONE.
Want these files to be in the "objdir/".

Comment 1

[Nelson Bolyard (seldom reads bugmail)]

This is not an NSS bug.  For building with versions of MSVC that do 
not support /PDB:NONE, you must define an environment variable 
MOZ_DEBUG_SYMBOLS=1

Evidently, the build you cited was built without that environment variable.

If yuo build with that environment variable defined, you will have no problem.
I do it every day.