<div dir="ltr"><div>I think 'bitbake -e recipe', and then searching for SRC_URI in it should show which layer applies which patch.</div><div><br></div><div>Alex<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 12 Mar 2020 at 13:56, <<a href="mailto:rpjday@crashcourse.ca">rpjday@crashcourse.ca</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> just got from colleague a miniscule snippet of build output:<br>
<br>
ERROR: openssl-1.0.2u-r0 do_patch: Command Error: 'quilt --quiltrc ... <br>
snip ...<br>
Output: Patch Use-SHA256-not-MD5-as-default-digest.patch is already <br>
applied; check your series file<br>
<br>
the problem seems obvious ... more than one layer being pulled<br>
into the build is trying to apply the same patch to that version<br>
of openssl.<br>
<br>
i don't have access to that build system, but i'm not surprised<br>
as it appears that at least three layers (oe-core, vendor, and<br>
wind river linux fixes layer) all supply that very patch.<br>
<br>
what is the simplest command from way back in "morty" that<br>
could display something as clear as, "layer A already applied<br>
this patch, now layer B is trying to apply it as well?"<br>
<br>
if it's in the log file, i can just point the person at that,<br>
short of getting access to the build system and finding it<br>
myself. thank you kindly.<br>
<br>
rday<br>
<br>
<br>
-- <br>
_______________________________________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org" target="_blank">Openembedded-core@lists.openembedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core" rel="noreferrer" target="_blank">http://lists.openembedded.org/mailman/listinfo/openembedded-core</a><br>
</blockquote></div>