On Mon, Aug 20, 2018 at 8:16 AM Seth Bollinger wrote:
> Hello All,
>
> We've been seeing the following warning for a while now. Is this expected?
>
> WARNING: manuf-image-1.0-r0 do_rootfs: Intentionally failing postinstall
> scriptlets of ['coreutils'] to defer them to first
On Mon, Aug 20, 2018 at 8:31 AM Alexander Kanavin
wrote:
> 2018-08-20 15:16 GMT+02:00 Seth Bollinger :
> > We've been seeing the following warning for a while now. Is this
> expected?
> >
> > WARNING: manuf-image-1.0-r0 do_rootfs: Intentionally failing postinstall
>
Hello All,
We've been seeing the following warning for a while now. Is this expected?
WARNING: manuf-image-1.0-r0 do_rootfs: Intentionally failing postinstall
scriptlets of ['coreutils'] to defer them to first boot is deprecated.
Please place them into pkg_postinst_ontarget_${PN} ().
>From
Hello All,
I'm trying to build two different kernels for the same machine. One kernel
supports a manufacturing process, the other production kernel is meant to
run on the device after it's been manufactured. I've manipulated the two
images I'm using to build the two kernels (the solution is
On Thu, Aug 21, 2014 at 7:25 PM, Christopher Larson clar...@kergoth.com
wrote:
On Thu, Aug 21, 2014 at 5:08 PM, Seth Bollinger seth.b...@gmail.com
wrote:
Our device requires two images to be built. Is there any way to have the
first image depend on the second image?
do_rootfs[depends
Hello All,
Our device requires two images to be built. Is there any way to have the
first image depend on the second image?
Thanks,
Seth
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Hello All,
We have a few code bases that we need to run Coverity on. Does someone
have an example of how that would hook into a recipe?
Thanks,
Seth
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Hello All,
I don't see that ldd is part of the cross toolchain build anywhere. Am I
missing something?
Thanks,
Seth
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
The vtX terminfo files aren't being copied on systems where bash isn't
the default shell (debian, etc.). I removed the bash specific syntax
so the files are properly copied on these systems.
Signed-off-by: Seth Bollinger seth.b...@gmail.com
---
meta/recipes-core/ncurses/ncurses.inc |2 +-
1
The vtX terminfo files aren't being copied on systems where bash isn't
the default shell (debian, etc.). I removed the bash specific syntax
so the files are properly copied on these systems.
Signed-off-by: Seth Bollinger seth.b...@gmail.com
---
meta/recipes-core/ncurses/ncurses.inc |2 +-
1
Hello All,
How does yocto know which package version to choose for an image if the
package can be altered (compilation difference, or perhaps config
alteration, etc.) by a DISTRO_FEATURE?
For instance, if I make a change to sysvinit-inittab/inittab based on a
DISTRO_FEATURE, I can have
On Thu, Oct 10, 2013 at 4:31 AM, Paul Eggleton
paul.eggle...@linux.intel.com wrote:
That's really the recommended way to do it. If the software being
configured
supports it, another way is to set it up to read all configuration files
from a
directory and then you can simply install a new
On Thu, Oct 10, 2013 at 9:40 AM, Burton, Ross ross.bur...@intel.com wrote:
You need to use $D so that you're not attempting to write to the *host's*
/etc:
echo test $D/etc/inittest2
In a postinst $D may be set, and if it is then the postinst is being
ran on the host at rootfs time, and
On Thu, Oct 10, 2013 at 10:09 AM, Burton, Ross ross.bur...@intel.comwrote:
Use $D instead of ${D}. ${D} will get expanded when the package is
created but you want to use the environment variable $D.
Looks like that worked! I apologize for missing the curly braces in your
previous response.
Hello All,
What's the best practice for recipes that need to update a shared file
provided by a different recipe? For example let's say that the
widget-watcher recipe creates /etc/ww.conf and the widget1, and widget2
recipes need to append a line to the config. I've searched through the
Hello All,
I'm having a problem with opkg. When I run the image I've built with the
package-management feature and PACKAGE_CLASS equal to package_ipk, the
image has no installed packages. They're obviously installed, because it's
running but opkg list-installed is empty. I was expecting a
Paul Eggleton
June 3, 2013 7:10
47AM
Hi Seth,If
/var/lib/opkg is empty in your image, it can only be because its
contents have been deleted; and that could be either because the
value of IMAGE_FEATURES doesn't end up containing
package-management, or alternatively
Hello All,
I'm trying to create a small SD card image that I can quickly dd to card
and then do an online resize as a post process step to take advantage of
the entire space of the card. Similar to how the raspbian image works.
Unfortunately genext2fs doesn't seem to set this flag (and
Hello All,
I recently ran into a problem in
meta-raspberrypi/classes/sdcard_image-rpi.bbclass
The following was run through my default debian dash shell (I thought I
switched a while back, but I must have reverted my VM image or
something...).
# If SDIMG_ROOTFS_TYPE is a .xz file use
Hello All,
Is anyone maintaining the meta-raspberrypi repository?
Thanks,
Seth
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
When the shell tests for rootfs type I was seeing [[: not found. I
use echo and egrep to test for the xz rootfs type to work around this
error.
Signed-off-by: Seth Bollinger seth.b...@gmail.com
---
classes/sdcard_image-rpi.bbclass |2 +-
1 files changed, 1 insertions(+), 1 deletions
start_cd.elf and fixup_cd.dat are required when running the system with
a 16MB GPU memory configuration. This change copies all files contained
in bcm2835-bootfiles instead of cherry picking.
Signed-off-by: Seth Bollinger seth.b...@gmail.com
---
classes/sdcard_image-rpi.bbclass |6
Hello All,
I've been having some serious problems trying to get my image to rebuild
recipes when their upstream repositories have changed. I have SRCREV =
${AUTOREV} in my recipe and in bitbake -e I see these 2 lines:
# SRCREV=${AUTOREV}
SRCREV=AUTOINC
I've found BB_SRCREV_POLICY and I've set
Hello All,
I currently have a modules*.tgz in my tmp/images/deploy directory that
contains all of the kernel modules built. What's the yocto way to pull
only the modules I care about into the rootfs image?
Thanks,
Seth
___
yocto mailing list
24 matches
Mail list logo
