Re: SRCREV spec not working for kernel git recipes

Elvis Dowson


On Jun 23, 2012, at 11:57 AM, Elvis Dowson wrote:

Hi Khem,

On Jun 23, 2012, at 11:29 AM, Khem Raj wrote:

I found out that if I specify SRCREV_pn-${PN}, it works and picks up the correct commit id, as follows:

SRCREV_pn-${PN} = "a5556fb251253ccb674bd22d9703c37f6f8807a8"

However, if you simply specifying SRCREV = "a5556fb251253ccb674bd22d9703c37f6f8807a8", it has no effect and it always picks up the latest commit from the git repository.

It would be great if someone could please explain why this is so, because I search through the Yocto documentation and it isn't mentioned anywhere. The OE classic way of doing things, it used to pick up the correct commit by just specifying SRCREV. Now I find that you have to specify SRCREV_pn-${PN} to get it to work.

Is this documented somewhere?
can you port bitbake -e virtual/kernel output with and without change
somewhere ?

The output files are rather large.


BTW, I do not have a PROVIDES += "virtual/kernel" entry in the linux-xilinx kernel recipes. Is that necessary to get SRCREV to work?
Even adding a PROVIDES += "virtual/kernel" entry to the linux-xilinx recipe did not change the behavior. So for the moment, SRCREV doesn't seem to have any effect, but SRCREV_pn-${PN} works.

Best regards,

Elvis Dowson

Join to automatically receive all group messages.