[yocto] GCC version 8 upgrade
How silly would it be to try and get GCC sdk v8 complied and installed for Jethro? -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Help with out of (python) tree python modules in SDK
I am on Krogoth. I have an autotools inheriting recipe. The configure script runs a python script (in repo), that imports an out-of-python-distro module. I can’t seem to wrap my head around the correct way to express this in terms of dependencies, such that when I build with an SDK, I can import this module. What does seem to work is adding nativesdk-python-foomodule to RRECOMMENDS_python-core_append_class-nativesdk in the python recipe. Is there a better way? My intuition says that: DEPENDS += “python-foomodule-native” translated to words means: to build this package, you need python-foomodule-native. And given that the target -dev packages get included in the SDK when you do this…the same doesn’t appear to be the case for python modules? I feel like I am missing a fundamental concept. Thx for your time. -brad bishop-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] assembling lvm disk images
Does anyone have any experience with assembling an lvm disk image from a bitbake task? My naiive approach to this would be to invent and implement an IMAGE_FSTYPE that builds up the image in a do_image_foo task. But the LVM userspace tools don’t do offline mode so this seems to require the use of things like loopback devices and sudo. Is that a can of worms? Does anyone have any advice on how to do something like this? Pointers to something similar? thx! brad -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] assembling lvm disk images
at 10:28 AM, Schmitt, Richard wrote: Not sure the type of lvm you're trying to use, but we successfully build a dm-verity rootfs offline. It probably is specific to what type of lvm you are using. Rich Thanks for the reply Rich! I’m not exactly sure what is meant by LVM type. If I look at the wikipedia page on devicemapper (https://en.wikipedia.org/wiki/Device_mapper) it lists a number of “mapping targets” - are these the LVM types? If it is, we’d be looking at linear mapping. The broader objective is to have a system with multiple root filesystems on a 16 GB EMMC device, and be able to add/remove/resize additional filesystems using the LVM2 userspace tools, much like a typical binary desktop distro would configure your hard drive. thx - brad -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Build break in the latest openbmc tree.
at 6:38 PM, James Feist wrote: On 8/22/19 3:35 PM, Jae Hyun Yoo wrote: Hi brad, + The mailing list We met a build break while making Intel platform builds. ERROR: No recipes available for: /home/yoojae/workspace/openbmc/meta-security/recipes-kernel/linux/linux-stable_5.2.bbappend It was added by the subtree update patch but there is no main recipe for it. Did we miss something? Thanks, Jae Hi Jae linux-stable is in meta-odroid: https://lists.yoctoproject.org/pipermail/yocto/2019-August/046424.html It isn’t clear to me if meta-security is supposed to have a hard dependency on meta-odroid or not. Hi Armin Could you suggest what the right thing to do here might be? thx! brad -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Build break in the latest openbmc tree.
On Sun, 2019-08-25 at 10:49 -0700, akuster808 wrote: > the meta-security layer should be fix now. > > please update and let me know if not. Thanks Armin! Jae, I've pulled this into OpenBMC. Can you give it a try? -brad -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Build break in the latest openbmc tree.
at 5:16 PM, Jae Hyun Yoo wrote: On 8/27/2019 5:00 PM, Brad Bishop wrote: On Sun, 2019-08-25 at 10:49 -0700, akuster808 wrote: the meta-security layer should be fix now. please update and let me know if not. Thanks Armin! Jae, I've pulled this into OpenBMC. Can you give it a try? Thanks Armin, Brad! I tried it using the latest tree and checked that the build breakage has gone, but a new issue happened while it's building 'qemu-native'. | ERROR: Execution of '/home/yoojae/workspace/openbmc/build/tmp/work/x86_64-linux/qemu-native/4.1.0-r0/temp/run.do_configure.2396' failed with exit code 1: | ERROR: unknown option --disable-libssh So I made a patch to fix the new issue. --- a/poky/meta/recipes-devtools/qemu/qemu.inc +++ b/poky/meta/recipes-devtools/qemu/qemu.inc @@ -137,7 +137,7 @@ PACKAGECONFIG[curses] = "--enable-curses,--disable-curses,ncurses," PACKAGECONFIG[gtk+] = "--enable-gtk,--disable-gtk,gtk+3 gettext-native" PACKAGECONFIG[vte] = "--enable-vte,--disable-vte,vte gettext-native" PACKAGECONFIG[libcap-ng] = "--enable-cap-ng,--disable-cap-ng,libcap-ng," -PACKAGECONFIG[ssh] = "--enable-libssh,--disable-libssh,libssh," +PACKAGECONFIG[ssh] = "--enable-libssh2,--disable-libssh2,libssh2," PACKAGECONFIG[gcrypt] = "--enable-gcrypt,--disable-gcrypt,libgcrypt," PACKAGECONFIG[nettle] = "--enable-nettle,--disable-nettle,nettle" PACKAGECONFIG[libusb] = "--enable-libusb,--disable-libusb,libusb1" Brad, Please apply this change into the qemu recipe. Hi Jae Please send your patch to OE-Core. FWIW I am able to build qemu-native without issue with OpenBMC 93ee980ed9 although I am not using meta-security. thx - brad -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Yocto/bitbake recipe 'diff test'?
> On Nov 12, 2019, at 1:55 AM, Kun Yi wrote: > > Sure, it's partially due to how we set up the build downstream. Our > downstream would put all the needed layers in one bblayers file, so we would > have something like: > > ##OEROOT##/meta \ > ##OEROOT##/meta-poky \ > ##OEROOT##/meta-openembedded/meta-oe \ > ##OEROOT##/meta-openembedded/meta-networking \ > ##OEROOT##/meta-openembedded/meta-python \ > ##OEROOT##/meta-phosphor \ > ##OEROOT##/meta-google \ > ##OEROOT##/meta-google-gbmc \ > ##OEROOT##/meta-aspeed \ > ##OEROOT##/meta-nuvoton \ > ##OEROOT##/meta-openpower \ > ##OEROOT##/meta-ingrasys \ > ##OEROOT##/meta-ingrasys/meta-zaius \ > ##OEROOT##/meta-quanta \ > ##OEROOT##/meta-quanta/meta-gsj \ > ... > > The distinct advantage of this approach is that we would be able to build > images for different machine types using the same layer conf, so the build > doesn't need to be reconfigured if you were to test on another platform. > > The challenge, as you can imagine, is that each meta layer now cannot 'leak' > any variable. e.g. if some recipe in meta-quanta sets a variable for quanta > systems only, then it must specify "_quanta" or a similar suffix to prevent > the variable expansion to apply to other systems. I think this rule is > generally preferred upstream, but not sure whether it is an official > guideline. > > With my proposal, it would be much easier for a multi-system layer setup like > ours to work. Not only that, it would benefit the most common use cases: > moving variable definitions in bitbake recipes, or even just adding a > variable for a particular machine feature. Having a visible diff would make > reviewing the changes so much easier. Thanks for the background Kun. I know yocto has a concept of Q&A checks that can be run - would it make sense to try something like this via that mechanism? Emit warnings (which we can elevate to build failures in CI) if variables aren’t properly overriden? That is nice because it doesn’t require any changes to our CI system. I’ve cross posted to the yocto mailing list in case there is any interest or ideas there. Here is a link to the entire thread as I remove a little too much context I think… https://lists.ozlabs.org/pipermail/openbmc/2019-November/019409.html -brad -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Yocto/bitbake recipe 'diff test'?
> On Nov 12, 2019, at 1:41 PM, Paul Barker wrote: > > have a look at my slides at the start of the Day 1 slide deck at > https://wiki.yoctoproject.org/wiki/YP_Summit_Lyon_2019. This is a great resource for layer best practices. Thanks Paul! -brad -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] bbappend and placing a file into /tmp on the target
I am trying to expand an existing package (base-passwd) and having it place /etc/passwd into /tmp/ I'm failing pretty miserably and am looking for some hints/tips. Mark Bishop Sr. Firmware/Software Engineer - Microwave Subsystems [cid:image001.png@01D281ED.A45F0A90] 4726 Eisenhower Blvd. Tampa, FL 33634 USA T +1 813 901 7293 mbis...@smithsinterconnectinc.com<mailto:mbis...@smithsinterconnectinc.com> smithsinterconnect.com<http://www.smithsinterconnect.com/> TRAK MICROWAVE IS NOW SMITHS INTERCONNECT! -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] bbappend and placing a file into /tmp on the target
VOLATILE-BINDS is kinda what I am looking for, but without the dependency of systemd From: Khem Raj [mailto:raj.k...@gmail.com] Sent: Monday, August 13, 2018 5:54 PM To: Bishop, Mark (STRT) Cc: Yocto Project Subject: Re: [yocto] bbappend and placing a file into /tmp on the target May be look into VOLATILE_BINDS On Mon, Aug 13, 2018 at 1:12 PM Bishop, Mark (STRT) mailto:mbis...@smithsinterconnectinc.com>> wrote: I am trying to expand an existing package (base-passwd) and having it place /etc/passwd into /tmp/ I’m failing pretty miserably and am looking for some hints/tips. Mark Bishop Sr. Firmware/Software Engineer – Microwave Subsystems [cid:image001.png@01D281ED.A45F0A90] 4726 Eisenhower Blvd. Tampa, FL 33634 USA T +1 813 901 7293 mbis...@smithsinterconnectinc.com<mailto:mbis...@smithsinterconnectinc.com> smithsinterconnect.com<http://www.smithsinterconnect.com/> TRAK MICROWAVE IS NOW SMITHS INTERCONNECT! This e-mail contains proprietary information some or all of which may be legally privileged. It is intended for the recipient only. If an addressing or transmission error has misdirected this e-mail, please notify the authority by replying to this e-mail. If you are not the intended recipient you must not use, disclose, distribute, copy, print, or rely on this e-mail. In addition, information contained in or attached to this e-mail may be subject to either 22 C.F.R. Parts 120?130, or 15 C.F.R. Parts 730-774. These regulations prohibit the release or disclosure of certain information contained herein to anyone who is not a U.S. citizen or permanent resident alien, without a license first having been issued. Failure to observe such requirements is a violation of U.S. law that carries serious penalties. -- ___ yocto mailing list yocto@yoctoproject.org<mailto:yocto@yoctoproject.org> https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] do_kernel_checkout() not using the correct directory
I am trying to compile a kernel located in SVN.
I get this error message:
ERROR: linux-xlnx-4.9-xilinx-v2017.2+git20-r0 do_kernel_checkout: S
/tmp/stride/work-shared/plnx_arm/kernel-source is not set to the linux source
directory. Check
ERROR: linux-xlnx-4.9-xilinx-v2017.2+git20-r0 do_kernel_checkout: the recipe
and set S to the proper extracted subdirectory
ERROR: linux-xlnx-4.9-xilinx-v2017.2+git20-r0 do_kernel_checkout: Function
failed: do_kernel_checkout (log file is located at
/tmp/stride/work/plnx_arm-xilinx-linux-gnueabi/linux-xlnx/4.9-xilinx-v2017.2+git20-r0/temp/log.do_kernel_checkout.34928)
ERROR: Logfile of failure stored in:
/tmp/stride/work/plnx_arm-xilinx-linux-gnueabi/linux-xlnx/4.9-xilinx-v2017.2+git20-r0/temp/log.do_kernel_checkout.34928
ERROR: Task
(/opt/pkg/petalinux/2017.2/components/yocto/source/arm/layers/meta-xilinx/recipes-kernel/linux/linux-xlnx_4.9.bb:do_kernel_checkout)
failed with exit code '1'
And my kernel gets downloaded to:
/tmp/stride/work/plnx_arm-xilinx-linux-gnueabi/linux-xlnx/4.9-xilinx-v2017.2+git20-r0/trunk
But Yocto is looking for it in /tmp/stride/work-shared/plnx_arm/kernel-source
Which is why it is failing in kernel-yocto.bbclass when I try and compile a
kernel located in SVN.
If it is a git repo it gets copied into
/tmp/stride/work-shared/plnx_arm/kernel-source and things work nicely.
do_kernel_checkout() {
...
if [ -d "${WORKDIR}/git/" ]; then
# case: git repository
# if S is WORKDIR/git, then we shouldn't be moving or deleting
the tree.
if [ "${source_dir}" != "${source_workdir}" ]; then
if [ -d "${source_workdir}/.git" ]; then
# regular git repository with .git
rm -rf ${S}
mv ${WORKDIR}/git ${S}
else
# create source for bare cloned git repository
git clone ${WORKDIR}/git ${S}
rm -rf ${WORKDIR}/git
fi
fi
cd ${S}
else
# case: we have no git repository at all.
# To support low bandwidth options for building the kernel,
we'll just
# convert the tree to a git repo and let the rest of the
process work unchanged
# if ${S} hasn't been set to the proper subdirectory a default
of "linux" is
# used, but we can't initialize that empty directory. So check
it and throw a
# clear error
cd ${S}
if [ ! -f "Makefile" ]; then
bberror "S ${S} is not set to the linux source
directory. Check "
bbfatal "the recipe and set S to the proper extracted
subdirectory"
fi
..
${S} is set to /tmp/stride/work-shared/plnx_arm/kernel-source when I need one
of the two things to happen:
A) ${S} set to ${WORKDIR}/trunk OR
B) ${WORKDIR}/trunk copied to ${S}/
I could modify that file directly on my machine and move on, but is there a way
I can create an .bbappend or something that will change ${S}
I'm pretty new to Yocto and I'd like to have a solution that resides in my
project folder instead of having to modify Yocto files so that when I do tool
installs on new development machines I can just checkout my project data and
have it work. I'm using Petalinux, so the process would be install that, then
checkout the project and then build it, with the correct ${S} directory flowing
into kernel-yocto.bbclass:do_kernel_checkout()
I'm new Yocto but I've been reading a ton and am looking for some advice.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] do_kernel_checkout() not using the correct directory
I changed the code in arm/layers/core/meta/classes/kernel-yocto.bbclass
From:
.
else
# case: we have no git repository at all.
# To support low bandwidth options for building the kernel,
we'll just
# convert the tree to a git repo and let the rest of the
process work unchanged
# if ${S} hasn't been set to the proper subdirectory a default
of "linux" is
# used, but we can't initialize that empty directory. So check
it and throw a
# clear error
cd ${S}
if [ ! -f "Makefile" ]; then
..
To:
else
# case: we have no git repository at all.
# To support low bandwidth options for building the kernel,
we'll just
# convert the tree to a git repo and let the rest of the
process work unchanged
# if ${S} hasn't been set to the proper subdirectory a default
of "linux" is
# used, but we can't initialize that empty directory. So check
it and throw a
# clear error
if [ -d "${WORKDIR}/trunk/" ]; then
source_workdir="${WORKDIR}/trunk"
if [ "${source_dir}" != "${source_workdir}" ]; then
rm -rf ${S}
mv ${WORKDIR}/trunk ${S}
fi
fi
cd ${S}
if [ ! -f "Makefile" ]; then
And everything is working but it seems that this would be the wrong way to do
this as this is me editing a base class file.
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On
Behalf Of Bishop, Mark (STRT)
Sent: Thursday, November 02, 2017 1:48 PM
To: yocto@yoctoproject.org
Subject: [yocto] do_kernel_checkout() not using the correct directory
I am trying to compile a kernel located in SVN.
I get this error message:
ERROR: linux-xlnx-4.9-xilinx-v2017.2+git20-r0 do_kernel_checkout: S
/tmp/stride/work-shared/plnx_arm/kernel-source is not set to the linux source
directory. Check
ERROR: linux-xlnx-4.9-xilinx-v2017.2+git20-r0 do_kernel_checkout: the recipe
and set S to the proper extracted subdirectory
ERROR: linux-xlnx-4.9-xilinx-v2017.2+git20-r0 do_kernel_checkout: Function
failed: do_kernel_checkout (log file is located at
/tmp/stride/work/plnx_arm-xilinx-linux-gnueabi/linux-xlnx/4.9-xilinx-v2017.2+git20-r0/temp/log.do_kernel_checkout.34928)
ERROR: Logfile of failure stored in:
/tmp/stride/work/plnx_arm-xilinx-linux-gnueabi/linux-xlnx/4.9-xilinx-v2017.2+git20-r0/temp/log.do_kernel_checkout.34928
ERROR: Task
(/opt/pkg/petalinux/2017.2/components/yocto/source/arm/layers/meta-xilinx/recipes-kernel/linux/linux-xlnx_4.9.bb:do_kernel_checkout)
failed with exit code '1'
And my kernel gets downloaded to:
/tmp/stride/work/plnx_arm-xilinx-linux-gnueabi/linux-xlnx/4.9-xilinx-v2017.2+git20-r0/trunk
But Yocto is looking for it in /tmp/stride/work-shared/plnx_arm/kernel-source
Which is why it is failing in kernel-yocto.bbclass when I try and compile a
kernel located in SVN.
If it is a git repo it gets copied into
/tmp/stride/work-shared/plnx_arm/kernel-source and things work nicely.
do_kernel_checkout() {
...
if [ -d "${WORKDIR}/git/" ]; then
# case: git repository
# if S is WORKDIR/git, then we shouldn't be moving or deleting
the tree.
if [ "${source_dir}" != "${source_workdir}" ]; then
if [ -d "${source_workdir}/.git" ]; then
# regular git repository with .git
rm -rf ${S}
mv ${WORKDIR}/git ${S}
else
# create source for bare cloned git repository
git clone ${WORKDIR}/git ${S}
rm -rf ${WORKDIR}/git
fi
fi
cd ${S}
else
# case: we have no git repository at all.
# To support low bandwidth options for building the kernel,
we'll just
# convert the tree to a git repo and let the rest of the
process work unchanged
# if ${S} hasn't been set to the proper subdirectory a default
of "linux" is
# used, but we can't initialize that empty directory. So check
it and throw a
# clear error
cd ${S}
if [ ! -f "Makefile" ]; then
bberror "S ${S} is not set to the linux source
directory. Check "
bbfatal "the recipe and set S to the proper extracted
subdirectory"
fi
.
[yocto] Change initscript level
I am just trying to change modutils.sh to run from /etc/rcS.d/S05modutils.sh to /etc/rcS.d/S15modutils.sh I can't figure this out. I have modified the yocto/source/arm/layers/core/meta/recipes-kernel/modutils-initscripts.bb From: INITSCRIPT_PARAMS = "start 05 S ." To: INITSCRIPT_PARAMS = "start 10 S ." And I still only have S05modutils.sh The pkg_postinst_modutils-initscripts still has "start 05 S ." in build/tmp/work/cortexa9hf-neon-xilinx-linux-gnueabi/modutils-initscripts/1.0-r7/pkgdata/runtime/modutils-initscripts It's quite apparent that I don't know what I'm doing here and I could use some sage advice on how to move these startup levels around. Thank you. Mark Bishop Sr. Firmware/Software Engineer - Microwave Subsystems [cid:image001.png@01D281ED.A45F0A90] 4726 Eisenhower Blvd. Tampa, FL 33634 USA T +1 813 901 7293 mbis...@smithsinterconnectinc.com<mailto:mbis...@smithsinterconnectinc.com> smithsinterconnect.com<http://www.smithsinterconnect.com/> TRAK MICROWAVE IS NOW SMITHS INTERCONNECT! -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] changing the apache2 conf (meta-webserver)
Let me start with that I'm new to Yocto. I've been able to get apache2 onto my zynq board but I need to change the config. I'm using a read-only rootfs and apache won't start because it wants to write to a log file. I know what I need to change in the apache config but I have no idea how to do that in Yocto. Could anyone walk me through it and if I am in the wrong spot, my apologies. Mark Bishop Sr. Firmware/Software Engineer - Microwave Subsystems [cid:image001.png@01D281ED.A45F0A90] 4726 Eisenhower Blvd. Tampa, FL 33634 USA T +1 813 901 7293 mbis...@smithsinterconnectinc.com<mailto:mbis...@smithsinterconnectinc.com> smithsinterconnect.com<http://www.smithsinterconnect.com/> TRAK MICROWAVE IS NOW SMITHS INTERCONNECT! -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] changing the apache2 conf (meta-webserver)
I want to change the ErrorLog entries. It's a common thing to do but I need help in how to do that in Yocto. -Original Message- From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Khem Raj Sent: Monday, February 05, 2018 3:07 PM To: yocto@yoctoproject.org Subject: Re: [yocto] changing the apache2 conf (meta-webserver) On 2/5/18 11:45 AM, Bishop, Mark (STRT) wrote: > Let me start with that I'm new to Yocto. > > > > I've been able to get apache2 onto my zynq board but I need to change > the config. I'm using a read-only rootfs and apache won't start > because it wants to write to a log file. I know what I need to change > in the apache config but I have no idea how to do that in Yocto. > Could anyone walk me through it and if I am in the wrong spot, my apologies. you might need to provide some r/w storage here it seems. Either you can symlink back /tmp to /var/log ( a hack ) or provide a proper storage thats persistent and mount it on /var/log or whereever it is expecting to write. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
