summaryrefslogtreecommitdiffstats
path: root/meta-skeleton/recipes-skeleton
diff options
context:
space:
mode:
authorAlexander Kanavin <alex.kanavin@gmail.com>2022-08-31 11:19:06 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2022-09-01 10:07:02 +0100
commit7b22dc70919464a5a2ca31926e37f9053a83e2a6 (patch)
tree6d347703586236060d8fcdc9dff338a5bca8e366 /meta-skeleton/recipes-skeleton
parentf7423a2f9f93320dbd1c4195997e6e797916852b (diff)
downloadpoky-7b22dc70919464a5a2ca31926e37f9053a83e2a6.tar.gz
perl: run builds from a pristine source tree
Running builds from a previously used directory relies on correctness of 'make clean' or incremental 'make', and sadly perl (or perl-cross) does not have either. The particularly nasty problem, currently occurring, is that sometimes, when reusing a previous build, we arrive at a combination of timestamps in the tree, where make becomes very confused, gets lost in its own rules and enters an infinite loop, never figuring out what needs to be rebuild in what order. Worse, there is no reliable trigger for this that was found, and any attempts to 'isolate the issue' haven't produced one. Let's simply add a clean S/B separation for builds, and always run a build from a reproducible set of files. [YOCTO #14902] (From OE-Core rev: 0919f5ec214594380eb5190b4878eadb30e3a471) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta-skeleton/recipes-skeleton')
0 files changed, 0 insertions, 0 deletions