BB file to build USBIP tools, looking for feedback. Was: building the kernel's usbipd daemon
chuck kamas
I have successfully gotten yocto to build the USBIP-tools directory by adding a bb recipe for it, see below. However, I am sure that I have violated ever good and reasonable best practice! Therefore I am looking for feedback on how to improve the recipe before I attempt to submit it for inclusion in the database.
Feedback is welcome and desired! So please comment. The issues I had to solve to get this recipe to work are: 1) the kernel source is removed from the tmp/work-shared/raspberrypi-cm3/kernel-source when the kernel is done building. I have not figured out how to keep this code populated so that this recipe can access it. I have tried adding DEPENDS = "virtual/kernel" but this did not seem to keep the code around. Is there a best practice for this? 2) the code is in kernel-source/tools/usb/usbip, and is based on autotools. However, those autotools are hidden behind a few scrips: autogen.sh -> runs "autoreconf -i -f -v" and cleanup.sh -> removes all of the autogen code. The issue I am having is that these shell scripts are currently modifying the work-shared/... copy and not a local copy. Should I be concerned? If so how to copy the code to a more reasonable place and then modify it? I saw something in the comments of the perf.bb code that seams to do this.... 3) is there a way to use (or should I) the autotools.bbclass? I have taken some code out of there to properly setup for the configure step. However, I feel that this is a dumb solution and I would rather reuse a class here. But, as far as I can tell the autotools needs to load the code from git and then configure it, but I only need the tools/usb/usbip directory of the kernel. 4) If I were to use the autotools class it is looking for .config files, but these are generated by the autoreconf program. How do I get the class to kick this off? do_configure_prepend ()?? I think that is enough questions for now. Thank you all for your help! Chuck -----------------code start----------------------- SUMMARY = "USBip part of Linux kernel built in tools" DESCRIPTION = " USB/IP protocol allows to pass USB device from server to \ client over the network. Server is a machine which provides (shares) a \ USB device. Client is a machine which uses USB device provided by server \ over the network. The USB device may be either physical device connected \ to a server or software entity created on a server using USB gadget subsystem." LICENSE = "GPLv2" LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/GPL-2.0;md5=801f80980d171dd6425610833a22dbe6" DEPENDS = "virtual/kernel libtool udev" PROVIDES = "virtual/usbip-tools" inherit linux-kernel-base kernel-arch kernelsrc manpages do_populate_lic[depends] += "virtual/kernel:do_patch" do_configure[depends] += "virtual/kernel:do_shared_workdir" EXTRA_OEMAKE = "\ -C ${S}/tools/usb/usbip \ O=${B} \ CROSS_COMPILE=${TARGET_PREFIX} \ CROSS=${TARGET_PREFIX} \ CC="${CC}" \ CCLD="${CC}" \ LD="${LD}" \ AR="${AR}" \ ARCH="${ARCH}" \ TMPDIR="${B}" \ " EXTRA_OEMAKE += "\ 'DESTDIR=${D}' \ KERNEL_SRC=${STAGING_KERNEL_DIR} \ " do_configure[depends] += "virtual/kernel:do_shared_workdir" inherit autotools gettext # stolen from autotools.bbclass CONFIGUREOPTS = " --build=${BUILD_SYS} \ --host=${HOST_SYS} \ --target=${TARGET_SYS} \ --prefix=${prefix} \ --exec_prefix=${exec_prefix} \ --bindir=${bindir} \ --sbindir=${sbindir} \ --libexecdir=${libexecdir} \ --datadir=${datadir} \ --sysconfdir=${sysconfdir} \ --sharedstatedir=${sharedstatedir} \ --localstatedir=${localstatedir} \ --libdir=${libdir} \ --includedir=${includedir} \ --oldincludedir=${oldincludedir} \ --infodir=${infodir} \ --mandir=${mandir} \ --disable-silent-rules \ ${CONFIGUREOPT_DEPTRACK} \ ${@append_libtool_sysroot(d)} \ " do_configure_prepend () { cd ${S}/tools/usb/usbip ./cleanup.sh ./autogen.sh ./configure ${CONFIGUREOPTS} ${EXTRA_OECONF} } do_compile() { oe_runmake } do_install() { oe_runmake DESTDIR=${D} install } PACKAGE_ARCH = "${MACHINE_ARCH}" python do_package_prepend() { d.setVar('PKGV', d.getVar("KERNEL_VERSION", True).split("-")[0]) } B = "${WORKDIR}/${BPN}-${PV}"
|
|
[meta-security][PATCH] python3-fail2ban: fix build failure and cleanup
Fixes:
error in fail2ban setup command: use_2to3 is invalid. ERROR: 'python3 setup.py build ' execution failed. drop custom fail2ban_setup.py remove pyhton-fail2ban as its a symlink to python3 Update to tip for 11.2 branch Signed-off-by: Armin Kuster <akuster808@...> --- .../fail2ban/files/fail2ban_setup.py | 174 ------------------ .../fail2ban/python3-fail2ban_0.11.2.bb | 8 +- 2 files changed, 4 insertions(+), 178 deletions(-) delete mode 100755 recipes-security/fail2ban/files/fail2ban_setup.py diff --git a/recipes-security/fail2ban/files/fail2ban_setup.py b/recipes-security/fail2ban/files/fail2ban_setup.py deleted file mode 100755 index e231949..0000000 --- a/recipes-security/fail2ban/files/fail2ban_setup.py +++ /dev/null @@ -1,174 +0,0 @@ -# emacs: -*- mode: python; py-indent-offset: 4; indent-tabs-mode: t -*- -# vi: set ft=python sts=4 ts=4 sw=4 noet : - -# This file is part of Fail2Ban. -# -# Fail2Ban is free software; you can redistribute it and/or modify -# it under the terms of the GNU General Public License as published by -# the Free Software Foundation; either version 2 of the License, or -# (at your option) any later version. -# -# Fail2Ban is distributed in the hope that it will be useful, -# but WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the -# GNU General Public License for more details. -# -# You should have received a copy of the GNU General Public License -# along with Fail2Ban; if not, write to the Free Software -# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. - -__author__ = "Cyril Jaquier, Steven Hiscocks, Yaroslav Halchenko" -__copyright__ = "Copyright (c) 2004 Cyril Jaquier, 2008-2016 Fail2Ban Contributors" -__license__ = "GPL" - -import platform - -try: - import setuptools - from setuptools import setup - from setuptools.command.install import install - from setuptools.command.install_scripts import install_scripts -except ImportError: - setuptools = None - from distutils.core import setup - -# all versions -from distutils.command.build_py import build_py -from distutils.command.build_scripts import build_scripts -if setuptools is None: - from distutils.command.install import install - from distutils.command.install_scripts import install_scripts -try: - # python 3.x - from distutils.command.build_py import build_py_2to3 - from distutils.command.build_scripts import build_scripts_2to3 - _2to3 = True -except ImportError: - # python 2.x - _2to3 = False - -import os -from os.path import isfile, join, isdir, realpath -import sys -import warnings -from glob import glob - -from fail2ban.setup import updatePyExec - -if setuptools and "test" in sys.argv: - import logging - logSys = logging.getLogger("fail2ban") - hdlr = logging.StreamHandler(sys.stdout) - fmt = logging.Formatter("%(asctime)-15s %(message)s") - hdlr.setFormatter(fmt) - logSys.addHandler(hdlr) - if set(["-q", "--quiet"]) & set(sys.argv): - logSys.setLevel(logging.CRITICAL) - warnings.simplefilter("ignore") - sys.warnoptions.append("ignore") - elif set(["-v", "--verbose"]) & set(sys.argv): - logSys.setLevel(logging.DEBUG) - else: - logSys.setLevel(logging.INFO) -elif "test" in sys.argv: - print("python distribute required to execute fail2ban tests") - print("") - -longdesc = ''' -Fail2Ban scans log files like /var/log/pwdfail or -/var/log/apache/error_log and bans IP that makes -too many password failures. It updates firewall rules -to reject the IP address or executes user defined -commands.''' - -if setuptools: - setup_extra = { - 'test_suite': "fail2ban.tests.utils.gatherTests", - 'use_2to3': True, - } -else: - setup_extra = {} - -data_files_extra = [] - -# Installing documentation files only under Linux or other GNU/ systems -# (e.g. GNU/kFreeBSD), since others might have protective mechanisms forbidding -# installation there (see e.g. #1233) -platform_system = platform.system().lower() -doc_files = ['README.md', 'DEVELOP', 'FILTERS', 'doc/run-rootless.txt'] -if platform_system in ('solaris', 'sunos'): - doc_files.append('README.Solaris') -if platform_system in ('linux', 'solaris', 'sunos') or platform_system.startswith('gnu'): - data_files_extra.append( - ('/usr/share/doc/fail2ban', doc_files) - ) - -# Get version number, avoiding importing fail2ban. -# This is due to tests not functioning for python3 as 2to3 takes place later -exec(open(join("fail2ban", "version.py")).read()) - -setup( - name = "fail2ban", - version = version, - description = "Ban IPs that make too many password failures", - long_description = longdesc, - author = "Cyril Jaquier & Fail2Ban Contributors", - author_email = "cyril.jaquier@...", - url = "http://www.fail2ban.org", - license = "GPL", - platforms = "Posix", - cmdclass = { - 'build_py': build_py, 'build_scripts': build_scripts, - }, - scripts = [ - 'bin/fail2ban-client', - 'bin/fail2ban-server', - 'bin/fail2ban-regex', - 'bin/fail2ban-testcases', - # 'bin/fail2ban-python', -- link (binary), will be installed via install_scripts_f2b wrapper - ], - packages = [ - 'fail2ban', - 'fail2ban.client', - 'fail2ban.server', - 'fail2ban.tests', - 'fail2ban.tests.action_d', - ], - package_data = { - 'fail2ban.tests': - [ join(w[0], f).replace("fail2ban/tests/", "", 1) - for w in os.walk('fail2ban/tests/files') - for f in w[2]] + - [ join(w[0], f).replace("fail2ban/tests/", "", 1) - for w in os.walk('fail2ban/tests/config') - for f in w[2]] + - [ join(w[0], f).replace("fail2ban/tests/", "", 1) - for w in os.walk('fail2ban/tests/action_d') - for f in w[2]] - }, - data_files = [ - ('/etc/fail2ban', - glob("config/*.conf") - ), - ('/etc/fail2ban/filter.d', - glob("config/filter.d/*.conf") - ), - ('/etc/fail2ban/filter.d/ignorecommands', - [p for p in glob("config/filter.d/ignorecommands/*") if isfile(p)] - ), - ('/etc/fail2ban/action.d', - glob("config/action.d/*.conf") + - glob("config/action.d/*.py") - ), - ('/etc/fail2ban/fail2ban.d', - '' - ), - ('/etc/fail2ban/jail.d', - '' - ), - ('/var/lib/fail2ban', - '' - ), - ] + data_files_extra, - **setup_extra -) diff --git a/recipes-security/fail2ban/python3-fail2ban_0.11.2.bb b/recipes-security/fail2ban/python3-fail2ban_0.11.2.bb index ed75a0e..627496f 100644 --- a/recipes-security/fail2ban/python3-fail2ban_0.11.2.bb +++ b/recipes-security/fail2ban/python3-fail2ban_0.11.2.bb @@ -9,10 +9,9 @@ HOMEPAGE = "http://www.fail2ban.org" LICENSE = "GPL-2.0" LIC_FILES_CHKSUM = "file://COPYING;md5=ecabc31e90311da843753ba772885d9f" -SRCREV ="eea1881b734b73599a21df2bfbe58b11f78d0a46" +SRCREV ="d6b884f3b72b8a42b21da863836569ef6836c2ea" SRC_URI = " git://github.com/fail2ban/fail2ban.git;branch=0.11 \ file://initd \ - file://fail2ban_setup.py \ file://run-ptest \ " @@ -20,13 +19,13 @@ inherit update-rc.d ptest setuptools3 S = "${WORKDIR}/git" -do_compile:prepend () { - cp ${WORKDIR}/fail2ban_setup.py ${S}/setup.py +do_compile () { cd ${S} ./fail2ban-2to3 } do_install:append () { + rm -f ${D}/${bindir}/fail2ban-python install -d ${D}/${sysconfdir}/fail2ban install -d ${D}/${sysconfdir}/init.d install -m 0755 ${WORKDIR}/initd ${D}${sysconfdir}/init.d/fail2ban-server @@ -38,6 +37,7 @@ do_install_ptest:append () { install -d ${D}${PTEST_PATH}/bin sed -i -e 's/##PYTHON##/${PYTHON_PN}/g' ${D}${PTEST_PATH}/run-ptest install -D ${S}/bin/* ${D}${PTEST_PATH}/bin + rm -f ${D}${PTEST_PATH}/bin/fail2ban-python } FILES:${PN} += "/run" -- 2.25.1
|
|
Re: How to enable graphics acceleration on qemux86-64?
Alexander Kanavin
If you switch to master, it's best if you make a new build directory and dont reuse the one you have. Alex
On Wed, 13 Oct 2021 at 22:09, Manuel Wagesreither <ManWag@...> wrote:
|
|
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
changing the 'libsss_sudo' to 'libsss-sudo' fixes the errors.
toggle quoted messageShow quoted text
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:
|
|
Re: [meta-security][PATCH] sssd: re-package to fix QA issues
On 10/13/21 1:49 AM, kai wrote:
From: Kai Kang <kai.kang@...>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'
|
|
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:
|
|
Re: How to enable graphics acceleration on qemux86-64?
Manuel Wagesreither
Hi Alex, Am Fr, 8. Okt 2021, um 11:00, schrieb Alexander Kanavin:
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 ?
Sending to Stephen's gmail address.
toggle quoted messageShow quoted text
On 2021-10-13 12:52 p.m., Randy MacLeod wrote:
When will we be doing hardknott's final release: 3.3.4 ? --
# Randy MacLeod # Wind River Linux
|
|
Re: #zeus meta-intel
#zeus
Monsees, Steven C (US)
Anything ?, I have yet to resolve this.
toggle quoted messageShow quoted text
-----Original Message-----
From: Monsees, Steven C (US) Sent: Wednesday, October 13, 2021 9:03 AM To: 'Mittal, Anuj' <anuj.mittal@...>; 'yocto@...' <yocto@...> 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@...>; yocto@... 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@...> Sent: Tuesday, October 12, 2021 10:10 PM To: Monsees, Steven C (US) <steven.monsees@...>; yocto@... 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:
|
|
Re: [ANNOUNCEMENT] Yocto Project 3.3.3 (hardknott-25.0.3) is Released --> When is hardknott's final release: 3.3.4 ?
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@...>
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@...> --- 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) ?
toggle quoted messageShow quoted text
-----Original Message-----
From: Monsees, Steven C (US) Sent: Wednesday, October 13, 2021 7:13 AM To: 'Mittal, Anuj' <anuj.mittal@...>; yocto@... 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@...> Sent: Tuesday, October 12, 2021 10:10 PM To: Monsees, Steven C (US) <steven.monsees@...>; yocto@... 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:
|
|
Re: #zeus meta-intel
#zeus
Monsees, Steven C (US)
Anuj:
toggle quoted messageShow quoted text
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@...> Sent: Tuesday, October 12, 2021 10:10 PM To: Monsees, Steven C (US) <steven.monsees@...>; yocto@... 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:
|
|
[meta-security][PATCH] sssd: re-package to fix QA issues
kai
From: Kai Kang <kai.kang@...>
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@...> --- 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
|
|
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,
toggle quoted messageShow quoted text
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-----
|
|
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:
|
|
Re: #zeus meta-intel
#zeus
Anuj Mittal
Did you build everything with this compiler from start? Is opencl-clang
toggle quoted messageShow quoted text
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:
|
|