3174 2012-09-26 10:27:49 +0000 QA warning building nativesdk-ncurses 2012-11-02 09:09:49 +0000 1 1 7 Build System, Metadata & Runtime OE-Core devtools / tool chain 1.3 x86 Multiple RESOLVED DUPLICATE 3325 in review Medium minor 1.3 1 bluelightning radu.moisan jessica.zhang meta.mr.watcher meta.watcher radu.moisan sgw --- --- --- oldest_to_newest 25766 0 bluelightning 2012-09-26 10:27:49 +0000 When building meta-toolchain I noticed we get the following QA warning: WARNING: QA Issue: nativesdk-ncurses: Files/directories were installed but not shipped /opt/poky/1.2+snapshot/sysroots/i686-pokysdk-linux/usr/bin/reset.ncurses /opt/poky/1.2+snapshot/sysroots/i686-pokysdk-linux/usr/bin/clear.ncurses I'm not sure if we also get these in the non-nativesdk case, but either way we ought to fix them. 25970 1 radu.moisan 2012-10-01 08:04:52 +0000 the check in package.bbclass seems legit, I'll look into ncurses. 26099 2 radu.moisan 2012-10-03 08:56:23 +0000 While processing nativesdk-ncurses the warning is thrown because FILE_nativesdk-ncurses-tools contains references to /opt/poky/1.2+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/clear /opt/poky/1.2+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/reset while in ${PKGD} I found /opt/poky/1.2+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/clear.ncurses /opt/poky/1.2+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/reset.ncurses At a first look the problem seems to be with FILE_nativesdk-ncurses-tools which should have the binaries appended with ".${BPN}" but for some reason they are not. 26101 3 radu.moisan 2012-10-03 09:30:16 +0000 Found the problem: ${PN} = nativesdk-ncurses so the evaluation of ${@['', '.${BPN\x7d'][d.getVar('PN', 1) == 'ncurses']} is the empty string which explains the missing append .${BPN} One quick fix, I guess, it could be to add INSANE_SKIP_nativesdk-${BPN}-tools = "installed_vs_shipped" 26103 4 radu.moisan 2012-10-03 09:41:13 +0000 Correction: INSANE_SKIP_nativesdk-${BPN} = "installed_vs_shipped" 27182 5 sgw 2012-11-02 09:09:49 +0000 Fixed by Robert via a different bug # *** This bug has been marked as a duplicate of bug 3325 ***