Closed
Bug 679334
Opened 13 years ago
Closed 13 years ago
LINK : fatal error LNK1266: error reading instrumentation file 'firefox.pgd'; File not found
Categories
(Firefox Build System :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla9
People
(Reporter: armenzg, Assigned: glandium)
References
Details
(Whiteboard: fixed-in-bs)
Attachments
(2 files, 2 obsolete files)
1.34 KB,
patch
|
ted
:
review+
|
Details | Diff | Splinter Review |
1.05 KB,
patch
|
ted
:
review+
|
Details | Diff | Splinter Review |
I am hitting this compilation error on the Windows 64-bit builds and is keeping the builds red.
nsBrowserApp.obj
LINK : fatal error LNK1266: error reading instrumentation file 'firefox.pgd'; File not found
make[6]: Leaving directory `/e/builds/moz2_slave/m-cen-w64/build/obj-firefox/browser/app'
make[6]: *** [firefox.exe] Error 242
make[5]: Leaving directory `/e/builds/moz2_slave/m-cen-w64/build/obj-firefox/browser'
make[4]: Leaving directory `/e/builds/moz2_slave/m-cen-w64/build/obj-firefox'
make[5]: *** [libs] Error 2
make[4]: *** [libs_tier_app] Error 2
make[3]: Leaving directory `/e/builds/moz2_slave/m-cen-w64/build/obj-firefox'
make[3]: *** [tier_app] Error 2
make[2]: *** [default] Error 2
make[2]: Leaving directory `/e/builds/moz2_slave/m-cen-w64/build/obj-firefox'
make[1]: Leaving directory `/e/builds/moz2_slave/m-cen-w64/build'
make[1]: *** [realbuild] Error 2
make: *** [profiledbuild] Error 2
Probably related to Bug 669031 ...
Assignee | ||
Comment 2•13 years ago
|
||
It kind of partially looks like bug 678409, in that you somehow don't have profiling information, and the linker fails because of it, while it shouldn't.
Assignee | ||
Comment 3•13 years ago
|
||
(In reply to Kyle Huey [:khuey] (khuey@mozilla.com) from comment #1)
> Probably related to Bug 669031 ...
Not quite, in that the file missing from bug 669031 is pretty much expected not to be there. Firefox.pgd being missing is not. Except if PROFILE_GEN_SCRIPT does nothing.
Reporter | ||
Comment 4•13 years ago
|
||
I have also hit this in the last week:
"LINK : fatal error LNK1266: error reading instrumentation file 'plc4.pgd'; File not found"
If I disable PGO on win64 do you think it will make us complete the step?
Yes, because this step will never be run.
Assignee | ||
Comment 6•13 years ago
|
||
(In reply to Armen Zambrano G. [:armenzg] - Release Engineer from comment #4)
> I have also hit this in the last week:
> "LINK : fatal error LNK1266: error reading instrumentation file 'plc4.pgd';
> File not found"
>
> If I disable PGO on win64 do you think it will make us complete the step?
You can also clobber.
Assignee | ||
Comment 8•13 years ago
|
||
Attachment #553458 -
Flags: review?(ted.mielczarek)
Assignee | ||
Comment 9•13 years ago
|
||
Attachment #553461 -
Flags: review?(ted.mielczarek)
Comment 10•13 years ago
|
||
Comment on attachment 553458 [details] [diff] [review]
Don't remove pgd files, but clear them with pgomgr instead
Review of attachment 553458 [details] [diff] [review]:
-----------------------------------------------------------------
::: config/rules.mk
@@ +903,5 @@
> ifdef MOZ_PROFILE_GENERATE
> # Clean up profiling data during PROFILE_GENERATE phase
> export::
> ifeq ($(OS_ARCH)_$(GNU_CC), WINNT_)
> + -$(for pgd,$(wildcard *.pgd),pgomgr -clear $(pgd);)
ITYM $(foreach) here. Will this blow up if there are no pgd files present? (This will expand to just - then.)
Attachment #553458 -
Flags: review?(ted.mielczarek) → review+
Assignee | ||
Comment 11•13 years ago
|
||
Attachment #553464 -
Flags: review?(ted.mielczarek)
Assignee | ||
Updated•13 years ago
|
Attachment #553458 -
Attachment is obsolete: true
Assignee | ||
Comment 12•13 years ago
|
||
Attachment #553465 -
Flags: review?(ted.mielczarek)
Assignee | ||
Updated•13 years ago
|
Attachment #553461 -
Attachment is obsolete: true
Attachment #553461 -
Flags: review?(ted.mielczarek)
Updated•13 years ago
|
Attachment #553465 -
Flags: review?(ted.mielczarek) → review+
Updated•13 years ago
|
Attachment #553464 -
Flags: review?(ted.mielczarek) → review+
Reporter | ||
Comment 13•13 years ago
|
||
Clobbering did the job. Clobberer was not working on staging.
This is not a valid bug anymore but I see patches. Feel free to close it or whatever you feel is right.
Reporter | ||
Updated•13 years ago
|
No longer blocks: support-win64
Reporter | ||
Comment 14•13 years ago
|
||
I have hit this again in production.
I have marked every builder to clobber since they could have objdirs from when they were connected to staging.
Updated•13 years ago
|
Assignee: nobody → mh+mozilla
Comment 15•13 years ago
|
||
NSPR patch:
Checking in config/rules.mk;
/cvsroot/mozilla/nsprpub/config/rules.mk,v <-- rules.mk
new revision: 3.82; previous revision: 3.81
done
Assignee | ||
Comment 16•13 years ago
|
||
Whiteboard: fixed-in-bs [needs nspr update]
Assignee | ||
Comment 17•13 years ago
|
||
Whiteboard: fixed-in-bs [needs nspr update] → fixed-in-bs
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla9
Updated•7 years ago
|
Product: Core → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•