Bug 2312

Summary: Examine changes after repeated perl do_compile
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Paul Eggleton <bluelightning>
Component: devtools / tool chainAssignee: Nitin Kamble <nitin.a.kamble>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: Low CC: meta.mr.watcher, meta.watcher, sgw
Version: 1.2   
Target Milestone: 1.3   
Hardware: x86   
OS: Multiple   
Whiteboard: (P2)
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---
Attachments:
Description Flags
Diff of second perl do_compile execution none

Description Paul Eggleton 2012-04-17 14:10:31 UTC
If you run perl's do_compile a second time with -f, there are a number of changes that look like they possibly shouldn't be happening. Attached is a diff (generated using git on the WORKDIR) of the changes that are made by the second do_compile execution.
Comment 1 Paul Eggleton 2012-04-17 14:11:49 UTC
Created attachment 483 [details]
Diff of second perl do_compile execution
Comment 2 Nitin Kamble 2012-05-02 22:42:44 UTC
as perl is cross-unfriendly this task can be more involved than looks. 

I will also like to understand what is the motivation of this requirement?
Comment 3 Paul Eggleton 2012-05-02 22:52:30 UTC
The motivation is, I noticed that these changes do happen on re-execution of do_compile, and although they do not cause any immediate failures I want to know if any of them are going to cause any subtle problems. Surely that shouldn't be hard to determine?
Comment 4 Nitin Kamble 2012-05-18 19:36:56 UTC
I checked even with these differences in the source area, there is no change in the generated packages.