Date   

Re: How to enable graphics acceleration on qemux86-64?

Manuel Wagesreither
 

`export DISPLAY=:0` did the trick.

The following shows when still on poky dunfell:

* I can now boot `runqmu kvm slirp sdl core-image-weston`. But gui is still slow. I cannot even type `systemctl poweroff` in weston-terminal, it inevitably becomes `wweesssttooo[...]`.
* `runqemu kvm slirp sdl gl core-image-weston` still fails with `Failed to run qemu: qemu-system-x86_64: OpenGL support is disabled`.

Updated to current poky master, but got this: `ERROR: ParseError in configuration INHERITs: Could not inherit file classes/image-mklibs.bbclass`.

Switched to hardknott-3.3.3 which is four weeks old and perhaps a little riper. It's currently building.

Regards,
Manuel


Re: [meta-security][PATCH] sssd: re-package to fix QA issues

Armin Kuster
 

changing the 'libsss_sudo' to 'libsss-sudo' fixes the errors.

I can do this locally or you can send a v2.

- armin

On 10/13/21 12:57 PM, Armin Kuster via lists.yoctoproject.org wrote:

On 10/13/21 1:49 AM, kai wrote:
From: Kai Kang <kai.kang@windriver.com>

It packages all file in ${libdir} to package sssd, including the .so
symlink files. Then it causes QA issues:

| ERROR: QA Issue: sssd rdepends on dbus-dev [dev-deps]
| ERROR: QA Issue: sssd rdepends on ding-libs-dev [dev-deps]

So re-package sssd then the .so symlink files and .pc files are packaged
to sssd-dev which should be.

File ${libdir}/libsss_sudo.so is not a symlink file but packaged to
sssd-dev too. Then causes another QA issue:

| ERROR: sssd-2.5.2-r0 do_package_qa: QA Issue:
-dev package sssd-dev contains non-symlink .so '/usr/lib/libsss_sudo.so' [dev-elf]
When building for ipk and deb I am seeing these errors.

IPK:
ERROR: sssd-2.5.2-r0 do_package_write_ipk: Fatal errors occurred in
subprocesses:
Command
'PATH="/home/akuster/oss/clean/poky/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/akuster/oss/clean/poky/scripts:/home/akuster/oss/clean/poky/build/tmp/work/core2-32-poky-linux/sssd/2.5.2-r0/recipe-sysroot-native/usr/bin/i686-poky-linux:/home/akuster/oss/clean/poky/build/tmp/work/core2-32-poky-linux/sssd/2.5.2-r0/recipe-sysroot/usr/bin/crossscripts:/home/akuster/oss/clean/poky/build/tmp/work/core2-32-poky-linux/sssd/2.5.2-r0/recipe-sysroot-native/usr/sbin:/home/akuster/oss/clean/poky/build/tmp/work/core2-32-poky-linux/sssd/2.5.2-r0/recipe-sysroot-native/usr/bin:/home/akuster/oss/clean/poky/build/tmp/work/core2-32-poky-linux/sssd/2.5.2-r0/recipe-sysroot-native/sbin:/home/akuster/oss/clean/poky/build/tmp/work/core2-32-poky-linux/sssd/2.5.2-r0/recipe-sysroot-native/bin:/home/akuster/oss/clean/poky/bitbake/bin:/home/akuster/oss/clean/poky/build/tmp/hosttools"
opkg-build -Z xz -a "--memlimit=50% --threads=16" libsss_sudo
/home/akuster/oss/clean/poky/build/tmp/work/core2-32-poky-linux/sssd/2.5.2-r0/deploy-ipks/core2-32'
returned non-zero exit status 1.
Subprocess output:libsss_sudo
*** Error: Package name libsss_sudo contains illegal characters, (other
than [a-z0-9.+-])

opkg-build: Please fix the above errors and try again.

ERROR: Logfile of failure stored in:
/home/akuster/oss/clean/poky/build/tmp/work/core2-32-poky-linux/sssd/2.5.2-r0/temp/log.do_package_write_ipk.2960686
ERROR: Task
(/home/akuster/oss/maint/meta-security/recipes-security/sssd/sssd_2.5.2.bb:do_package_write_ipk)
failed with exit code '1'

DEB:

ERROR: sssd-2.5.2-r0 do_package_write_deb: Fatal errors occurred in
subprocesses:
Command
'PATH="/home/akuster/oss/clean/poky/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/akuster/oss/clean/poky/scripts:/home/akuster/oss/clean/poky/build/tmp/work/core2-32-poky-linux/sssd/2.5.2-r0/recipe-sysroot-native/usr/bin/i686-poky-linux:/home/akuster/oss/clean/poky/build/tmp/work/core2-32-poky-linux/sssd/2.5.2-r0/recipe-sysroot/usr/bin/crossscripts:/home/akuster/oss/clean/poky/build/tmp/work/core2-32-poky-linux/sssd/2.5.2-r0/recipe-sysroot-native/usr/sbin:/home/akuster/oss/clean/poky/build/tmp/work/core2-32-poky-linux/sssd/2.5.2-r0/recipe-sysroot-native/usr/bin:/home/akuster/oss/clean/poky/build/tmp/work/core2-32-poky-linux/sssd/2.5.2-r0/recipe-sysroot-native/sbin:/home/akuster/oss/clean/poky/build/tmp/work/core2-32-poky-linux/sssd/2.5.2-r0/recipe-sysroot-native/bin:/home/akuster/oss/clean/poky/bitbake/bin:/home/akuster/oss/clean/poky/build/tmp/hosttools"
dpkg-deb -b
/home/akuster/oss/clean/poky/build/tmp/work/core2-32-poky-linux/sssd/2.5.2-r0/packages-split/libsss_sudo
/home/akuster/oss/clean/poky/build/tmp/work/core2-32-poky-linux/sssd/2.5.2-r0/deploy-debs/core2-32'
returned non-zero exit status 2.
Subprocess output:dpkg-deb: error: package name has characters that
aren't lowercase alphanums or '-+.'

ERROR: Logfile of failure stored in:
/home/akuster/oss/clean/poky/build/tmp/work/core2-32-poky-linux/sssd/2.5.2-r0/temp/log.do_package_write_deb.2973553
ERROR: Task
(/home/akuster/oss/maint/meta-security/recipes-security/sssd/sssd_2.5.2.bb:do_package_write_deb)
failed with exit code '1'



So create a new sub-package libsss_sudo to package file libsss_sudo.so
and make sssd rdepends on it.

Signed-off-by: Kai Kang <kai.kang@windriver.com>
---
recipes-security/sssd/sssd_2.5.2.bb | 16 +++++++++-------
1 file changed, 9 insertions(+), 7 deletions(-)

diff --git a/recipes-security/sssd/sssd_2.5.2.bb b/recipes-security/sssd/sssd_2.5.2.bb
index 76d6e03..da1a5c3 100644
--- a/recipes-security/sssd/sssd_2.5.2.bb
+++ b/recipes-security/sssd/sssd_2.5.2.bb
@@ -125,10 +125,12 @@ SYSTEMD_SERVICE:${PN} = " \
"
SYSTEMD_AUTO_ENABLE = "disable"

-FILES:${PN} += "${libdir} ${datadir} ${base_libdir}/security/pam_sss*.so"
-FILES:${PN}-dev = " ${includedir}/* ${libdir}/*la ${libdir}/*/*la"
-
-# The package contains symlinks that trip up insane
-INSANE_SKIP:${PN} = "dev-so"
-
-RDEPENDS:${PN} = "bind bind-utils dbus libldb libpam"
+PACKAGES =+ "libsss_sudo"
+FILES:${PN} += "${base_libdir}/security/pam_sss*.so \
+ ${datadir}/dbus-1/system-services/*.service \
+ ${libdir}/krb5/* \
+ ${libdir}/ldb/* \
+ "
+FILES:libsss_sudo = "${libdir}/libsss_sudo.so"
+
+RDEPENDS:${PN} = "bind bind-utils dbus libldb libpam libsss_sudo"




Re: [meta-security][PATCH] sssd: re-package to fix QA issues

Armin Kuster
 

On 10/13/21 1:49 AM, kai wrote:
From: Kai Kang <kai.kang@windriver.com>

It packages all file in ${libdir} to package sssd, including the .so
symlink files. Then it causes QA issues:

| ERROR: QA Issue: sssd rdepends on dbus-dev [dev-deps]
| ERROR: QA Issue: sssd rdepends on ding-libs-dev [dev-deps]

So re-package sssd then the .so symlink files and .pc files are packaged
to sssd-dev which should be.

File ${libdir}/libsss_sudo.so is not a symlink file but packaged to
sssd-dev too. Then causes another QA issue:

| ERROR: sssd-2.5.2-r0 do_package_qa: QA Issue:
-dev package sssd-dev contains non-symlink .so '/usr/lib/libsss_sudo.so' [dev-elf]
When building for ipk and deb I am seeing these errors.

IPK:
ERROR: sssd-2.5.2-r0 do_package_write_ipk: Fatal errors occurred in
subprocesses:
Command
'PATH="/home/akuster/oss/clean/poky/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/akuster/oss/clean/poky/scripts:/home/akuster/oss/clean/poky/build/tmp/work/core2-32-poky-linux/sssd/2.5.2-r0/recipe-sysroot-native/usr/bin/i686-poky-linux:/home/akuster/oss/clean/poky/build/tmp/work/core2-32-poky-linux/sssd/2.5.2-r0/recipe-sysroot/usr/bin/crossscripts:/home/akuster/oss/clean/poky/build/tmp/work/core2-32-poky-linux/sssd/2.5.2-r0/recipe-sysroot-native/usr/sbin:/home/akuster/oss/clean/poky/build/tmp/work/core2-32-poky-linux/sssd/2.5.2-r0/recipe-sysroot-native/usr/bin:/home/akuster/oss/clean/poky/build/tmp/work/core2-32-poky-linux/sssd/2.5.2-r0/recipe-sysroot-native/sbin:/home/akuster/oss/clean/poky/build/tmp/work/core2-32-poky-linux/sssd/2.5.2-r0/recipe-sysroot-native/bin:/home/akuster/oss/clean/poky/bitbake/bin:/home/akuster/oss/clean/poky/build/tmp/hosttools"
opkg-build -Z xz -a "--memlimit=50% --threads=16" libsss_sudo
/home/akuster/oss/clean/poky/build/tmp/work/core2-32-poky-linux/sssd/2.5.2-r0/deploy-ipks/core2-32'
returned non-zero exit status 1.
Subprocess output:libsss_sudo
*** Error: Package name libsss_sudo contains illegal characters, (other
than [a-z0-9.+-])

opkg-build: Please fix the above errors and try again.

ERROR: Logfile of failure stored in:
/home/akuster/oss/clean/poky/build/tmp/work/core2-32-poky-linux/sssd/2.5.2-r0/temp/log.do_package_write_ipk.2960686
ERROR: Task
(/home/akuster/oss/maint/meta-security/recipes-security/sssd/sssd_2.5.2.bb:do_package_write_ipk)
failed with exit code '1'

DEB:

ERROR: sssd-2.5.2-r0 do_package_write_deb: Fatal errors occurred in
subprocesses:
Command
'PATH="/home/akuster/oss/clean/poky/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/akuster/oss/clean/poky/scripts:/home/akuster/oss/clean/poky/build/tmp/work/core2-32-poky-linux/sssd/2.5.2-r0/recipe-sysroot-native/usr/bin/i686-poky-linux:/home/akuster/oss/clean/poky/build/tmp/work/core2-32-poky-linux/sssd/2.5.2-r0/recipe-sysroot/usr/bin/crossscripts:/home/akuster/oss/clean/poky/build/tmp/work/core2-32-poky-linux/sssd/2.5.2-r0/recipe-sysroot-native/usr/sbin:/home/akuster/oss/clean/poky/build/tmp/work/core2-32-poky-linux/sssd/2.5.2-r0/recipe-sysroot-native/usr/bin:/home/akuster/oss/clean/poky/build/tmp/work/core2-32-poky-linux/sssd/2.5.2-r0/recipe-sysroot-native/sbin:/home/akuster/oss/clean/poky/build/tmp/work/core2-32-poky-linux/sssd/2.5.2-r0/recipe-sysroot-native/bin:/home/akuster/oss/clean/poky/bitbake/bin:/home/akuster/oss/clean/poky/build/tmp/hosttools"
dpkg-deb -b
/home/akuster/oss/clean/poky/build/tmp/work/core2-32-poky-linux/sssd/2.5.2-r0/packages-split/libsss_sudo
/home/akuster/oss/clean/poky/build/tmp/work/core2-32-poky-linux/sssd/2.5.2-r0/deploy-debs/core2-32'
returned non-zero exit status 2.
Subprocess output:dpkg-deb: error: package name has characters that
aren't lowercase alphanums or '-+.'

ERROR: Logfile of failure stored in:
/home/akuster/oss/clean/poky/build/tmp/work/core2-32-poky-linux/sssd/2.5.2-r0/temp/log.do_package_write_deb.2973553
ERROR: Task
(/home/akuster/oss/maint/meta-security/recipes-security/sssd/sssd_2.5.2.bb:do_package_write_deb)
failed with exit code '1'




So create a new sub-package libsss_sudo to package file libsss_sudo.so
and make sssd rdepends on it.

Signed-off-by: Kai Kang <kai.kang@windriver.com>
---
recipes-security/sssd/sssd_2.5.2.bb | 16 +++++++++-------
1 file changed, 9 insertions(+), 7 deletions(-)

diff --git a/recipes-security/sssd/sssd_2.5.2.bb b/recipes-security/sssd/sssd_2.5.2.bb
index 76d6e03..da1a5c3 100644
--- a/recipes-security/sssd/sssd_2.5.2.bb
+++ b/recipes-security/sssd/sssd_2.5.2.bb
@@ -125,10 +125,12 @@ SYSTEMD_SERVICE:${PN} = " \
"
SYSTEMD_AUTO_ENABLE = "disable"

-FILES:${PN} += "${libdir} ${datadir} ${base_libdir}/security/pam_sss*.so"
-FILES:${PN}-dev = " ${includedir}/* ${libdir}/*la ${libdir}/*/*la"
-
-# The package contains symlinks that trip up insane
-INSANE_SKIP:${PN} = "dev-so"
-
-RDEPENDS:${PN} = "bind bind-utils dbus libldb libpam"
+PACKAGES =+ "libsss_sudo"
+FILES:${PN} += "${base_libdir}/security/pam_sss*.so \
+ ${datadir}/dbus-1/system-services/*.service \
+ ${libdir}/krb5/* \
+ ${libdir}/ldb/* \
+ "
+FILES:libsss_sudo = "${libdir}/libsss_sudo.so"
+
+RDEPENDS:${PN} = "bind bind-utils dbus libldb libpam libsss_sudo"



Re: How to enable graphics acceleration on qemux86-64?

Alexander Kanavin
 

Can you check with current master (instead of dunfell) please?

You also need to run runqemu inside an X session (e.g. DISPLAY environment variable should be set to a valid X server).

If sdl does not work, enabling gtk is not going to work either.

Alex


On Wed, 13 Oct 2021 at 21:21, Manuel Wagesreither <ManWag@...> wrote:
Hi Alex,

Am Fr, 8. Okt 2021, um 11:00, schrieb Alexander Kanavin:
Something in your custom setup disables opengl in qemu-system-native.

Can you try core-image-weston with plain poky only?

This is the test we use to ensure it does work, it lists all the settings that have to be in place
(but in poky they are enabled by default, except the gtk frontend):

Interesting. Things don't work on both my Debian Buster machines.

How does opengl get set in qemu-system-native? Am Yocto novice and don't speak Python.

Am using poky repo on tag dunfell-23.0.10 = 2a848e9507.

Here's my complete test results:

* `runqemu kvm slirp core-image-weston` fails with `Failed to run qemu: Could not initialize SDL(x11 not available) - exiting`
* `runqemu kvm slirp sdl core-image-minimal` fails with `Failed to run qemu: Could not initialize SDL(x11 not available) - exiting`
* `runqemu kvm slirp sdl gl core-image-minimal` fails with `Failed to run qemu: qemu-system-x86_64: OpenGL support is disabled`
* `runqemu kvm slirp gtk core-image-minimal` fails with `Failed to run qemu: qemu-system-x86_64: Display 'gtk' is not available.`

How would I enable gtk frontend in poky?

Thanks, Manuel


Re: How to enable graphics acceleration on qemux86-64?

Manuel Wagesreither
 

Hi Alex,

Am Fr, 8. Okt 2021, um 11:00, schrieb Alexander Kanavin:
Something in your custom setup disables opengl in qemu-system-native.

Can you try core-image-weston with plain poky only?

This is the test we use to ensure it does work, it lists all the settings that have to be in place
(but in poky they are enabled by default, except the gtk frontend):

Interesting. Things don't work on both my Debian Buster machines.

How does opengl get set in qemu-system-native? Am Yocto novice and don't speak Python.

Am using poky repo on tag dunfell-23.0.10 = 2a848e9507.

Here's my complete test results:

* `runqemu kvm slirp core-image-weston` fails with `Failed to run qemu: Could not initialize SDL(x11 not available) - exiting`
* `runqemu kvm slirp sdl core-image-minimal` fails with `Failed to run qemu: Could not initialize SDL(x11 not available) - exiting`
* `runqemu kvm slirp sdl gl core-image-minimal` fails with `Failed to run qemu: qemu-system-x86_64: OpenGL support is disabled`
* `runqemu kvm slirp gtk core-image-minimal` fails with `Failed to run qemu: qemu-system-x86_64: Display 'gtk' is not available.`

How would I enable gtk frontend in poky?

Thanks, Manuel


Re: [ANNOUNCEMENT] Yocto Project 3.3.3 (hardknott-25.0.3) is Released --> When is hardknott's final release: 3.3.4 ?

Randy MacLeod
 

Sending to Stephen's gmail address.

On 2021-10-13 12:52 p.m., Randy MacLeod wrote:
When will we be doing hardknott's final release: 3.3.4 ?
Is this info documented in the wiki:
I don't see it in either of these links:
https://wiki.yoctoproject.org/wiki/Releases
https://wiki.yoctoproject.org/wiki/Special:RecentChanges
../Randy
--
# Randy MacLeod
# Wind River Linux


Re: #zeus meta-intel #zeus

Monsees, Steven C (US)
 

Anything ?, I have yet to resolve this.

-----Original Message-----
From: Monsees, Steven C (US)
Sent: Wednesday, October 13, 2021 9:03 AM
To: 'Mittal, Anuj' <anuj.mittal@intel.com>; 'yocto@lists.yoctoproject.org' <yocto@lists.yoctoproject.org>
Subject: RE: [yocto] #zeus meta-intel


Are there any patches required for these components (igc, opencl-clang, and intel-compute-runtime) ?

-----Original Message-----
From: Monsees, Steven C (US)
Sent: Wednesday, October 13, 2021 7:13 AM
To: 'Mittal, Anuj' <anuj.mittal@intel.com>; yocto@lists.yoctoproject.org
Subject: RE: [yocto] #zeus meta-intel


Anuj:

I rebuilt the entire image (but did not delete the state_cache)...
I am building meta-clang (zeus based, I believe it is 9.0.1).

Steve

-----Original Message-----
From: Mittal, Anuj <anuj.mittal@intel.com>
Sent: Tuesday, October 12, 2021 10:10 PM
To: Monsees, Steven C (US) <steven.monsees@baesystems.com>; yocto@lists.yoctoproject.org
Subject: Re: [yocto] #zeus meta-intel

External Email Alert

This email has been sent from an account outside of the BAE Systems network.

Please treat the email with caution, especially if you are requested to click on a link, decrypt/open an attachment, or enable macros. For further information on how to spot phishing, access “Cybersecurity OneSpace Page” and report phishing by clicking the button “Report Phishing” on the Outlook toolbar.


Did you build everything with this compiler from start? Is opencl-clang building with the right LLVM lib from meta-clang?

Thanks,

Anuj

On Tue, 2021-10-12 at 17:15 +0000, Monsees, Steven C (US) wrote:

Anuj:

I picked up the tarball for for the baseline dunfell tools platform to
update host tools...

I am seeing it compile cleaner but for one issue causng ld to fail:

/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1331:
undefined reference to `vtable for
llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > >'

Isn't LLVM brought in along with clang under meta-clang ?

Is there a missing build dependency ?

Thanks,
Steve

Build excerpt showing multiple " undefined reference to `vtable "
errors...

/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function
`llvm::cl::opt<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > >::~opt()':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1331:
undefined reference to `vtable for
llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > >'
/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function
`llvm::cl::OptionValue<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >::OptionValue()':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:601:
undefined reference to `vtable for
llvm::cl::OptionValue<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >'
/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function
`llvm::cl::opt<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >
::opt<llvm::cl::FormattingFlags, llvm::cl::desc,
llvm::cl::initializer<char [2]> >(llvm::cl::FormattingFlags const&,
llvm::cl::desc const&, llvm::cl::initializer<char [2]> const&)':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1407:
undefined reference to `vtable for
llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > >'
/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function
`llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> >
::parser(llvm::cl::Option&)':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1072:
undefined reference to `vtable for
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >'
/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function
`llvm::cl::opt<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > >::~opt()':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1331:
undefined reference to `vtable for
llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > >'
/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function
`llvm::cl::OptionValue<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >::OptionValue()':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:601:
undefined reference to `vtable for
llvm::cl::OptionValue<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >'
/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function
`llvm::cl::opt<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > >::opt<char [9],
llvm::cl::desc>(char const (&) [9], llvm::cl::desc const&)':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1407:
undefined reference to `vtable for
llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > >'
/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function
`llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> >
::parser(llvm::cl::Option&)':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1072:
undefined reference to `vtable for
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >'
collect2: error: ld returned 1 exit status

-----Original Message-----
From: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org> On
Behalf Of Anuj Mittal
Sent: Tuesday, October 12, 2021 10:43 AM
To: Monsees, Steven C (US) <steven.monsees@baesystems.com>;
yocto@lists.yoctoproject.org
Subject: Re: [yocto] #zeus meta-intel

External Email Alert

This email has been sent from an account outside of the BAE Systems
network.

Please treat the email with caution, especially if you are requested
to click on a link, decrypt/open an attachment, or enable macros.  For
further information on how to spot phishing, access “Cybersecurity
OneSpace Page” and report phishing by clicking the button “Report
Phishing” on the Outlook toolbar.


On Tue, 2021-10-12 at 12:43 +0000, Monsees, Steven C (US) wrote:
g++: error: unrecognized command line option ‘-std=c++14’
It looks like the gcc version is too old on your host for this to work.

Thanks,

Anuj


Re: [ANNOUNCEMENT] Yocto Project 3.3.3 (hardknott-25.0.3) is Released --> When is hardknott's final release: 3.3.4 ?

Randy MacLeod
 

When will we be doing hardknott's final release: 3.3.4 ?

Is this info documented in the wiki:

I don't see it in either of these links:

https://wiki.yoctoproject.org/wiki/Releases
https://wiki.yoctoproject.org/wiki/Special:RecentChanges

../Randy


[PATCH yocto-autobuilder-helper] scripts/collect-results: publish everything in tmp/log/oeqa/

Alexander Kanavin
 

From: Alexander Kanavin <alex@linutronix.de>

In addition to the testresult json, testimage class now also
provides the testimage task log and qemu console output log
which can be useful for debugging test failures or
even checking qemu test runs when failures did not happen.

Rather than duplicate specific file/folder names, let's copy all
that is available, and define what is published in the testimage
class itself (with appropriate folder structure if/when needed).
At the moment there's just three files, and they are copied into
folders named after image names, so there's no clutter or risk
of mixing them up with unrelated logs.

[YOCTO #14518]

Signed-off-by: Alexander Kanavin <alex@linutronix.de>
---
scripts/collect-results | 8 +++-----
1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/scripts/collect-results b/scripts/collect-results
index 93834d6..3663330 100755
--- a/scripts/collect-results
+++ b/scripts/collect-results
@@ -3,11 +3,9 @@ WORKDIR=$1
DEST=$2
target=$3

-RESFILE=$WORKDIR/tmp/log/oeqa/testresults.json
-
-if [ -e $RESFILE ]; then
- mkdir -p $DEST/$target
- cp $WORKDIR/tmp/log/oeqa/testresults.json $DEST/$target/
+mkdir -p $DEST
+if [ -e $WORKDIR/tmp/log/oeqa/ ]; then
+ cp -rf $WORKDIR/tmp/log/oeqa/ $DEST/$target
fi

if [ -e $WORKDIR/buildhistory ]; then
--
2.31.1


Re: #zeus meta-intel #zeus

Monsees, Steven C (US)
 

Are there any patches required for these components (igc, opencl-clang, and intel-compute-runtime) ?

-----Original Message-----
From: Monsees, Steven C (US)
Sent: Wednesday, October 13, 2021 7:13 AM
To: 'Mittal, Anuj' <anuj.mittal@intel.com>; yocto@lists.yoctoproject.org
Subject: RE: [yocto] #zeus meta-intel


Anuj:

I rebuilt the entire image (but did not delete the state_cache)...
I am building meta-clang (zeus based, I believe it is 9.0.1).

Steve

-----Original Message-----
From: Mittal, Anuj <anuj.mittal@intel.com>
Sent: Tuesday, October 12, 2021 10:10 PM
To: Monsees, Steven C (US) <steven.monsees@baesystems.com>; yocto@lists.yoctoproject.org
Subject: Re: [yocto] #zeus meta-intel

External Email Alert

This email has been sent from an account outside of the BAE Systems network.

Please treat the email with caution, especially if you are requested to click on a link, decrypt/open an attachment, or enable macros. For further information on how to spot phishing, access “Cybersecurity OneSpace Page” and report phishing by clicking the button “Report Phishing” on the Outlook toolbar.


Did you build everything with this compiler from start? Is opencl-clang building with the right LLVM lib from meta-clang?

Thanks,

Anuj

On Tue, 2021-10-12 at 17:15 +0000, Monsees, Steven C (US) wrote:

Anuj:

I picked up the tarball for for the baseline dunfell tools platform to
update host tools...

I am seeing it compile cleaner but for one issue causng ld to fail:

/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1331:
undefined reference to `vtable for
llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > >'

Isn't LLVM brought in along with clang under meta-clang ?

Is there a missing build dependency ?

Thanks,
Steve

Build excerpt showing multiple " undefined reference to `vtable "
errors...

/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function
`llvm::cl::opt<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > >::~opt()':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1331:
undefined reference to `vtable for
llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > >'
/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function
`llvm::cl::OptionValue<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >::OptionValue()':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:601:
undefined reference to `vtable for
llvm::cl::OptionValue<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >'
/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function
`llvm::cl::opt<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >
::opt<llvm::cl::FormattingFlags, llvm::cl::desc,
llvm::cl::initializer<char [2]> >(llvm::cl::FormattingFlags const&,
llvm::cl::desc const&, llvm::cl::initializer<char [2]> const&)':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1407:
undefined reference to `vtable for
llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > >'
/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function
`llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> >
::parser(llvm::cl::Option&)':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1072:
undefined reference to `vtable for
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >'
/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function
`llvm::cl::opt<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > >::~opt()':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1331:
undefined reference to `vtable for
llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > >'
/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function
`llvm::cl::OptionValue<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >::OptionValue()':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:601:
undefined reference to `vtable for
llvm::cl::OptionValue<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >'
/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function
`llvm::cl::opt<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > >::opt<char [9],
llvm::cl::desc>(char const (&) [9], llvm::cl::desc const&)':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1407:
undefined reference to `vtable for
llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > >'
/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function
`llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> >
::parser(llvm::cl::Option&)':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1072:
undefined reference to `vtable for
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >'
collect2: error: ld returned 1 exit status

-----Original Message-----
From: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org> On
Behalf Of Anuj Mittal
Sent: Tuesday, October 12, 2021 10:43 AM
To: Monsees, Steven C (US) <steven.monsees@baesystems.com>;
yocto@lists.yoctoproject.org
Subject: Re: [yocto] #zeus meta-intel

External Email Alert

This email has been sent from an account outside of the BAE Systems
network.

Please treat the email with caution, especially if you are requested
to click on a link, decrypt/open an attachment, or enable macros.  For
further information on how to spot phishing, access “Cybersecurity
OneSpace Page” and report phishing by clicking the button “Report
Phishing” on the Outlook toolbar.


On Tue, 2021-10-12 at 12:43 +0000, Monsees, Steven C (US) wrote:
g++: error: unrecognized command line option ‘-std=c++14’
It looks like the gcc version is too old on your host for this to work.

Thanks,

Anuj


Re: #zeus meta-intel #zeus

Monsees, Steven C (US)
 

Anuj:

I rebuilt the entire image (but did not delete the state_cache)...
I am building meta-clang (zeus based, I believe it is 9.0.1).

Steve

-----Original Message-----
From: Mittal, Anuj <anuj.mittal@intel.com>
Sent: Tuesday, October 12, 2021 10:10 PM
To: Monsees, Steven C (US) <steven.monsees@baesystems.com>; yocto@lists.yoctoproject.org
Subject: Re: [yocto] #zeus meta-intel

External Email Alert

This email has been sent from an account outside of the BAE Systems network.

Please treat the email with caution, especially if you are requested to click on a link, decrypt/open an attachment, or enable macros. For further information on how to spot phishing, access “Cybersecurity OneSpace Page” and report phishing by clicking the button “Report Phishing” on the Outlook toolbar.


Did you build everything with this compiler from start? Is opencl-clang building with the right LLVM lib from meta-clang?

Thanks,

Anuj

On Tue, 2021-10-12 at 17:15 +0000, Monsees, Steven C (US) wrote:

Anuj:

I picked up the tarball for for the baseline dunfell tools platform to
update host tools...

I am seeing it compile cleaner but for one issue causng ld to fail:

/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1331:
undefined reference to `vtable for
llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > >'

Isn't LLVM brought in along with clang under meta-clang ?

Is there a missing build dependency ?

Thanks,
Steve

Build excerpt showing multiple " undefined reference to `vtable "
errors...

/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function
`llvm::cl::opt<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > >::~opt()':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1331:
undefined reference to `vtable for
llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > >'
/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function
`llvm::cl::OptionValue<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >::OptionValue()':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:601:
undefined reference to `vtable for
llvm::cl::OptionValue<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >'
/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function
`llvm::cl::opt<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >
::opt<llvm::cl::FormattingFlags, llvm::cl::desc,
llvm::cl::initializer<char [2]> >(llvm::cl::FormattingFlags const&,
llvm::cl::desc const&, llvm::cl::initializer<char [2]> const&)':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1407:
undefined reference to `vtable for
llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > >'
/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function
`llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> >
::parser(llvm::cl::Option&)':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1072:
undefined reference to `vtable for
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >'
/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function
`llvm::cl::opt<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > >::~opt()':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1331:
undefined reference to `vtable for
llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > >'
/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function
`llvm::cl::OptionValue<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >::OptionValue()':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:601:
undefined reference to `vtable for
llvm::cl::OptionValue<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >'
/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function
`llvm::cl::opt<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > >::opt<char [9],
llvm::cl::desc>(char const (&) [9], llvm::cl::desc const&)':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1407:
undefined reference to `vtable for
llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > >'
/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function
`llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> >
::parser(llvm::cl::Option&)':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1072:
undefined reference to `vtable for
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >'
collect2: error: ld returned 1 exit status

-----Original Message-----
From: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org> On
Behalf Of Anuj Mittal
Sent: Tuesday, October 12, 2021 10:43 AM
To: Monsees, Steven C (US) <steven.monsees@baesystems.com>;
yocto@lists.yoctoproject.org
Subject: Re: [yocto] #zeus meta-intel

External Email Alert

This email has been sent from an account outside of the BAE Systems
network.

Please treat the email with caution, especially if you are requested
to click on a link, decrypt/open an attachment, or enable macros.  For
further information on how to spot phishing, access “Cybersecurity
OneSpace Page” and report phishing by clicking the button “Report
Phishing” on the Outlook toolbar.


On Tue, 2021-10-12 at 12:43 +0000, Monsees, Steven C (US) wrote:
g++: error: unrecognized command line option ‘-std=c++14’
It looks like the gcc version is too old on your host for this to work.

Thanks,

Anuj


[meta-security][PATCH] sssd: re-package to fix QA issues

kai
 

From: Kai Kang <kai.kang@windriver.com>

It packages all file in ${libdir} to package sssd, including the .so
symlink files. Then it causes QA issues:

| ERROR: QA Issue: sssd rdepends on dbus-dev [dev-deps]
| ERROR: QA Issue: sssd rdepends on ding-libs-dev [dev-deps]

So re-package sssd then the .so symlink files and .pc files are packaged
to sssd-dev which should be.

File ${libdir}/libsss_sudo.so is not a symlink file but packaged to
sssd-dev too. Then causes another QA issue:

| ERROR: sssd-2.5.2-r0 do_package_qa: QA Issue:
-dev package sssd-dev contains non-symlink .so '/usr/lib/libsss_sudo.so' [dev-elf]

So create a new sub-package libsss_sudo to package file libsss_sudo.so
and make sssd rdepends on it.

Signed-off-by: Kai Kang <kai.kang@windriver.com>
---
recipes-security/sssd/sssd_2.5.2.bb | 16 +++++++++-------
1 file changed, 9 insertions(+), 7 deletions(-)

diff --git a/recipes-security/sssd/sssd_2.5.2.bb b/recipes-security/sssd/sssd_2.5.2.bb
index 76d6e03..da1a5c3 100644
--- a/recipes-security/sssd/sssd_2.5.2.bb
+++ b/recipes-security/sssd/sssd_2.5.2.bb
@@ -125,10 +125,12 @@ SYSTEMD_SERVICE:${PN} = " \
"
SYSTEMD_AUTO_ENABLE = "disable"

-FILES:${PN} += "${libdir} ${datadir} ${base_libdir}/security/pam_sss*.so"
-FILES:${PN}-dev = " ${includedir}/* ${libdir}/*la ${libdir}/*/*la"
-
-# The package contains symlinks that trip up insane
-INSANE_SKIP:${PN} = "dev-so"
-
-RDEPENDS:${PN} = "bind bind-utils dbus libldb libpam"
+PACKAGES =+ "libsss_sudo"
+FILES:${PN} += "${base_libdir}/security/pam_sss*.so \
+ ${datadir}/dbus-1/system-services/*.service \
+ ${libdir}/krb5/* \
+ ${libdir}/ldb/* \
+ "
+FILES:libsss_sudo = "${libdir}/libsss_sudo.so"
+
+RDEPENDS:${PN} = "bind bind-utils dbus libldb libpam libsss_sudo"
--
2.17.1


Re: Node-red and Wifi

Josef Holzmayr
 

Brutally honest:

Yes it can. No you won't be able to do it without reading the docs.

<donald@...> schrieb am Mi., 13. Okt. 2021, 08:51:

I am looking at various distributions to move to from my existing one - without wanting to wade through another lots of documentation - can the Yocto buid
1) be configured to act as a WiFi access point - with natting
2) run node-red

I will be running on an Armbian quadcore.



Node-red and Wifi

donald@...
 

I am looking at various distributions to move to from my existing one - without wanting to wade through another lots of documentation - can the Yocto buid
1) be configured to act as a WiFi access point - with natting
2) run node-red

I will be running on an Armbian quadcore.


Re: [qa-build-notification] QA notification for completed autobuilder build (yocto-3.4.rc1)

Teoh, Jay Shen
 

Hi all,

Intel and WR YP QA is planning for QA execution for YP build yocto-3.4.rc1. We are planning to execute following tests for this cycle:

OEQA-manual tests for following module:
1. OE-Core
2. BSP-hw

Runtime auto test for following platforms:
1. MinnowTurbot 32-bit
2. Coffee Lake
3. NUC 7
4. NUC 6
5. Edgerouter
6. Beaglebone

ETA for completion is next Monday, Oct 18.

Thanks,
Jay

-----Original Message-----
From: qa-build-notification@lists.yoctoproject.org <qa-build-
notification@lists.yoctoproject.org> On Behalf Of Richard Purdie
Sent: Tuesday, 12 October, 2021 1:25 AM
To: yocto@lists.yoctoproject.org
Cc: qa-build-notification <qa-build-notification@lists.yoctoproject.org>
Subject: [qa-build-notification] QA notification for completed autobuilder build
(yocto-3.4.rc1)

A build flagged for QA (yocto-3.4.rc1) was completed on the autobuilder and is
available at:


https://autobuilder.yocto.io/pub/releases/yocto-3.4.rc1


Build hash information:

bitbake: c78ebac71ec976fdf27ea24767057882870f5c60
meta-agl: 228ecc1dec390138c44299d1c244acda9ad75ce1
meta-arm: 98193f3b6167e07cbb794e96b80d78ca1779ea4f
meta-aws: 27bca81c4d3f0138fda583f9ea98df6152332333
meta-gplv2: f04e4369bf9dd3385165281b9fa2ed1043b0e400
meta-intel: 90170cf85fe35b4e8dc00eee50053c0205276b63
meta-mingw: f5d761cbd5c957e4405c5d40b0c236d263c916a8
meta-openembedded: f2152d79043601eacb70da1a3ab36f5ac56f3e28
oecore: bb1dea6806f084364b6017db2567f438e805aef0
poky: f6d1126fff213460dc6954a5d5fc168606d76b66



This is an automated message from the Yocto Project Autobuilder
Git: git://git.yoctoproject.org/yocto-autobuilder2
Email: richard.purdie@linuxfoundation.org







Re: util-linux and --enable-raw with recent kernels

Federico Pellegrin
 


Thanks Khem!
Indeed I checked on master but got cheated by the web git interface and I was looking at an older commit :-/
Glad it is the right way to go and already solved on master!

Cheers,
Federico


Il giorno mar 12 ott 2021 alle ore 18:55 Khem Raj <raj.khem@...> ha scritto:


On 10/12/21 9:27 AM, Federico Pellegrin wrote:
>
> Hello,
> Running on a quite recent kernel (5.14.10 from Fedora 34) I've came
> across a problem when building util-linux (2.35.2) native, namely in the
> configure phase:
>
> configure: error: raw selected, but required raw.h header file not available
>

you might want to use latest master, fix that you might find useful is

https://git.openembedded.org/openembedded-core/commit/?id=7f577c10913104860121f682b9b3754870c4db23

> After a bit or research I believe it is due to:
> https://www.mail-archive.com/debian-bugs-dist@.../msg1820154.html
> <https://www.mail-archive.com/debian-bugs-dist@.../msg1820154.html>
>
> Which is related to the change in the recent kernels here:
> https://github.com/torvalds/linux/commit/603e4922f1c81fc2ed3a87b4f91a8d3aafc7e093#diff-10d697dff14540ee1eb6539dcc53b2b88844b6187c1995c0698ba0936754304a
> <https://github.com/torvalds/linux/commit/603e4922f1c81fc2ed3a87b4f91a8d3aafc7e093#diff-10d697dff14540ee1eb6539dcc53b2b88844b6187c1995c0698ba0936754304a>
> where the raw.h file was indeed removed.
>
> As per first link it may not be obvious to fix, and don't see an
> upstream fix for it, but from the Yocto perspective my current
> workaround is basically just to remove "--enable-raw" from the
> EXTRA_OECONF to disable the raw feature.
>
> While the whole image seemed to build fine with this, I'm not very sure
> if that configuration option had a precise use (which maybe it's being
> skipping in my specific build) or not, so I wanted to ask the experts if
> there is any opinion on this and/or should I do a merge request that
> removes it to handle this problem, at least until there is a better
> solution upstream in util-linux?
>
> Many thanks,
> Federico
>
>
>
>


Re: #zeus meta-intel #zeus

Anuj Mittal
 

Did you build everything with this compiler from start? Is opencl-clang
building with the right LLVM lib from meta-clang?

Thanks,

Anuj

On Tue, 2021-10-12 at 17:15 +0000, Monsees, Steven C (US) wrote:

Anuj:

I picked up the tarball for for the baseline dunfell tools platform to
update host tools...

I am seeing it compile cleaner but for one issue causng ld to fail:

/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1331:
undefined reference to `vtable for
llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > >'

Isn't LLVM brought in along with clang under meta-clang ?

Is there a missing build dependency ?

Thanks,
Steve

Build excerpt showing multiple " undefined reference to `vtable "
errors...

/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function
`llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > >::~opt()':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1331:
undefined reference to `vtable for
llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > >'
/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function
`llvm::cl::OptionValue<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >::OptionValue()':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:601:
undefined reference to `vtable for
llvm::cl::OptionValue<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >'
/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function
`llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >
::opt<llvm::cl::FormattingFlags, llvm::cl::desc,
llvm::cl::initializer<char [2]> >(llvm::cl::FormattingFlags const&,
llvm::cl::desc const&, llvm::cl::initializer<char [2]> const&)':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1407:
undefined reference to `vtable for
llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > >'
/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function
`llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> >
::parser(llvm::cl::Option&)':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1072:
undefined reference to `vtable for
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >'
/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function
`llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > >::~opt()':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1331:
undefined reference to `vtable for
llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > >'
/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function
`llvm::cl::OptionValue<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >::OptionValue()':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:601:
undefined reference to `vtable for
llvm::cl::OptionValue<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >'
/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function
`llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > >::opt<char [9],
llvm::cl::desc>(char const (&) [9], llvm::cl::desc const&)':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1407:
undefined reference to `vtable for
llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >, false,
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > >'
/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function
`llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> >
::parser(llvm::cl::Option&)':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1072:
undefined reference to `vtable for
llvm::cl::parser<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >'
collect2: error: ld returned 1 exit status

-----Original Message-----
From: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org> On
Behalf Of Anuj Mittal
Sent: Tuesday, October 12, 2021 10:43 AM
To: Monsees, Steven C (US) <steven.monsees@baesystems.com>;
yocto@lists.yoctoproject.org
Subject: Re: [yocto] #zeus meta-intel

External Email Alert

This email has been sent from an account outside of the BAE Systems
network.

Please treat the email with caution, especially if you are requested to
click on a link, decrypt/open an attachment, or enable macros.  For
further information on how to spot phishing, access “Cybersecurity
OneSpace Page” and report phishing by clicking the button “Report
Phishing” on the Outlook toolbar.


On Tue, 2021-10-12 at 12:43 +0000, Monsees, Steven C (US) wrote:
g++: error: unrecognized command line option ‘-std=c++14’
It looks like the gcc version is too old on your host for this to work.

Thanks,

Anuj


Re: #zeus meta-intel #zeus

Monsees, Steven C (US)
 

Anuj:

I picked up the tarball for for the baseline dunfell tools platform to update host tools...

I am seeing it compile cleaner but for one issue causng ld to fail:

/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1331: undefined reference to `vtable for llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, false, llvm::cl::parser<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >'

Isn't LLVM brought in along with clang under meta-clang ?

Is there a missing build dependency ?

Thanks,
Steve

Build excerpt showing multiple " undefined reference to `vtable " errors...

/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld: IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function `llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, false, llvm::cl::parser<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >::~opt()':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1331: undefined reference to `vtable for llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, false, llvm::cl::parser<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >'
/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld: IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function `llvm::cl::OptionValue<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >::OptionValue()':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:601: undefined reference to `vtable for llvm::cl::OptionValue<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >'
/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld: IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function `llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, false, llvm::cl::parser<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >::opt<llvm::cl::FormattingFlags, llvm::cl::desc, llvm::cl::initializer<char [2]> >(llvm::cl::FormattingFlags const&, llvm::cl::desc const&, llvm::cl::initializer<char [2]> const&)':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1407: undefined reference to `vtable for llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, false, llvm::cl::parser<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >'
/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld: IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function `llvm::cl::parser<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >::parser(llvm::cl::Option&)':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1072: undefined reference to `vtable for llvm::cl::parser<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >'
/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld: IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function `llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, false, llvm::cl::parser<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >::~opt()':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1331: undefined reference to `vtable for llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, false, llvm::cl::parser<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >'
/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld: IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function `llvm::cl::OptionValue<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >::OptionValue()':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:601: undefined reference to `vtable for llvm::cl::OptionValue<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >'
/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld: IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function `llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, false, llvm::cl::parser<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >::opt<char [9], llvm::cl::desc>(char const (&) [9], llvm::cl::desc const&)':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1407: undefined reference to `vtable for llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, false, llvm::cl::parser<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >'
/opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld: IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function `llvm::cl::parser<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >::parser(llvm::cl::Option&)':
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1072: undefined reference to `vtable for llvm::cl::parser<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >'
collect2: error: ld returned 1 exit status

-----Original Message-----
From: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org> On Behalf Of Anuj Mittal
Sent: Tuesday, October 12, 2021 10:43 AM
To: Monsees, Steven C (US) <steven.monsees@baesystems.com>; yocto@lists.yoctoproject.org
Subject: Re: [yocto] #zeus meta-intel

External Email Alert

This email has been sent from an account outside of the BAE Systems network.

Please treat the email with caution, especially if you are requested to click on a link, decrypt/open an attachment, or enable macros. For further information on how to spot phishing, access “Cybersecurity OneSpace Page” and report phishing by clicking the button “Report Phishing” on the Outlook toolbar.


On Tue, 2021-10-12 at 12:43 +0000, Monsees, Steven C (US) wrote:
g++: error: unrecognized command line option ‘-std=c++14’
It looks like the gcc version is too old on your host for this to work.

Thanks,

Anuj


Re: util-linux and --enable-raw with recent kernels

Khem Raj
 

On 10/12/21 9:27 AM, Federico Pellegrin wrote:
Hello,
Running on a quite recent kernel (5.14.10 from Fedora 34) I've came across a problem when building util-linux (2.35.2) native, namely in the configure phase:
configure: error: raw selected, but required raw.h header file not available
you might want to use latest master, fix that you might find useful is

https://git.openembedded.org/openembedded-core/commit/?id=7f577c10913104860121f682b9b3754870c4db23

After a bit or research I believe it is due to:
https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1820154.html <https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1820154.html>
Which is related to the change in the recent kernels here:
https://github.com/torvalds/linux/commit/603e4922f1c81fc2ed3a87b4f91a8d3aafc7e093#diff-10d697dff14540ee1eb6539dcc53b2b88844b6187c1995c0698ba0936754304a <https://github.com/torvalds/linux/commit/603e4922f1c81fc2ed3a87b4f91a8d3aafc7e093#diff-10d697dff14540ee1eb6539dcc53b2b88844b6187c1995c0698ba0936754304a>
where the raw.h file was indeed removed.
As per first link it may not be obvious to fix, and don't see an upstream fix for it, but from the Yocto perspective my current workaround is basically just to remove "--enable-raw" from the EXTRA_OECONF to disable the raw feature.
While the whole image seemed to build fine with this, I'm not very sure if that configuration option had a precise use (which maybe it's being skipping in my specific build) or not, so I wanted to ask the experts if there is any opinion on this and/or should I do a merge request that removes it to handle this problem, at least until there is a better solution upstream in util-linux?
Many thanks,
Federico


util-linux and --enable-raw with recent kernels

Federico Pellegrin
 


Hello,
Running on a quite recent kernel (5.14.10 from Fedora 34) I've came across a problem when building util-linux (2.35.2) native, namely in the configure phase:

configure: error: raw selected, but required raw.h header file not available

After a bit or research I believe it is due to:

Which is related to the change in the recent kernels here:
where the raw.h file was indeed removed.

As per first link it may not be obvious to fix, and don't see an upstream fix for it, but from the Yocto perspective my current workaround is basically just to remove "--enable-raw" from the EXTRA_OECONF to disable the raw feature.

While the whole image seemed to build fine with this, I'm not very sure if that configuration option had a precise use (which maybe it's being skipping in my specific build) or not, so I wanted to ask the experts if there is any opinion on this and/or should I do a merge request that removes it to handle this problem, at least until there is a better solution upstream in util-linux?

Many thanks,
Federico

2081 - 2100 of 57104