Bug 11663 - Build QA RPATH warning in perl-native build (HiRes.so)
Summary: Build QA RPATH warning in perl-native build (HiRes.so)
Status: RESOLVED WORKSFORME
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 2.4
Hardware: All Multiple
: Medium normal
Target Milestone: 4.99
Assignee: Ross Burton
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-06-14 15:38 UTC by Khem Raj
Modified: 2019-06-07 22:06 UTC (History)
4 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 Khem Raj 2017-06-14 15:38:04 UTC 
This following warning appears all the time, on pyro as well as master.


WARNING: perl-native-5.24.1-r0 do_populate_sysroot: Skipping RPATH /usr/lib as is a standard search path for /mnt/a/oe/build/tmp/work/x86_64-linux/perl-native/5.24.1-r0/sysroot-destdir/mnt/a/oe/build/tmp/work/x86_64-linux/perl-native/5.24.1-r0/recipe-sysroot-native/usr/lib/perl-native/perl/5.24.1/auto/Time/HiRes/HiRes.so


Build Configuration:
BB_VERSION        = "1.34.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "arch"
TARGET_SYS        = "powerpc-bec-linux"
MACHINE           = "qemuppc"
DISTRO            = "bec"
DISTRO_VERSION    = "nodistro.0"
TUNE_FEATURES     = "m32 fpu-hard ppc7400 altivec"
TARGET_FPU        = ""
meta-bec          = "master:be744cc8a5c3e544fa6a6c5ca6cfcc0c1aed4dcb"
meta              = "kraj/master:28c86492bb0997a583a11ff1e30305fba405208b"
workspace         = "kraj/master:914614b6858b48a06638dc0a2bbb5d6c2312da9f"
Comment 1 Ross Burton 2017-06-15 14:56:13 UTC 
I bet this is because you're using arch...
Comment 2 Juan Manuel Cruz Alcaraz 2017-08-29 15:14:15 UTC 
Inherited from Anibal.
Comment 3 Richard Purdie 2019-06-07 22:06:31 UTC 
The autobuilder isn't seeing this issue and I suspect it was fixed in our WARNING purge for the new autobuilder (which highlights warnings).