Customer was validating that RCPL 11 config/build still produces the same output as it did prior to upgrading to RCPL13. Found that it does not.
Reinstalling RCPL 11
I have two separate projects, but they share a common /opt/WindRiver7 directory that includes the installation of RCPL11 and RCPL13. Here is how to reproduce the problem: 1. Start with a /opt/WindRiver7 with only RCPL11 installed 2. Create a project with the vanilla script attached. It requires none of our layers and uses only the most basic options (NOTE the command- line option of the workspace number): mkdir -p /opt/workspace1/project cd /opt/workspace1/project ~/vanilla.sh 1 3. Build the kernel source code up to the kernel metadata task. This avoids any patching whatsoever: cd /opt/workspace1/project make linux-windriver kernel_metadata 4. Update/upgrade /opt/WindRiver7 to RCPL13. 5. Create a new project with the vanilla script attached and build the same recipe. Keeping in mind that it still says 'with-rcpl-version-0011". mkdir -p /opt/workspace2/project cd /opt/workspace2/project ~/vanilla.sh 2 make linux-windriver kernel_metadata Now, compare the kernel source code at /opt/workspace1/project/bitbake_build/tmp/work-shared/intel-x86-32/kernel-source and /opt/workspace2/project/bitbake_build/tmp/work-shared/intel-x86-32/kernel-source You will note that roughly 100 source files differ between the two. To maintain building old release sanity, these two should not differ in any way.
