Bug 2312 - Examine changes after repeated perl do_compile
Summary: Examine changes after repeated perl do_compile
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: devtools / tool chain (show other bugs)
Version: 1.2
Hardware: x86 Multiple
: Low enhancement
Target Milestone: 1.3
Assignee: Nitin Kamble
QA Contact:
URL:
Whiteboard: (P2)
Depends on:
Blocks:
 
Reported: 2012-04-17 14:10 UTC by Paul Eggleton
Modified: 2012-05-18 19:36 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

Attachments
Diff of second perl do_compile execution (101.49 KB, text/plain)
2012-04-17 14:11 UTC, Paul Eggleton 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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.