Ah, I was just playing with a build of my own (which works so I can't
replicate the error), but if I "bitbake -e openssl", then I can obviously
see all the operations that go into constructing the SRC_URI, along with
the layers that contribute to that expansion, so I am assuming that,
even if more than one layer tries to apply the same patch, all those
SRC_URI values will be properly appended, in the sense of a duplicate
patch will occur twice in the final value of SRC_URI, yes?
And only when do_patch() kicks in will the duplicate patch generate a
patch error, correct? That seems pretty straightforward, as long as
I'm understanding the process here.
Thanks again.
rday
Quoting Alexander Kanavin <[email protected]>:
I think 'bitbake -e recipe', and then searching for SRC_URI in it should
show which layer applies which patch.
Alex
On Thu, 12 Mar 2020 at 13:56, <[email protected]> wrote:
just got from colleague a miniscule snippet of build output:
ERROR: openssl-1.0.2u-r0 do_patch: Command Error: 'quilt --quiltrc ...
snip ...
Output: Patch Use-SHA256-not-MD5-as-default-digest.patch is already
applied; check your series file
the problem seems obvious ... more than one layer being pulled
into the build is trying to apply the same patch to that version
of openssl.
i don't have access to that build system, but i'm not surprised
as it appears that at least three layers (oe-core, vendor, and
wind river linux fixes layer) all supply that very patch.
what is the simplest command from way back in "morty" that
could display something as clear as, "layer A already applied
this patch, now layer B is trying to apply it as well?"
if it's in the log file, i can just point the person at that,
short of getting access to the build system and finding it
myself. thank you kindly.
rday
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
