Khem Raj 43b79d8e37 bcc: Skip the buildpaths HOME check for upstream example text ...

bcc's tools/funccount_example.txt documents tracing a binary that
upstream placed under /home/ubuntu:

  # ./funccount -p 1442 /home/ubuntu/contentions:*
  Tracing 15 functions for "/home/ubuntu/contentions:*"...
  If /home/ubuntu is in the $PATH, then the following command will also work:

That is documentation prose, not a leaked build path, but the buildpaths
QA check flags any packaged file containing the builder's HOME, so on a
host whose HOME is /home/ubuntu it warns twice - once for the copy in
${datadir}/bcc/tools/doc and once for the copy do_install_ptest places
in ${libdir}/tools:

  WARNING: bcc-0.37.0-r0 do_package_qa: QA Issue: File
  /usr/share/bcc/tools/doc/funccount_example.txt in package bcc contains
  a reference to the build host HOME directory. [buildpaths]
  WARNING: bcc-0.37.0-r0 do_package_qa: QA Issue: File
  /usr/lib/tools/funccount_example.txt in package bcc-ptest contains a
  reference to the build host HOME directory. [buildpaths]

Both packaged copies are byte identical to the file in the upstream tree
and contain no reference to TMPDIR, confirming nothing is baked in at
build time. Set OEQA_BUILDPATHS_SKIP as the QA message suggests, which
suppresses only the HOME half of the check; the TMPDIR half still guards
against real build path leaks. oe-core does the same for sudo, perl,
python3-numpy and python3-pytest.

Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>

2026-09-11 22:47:22 -07:00

..

bcc

bcc: Fix build with LLVM 23

2026-09-04 17:10:39 -07:00

bcc_0.37.0.bb

bcc: Skip the buildpaths HOME check for upstream example text

2026-09-11 22:47:22 -07:00