[yocto] remove Yocto systemd features
Hi, Yocto pulls in systemd and enable certain features by default.I am trying to remove some features in systemd *225* yocto builds such as logind (just for testing purpose), I was trying to use a '*.bbappend' file with 'PACKAGECONFIG_append' to achieve that, but seems like it only takes options defined in poky/meta/recipes-core/systemd/systemd_225.bb file. systemd_229.bb has logind option, but I'd like to do it in system_225.bb Available options in 225 are resolved/networkd/audit etc listed below. which does not include logind, is there any way I can remove those features? PACKAGECONFIG[xz] = "--enable-xz,--disable-xz,xz" PACKAGECONFIG[cryptsetup] = "--enable-libcryptsetup,--disable-libcryptsetup,cryptsetup" PACKAGECONFIG[microhttpd] = "--enable-microhttpd,--disable-microhttpd,libmicrohttpd" PACKAGECONFIG[elfutils] = "--enable-elfutils,--disable-elfutils,elfutils" PACKAGECONFIG[resolved] = "--enable-resolved,--disable-resolved" PACKAGECONFIG[networkd] = "--enable-networkd,--disable-networkd" PACKAGECONFIG[libidn] = "--enable-libidn,--disable-libidn,libidn" PACKAGECONFIG[audit] = "--enable-audit,--disable-audit,audit" PACKAGECONFIG[manpages] = "--enable-manpages,--disable-manpages,libxslt-native xmlto-native docbook-xml-dtd4-native docbook-xsl-stylesheets-native" PACKAGECONFIG[pam] = "--enable-pam,--disable-pam,libpam" ... ... also I'd like to remove functions like graphical user session support and display service etc. Any ideas if that's possible? Thanks, Michael -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Retrieve SRCREV variable value outside of a specific recipe (not modifying it)
Hi,
My goal is to pull recipe's SRCREV variable into a top level *.bbclass
file. I understand we can use SRCREV_pn- to modify the
revision on the fly outside of recipe in configuration files but when I
print out SRCREV information using ${SRCREV_pn-recipename} all I got back
is the recipe name instead of SREREV value for that specific recipe.
Is there a way to retrieve SREREV value outside of recipe?
Thanks,
Michael
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] do_patch through Yocto fails while "git am" succeed
Does anyone know what's the difference between using Yocto to apply patches and apply patch directly using git command? I am trying to apply patches for arm-trusted-firmware through yocto by extending arm-trusted-firmware.bb file, in .bbappend file, I have: SRC_URI = "file://" I got the following error: ERROR: arm-trusted-firmware-1.2 do_patch: Command Error: 'quilt --quiltrc /build/tmp/sysroots/x86_64-linux/etc/quiltrc push' exited with 1 Output: Applying patch 0002-csu_dma-Added-support-to-load-PL-bitstream.patch (Stripping trailing CRs from patch.) ... some files can be patched patching file Hunk #1 FAILED at 41. 1 out of 1 hunk FAILED -- rejects in file Patch 0002-csu_dma-Added-support-to-load-PL-bitstream.patch does not apply (enforce with -f) However, if using "git am " under cloned arm-trusted-firmware git repo, the patches are successfully patched. What could be the difference? Thanks! -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] do_patch through Yocto fails while "git am" succeed
Hi Khem, I'm using Yocto 2.1 Krogoth, and quilt version is 0.64. The workstation is running Redhat 6.6. Thanks On Wed, Jun 15, 2016 at 5:10 PM, Khem Raj wrote: > On Fri, Jun 10, 2016 at 11:12 AM, Michael Hu wrote: > > Does anyone know what's the difference between using Yocto to apply > patches > > and apply patch directly using git command? > > > > I am trying to apply patches for arm-trusted-firmware through yocto by > > extending arm-trusted-firmware.bb file, in .bbappend file, I have: > > > > SRC_URI = "file://" > > > > I got the following error: > > ERROR: arm-trusted-firmware-1.2 do_patch: Command Error: 'quilt --quiltrc > > /build/tmp/sysroots/x86_64-linux/etc/quiltrc push' exited with 1 Output: > > Applying patch 0002-csu_dma-Added-support-to-load-PL-bitstream.patch > > (Stripping trailing CRs from patch.) > > ... some files can be patched > > patching file > > Hunk #1 FAILED at 41. > > 1 out of 1 hunk FAILED -- rejects in file > > Patch 0002-csu_dma-Added-support-to-load-PL-bitstream.patch does not > apply > > (enforce with -f) > > > > However, if using "git am " under cloned arm-trusted-firmware git > > repo, the patches are successfully patched. > > > > What could be the difference? > > which distro do you use on build host and version of quilt, there were > similar issues e..g with ubuntu 12.04 > on applying patches that were generated with newer quilt versions. > > > > > Thanks! > > > > > > -- > > ___ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto > > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] fetch artifacts from Artifactory
Hello, I am trying to retrieve artifacts from Jfrog Artifactory, I put the https url in the recipe: SRC_URI = "https://artifactory.xx.com/" and Yocto build returns the following error " WARNING: do_fetch: Failed to fetch URL https://artifactory.xx.com/xx ;user=;pswd=, attempting MIRRORS if available ERROR: xx-1.0-r0 do_fetch: Fetcher failure: Fetch command failed with exit code 6, output: Authorization failed. " I tried to remove the 'user' and 'pswd' option, the same error returned. What's the correct syntax for fetching artifacts? Thanks for the help! Michael -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Proper way of rebuilding kernel image
Hi, I am compiling Yocto kernel image with: * a third party's "in-tree" kernel configuration * the same third party's BSP (which has some further kernel configurations as well) * my own kernel configuration fragments for my project on top of the above two What I found was if I make a small change to my own kernel config fragment, e.g. just add an empty line or add a comment, *don't *do a bitbake clean, and bitbake the kernel image again, the "in-tree" kernel configuration doesn't get picked up, therefore the new kernel's .config file is drastically different than a clean build. But If I do a bitbake clean kernel recipe and bitbake the kernel image again, I get the same .config file both times. The way I specify "in-tree" kernel configuration: KBUILD_DEFCONFIG_machine_name ?= "_defconfig" KCONFIG_MODE_machine_name ?="--alldefconfig" What's the proper way of rebuilding kernel image once recipe has changes? Seems like doing a cleanall build every time takes a lot of time and inefficient. Thanks! .M. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
