Bug 15765 - tool paths in rpm macros incorrect
Summary: tool paths in rpm macros incorrect
Status: NEW
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: devtools / tool chain (show other bugs)
Version: 5.0.7
Hardware: x86 Multiple
: Medium normal
Target Milestone: 5.99
Assignee: Unassigned
QA Contact:
URL:
Whiteboard:
: 15766 (view as bug list)
Depends on:
Blocks:
 
Reported: 2025-02-19 05:51 UTC by Matevz Langus
Modified: 2025-02-20 15:59 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Matevz Langus 2025-02-19 05:51:14 UTC 
When building and installing SDK with:
  bitbake core-image-minimal -c populate_sdk -f
or
  bitbake core-image-minimal -c populate_sdk_ext -f

resulting tools, specifically file /opt/poky/5.0.7/sysroots/x86_64-pokysdk-linux/usr/lib/rpm/macros

will contain incorrect paths to tools for example:

  %__make			usr/bin/make


In previous Yocto versions (for sure in Kirkstone) this was:

  %__make			/usr/bin/make


which also does not seem right as this macro should point to Yocto's toolchain and utils. But with Kirkstone at least it worked as rpm/rpmbuild called OS'es make. With Scarthgap however it fails as it can not find make.

We believe this is a bug as we are so far unable to see how this could be a feature.

Shouldn't this macro point to either:
- just 'make'
- full path to Yocto's 'make' (when ext SDK is built?
Comment 1 Randy MacLeod 2025-02-20 15:31:49 UTC 
*** Bug 15766 has been marked as a duplicate of this bug. ***