[yocto] [autobuilder] Y-AB in a docker container?

Hi, I use the good old yocto autobuilder in a docker container and it still serves me well, but I would like to move to the shiny new yocto autobuilder. Before I start spending hours to do it myself I wonder if someone already did something like this and is willing to share the Dockerfile(s).

[yocto] warning: #warning _FORTIFY_SOURCE requires compiling with optimization (-O)

Hi, I can see in some examples: warning: #warning _FORTIFY_SOURCE requires compiling with optimization (-O) which can be fixed by passing the proper CFLAGS. Unfortunately the warning is only visible in log files. 1) Is there a way to show compiler warnings when you bitbake on the console (wi

Re: [yocto] Yocto Project Upcoming Conferences and Developer Days

Hi, I think the discussion went a bit off track, which happens on mailing lists after x replies;) Please see my comments in-line. On 03.05.19 21:01, Volosincu, Andreea S wrote: ELCE – Monday, October 28 -30, 2019, Lyon Convention Centre, Lyon, France   Yocto Project is a spons

Re: [yocto] Proper Use of KERNEL_MODULE_AUTOLOAD variable

Hi Ken, Is there any particular reason you don't use the sample[1] for an out of tree kernel module? [1] http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-skeleton/recipes-kernel/hello-mod Regards, Robert -- ___ yocto mailing list yocto@yo

Re: [yocto] Fetch from git every bitbake

Hi Mauro, Can you please elaborate a bit what exactly you try to do? SRCREV = "${AUTOREV}" will get the latest and greatest version from your git repo (the first time and afterwards only if something changed in the git repo) and a rebuild will only be triggered if something changed on your gi

[yocto] supplier workflow

Hi, I came across a scenario, which does not seem too strange, but I am not sure how this can be handled with OE/YP. (just nasty hacks with SSTATE) 1) Company A provides an SDK to to Company B - no source code provided 2) Company B provides a "binary" back to Company A - no source code povided

Re: [yocto] thud, beaglebone-yocto.conf: SERIAL_CONSOLES setting

Hi, On 02.11.18 16:27, Khem Raj wrote: omap serial is obsolete why does linux-yocto keeps using it. seondly, machine config should enable both consoles ttyO0 and ttyS0 if you know that at least one kernel is using ttyO0 How about picking whatever works for you in the kernel conf and in machin

Re: [yocto] 2.6 migration guide

Hi Scott, On 31.10.18 00:06, Scott Rifenbark wrote: I have an initial section at https://yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#moving-to-the-yocto-project-2.6-release, which is based on Richard's input.  I am sure there are more items. You might want to add a link to the bitb

Re: [yocto] Problem with packages during "devtool build"

Hi, On 2018-04-05 21:02, Raymond Yeung wrote: "inherit module" is already in recipes/cgosapi.bb file.  In fact, as I use devtool to "add" the recipe to workspace layer, this .bb file is autogenerated.  I only added the last line that sets KERNELDIR that 3rd Party software's Makefile uses. Di

Re: [yocto] ClamAV PCRE support

Hi Tom, I never tried to get clamav to run, but please see my comments below. On 2018-04-03 16:22, Tom Gibson wrote: Hi Anuj This is happening because clamav is looking for pcre-config (uses it to find pcre paths) and it's not able to locate it ... Even if you do get around this error by pa

Re: [yocto] U-Boot networking broken in Rocko

On 2018-03-26 19:51, akuster808 wrote: I found that this has already been fixed in U-Boot with the commit below.  I think it has something to do with the way GCC 7.1 onwards is now handling memory alignment. I also saw something similar and by upgrading to U-boot 2018.03 the problem went

Re: [yocto] static libraries missing from sdk

Hi, I played around a bit with my autotooled lib, which produces only a static lib. 1) My preferred approach is this: I add to local.conf: TOOLCHAIN_TARGET_TASK_append = " libhw-a-staticdev libhw-a-dev" The recipe looks like this: https://pastebin.com/YLUvQSSx 2) But your approach works a

Re: [yocto] static libraries missing from sdk

Hi, On 2018-02-07 16:01, Mircea Gliga wrote: With this line you try to add -dev (.so), -dbg and staticdev (.a) for **all** packages:     SDKIMAGE_FEATURES += "dev-pkgs dbg-pkgs staticdev-pkgs" I am not sure it makes sense to build and add both the static and dynamic libs to an SDK. Do

Re: [yocto] static libraries missing from sdk

Hi, OK I think I understood. You want a static library and apparently .h and friends as well as the .a file should end up in the SDK and nothing on the rootfs. If you enable staticdev-pkgs in the SDKIMAGE_FEATURES *all* the staticdev pkgs should end up in the SDK (I assume), but you need to

Re: [yocto] static libraries missing from sdk

Hi, On 2018-02-07 09:46, Mircea Gliga wrote: Thanks for your answer. I already have the ALLOW_EMPTY_${PN} = "1" in the recipe What I still don't get is why the -dev gets installed but the -staticdev doesn't, even though the dependency is satisfied (the empty pkg exists). Just to understand

Re: [yocto] static libraries missing from sdk

Hi, On 2018-02-06 14:53, Mircea Gliga wrote: Hello, I have a problem providing a static library in the SDK: I have a recipe that builds a library. It outputs an -dev pkg with the /usr/{include,lib} libs in it and a -staticdev pkg with the static library. The main pkg is empty, in my recipe I h

[yocto] [PATCH] poky: LICENSE in packagegroup makes no sense - removed

Signed-off-by: Robert Berger --- meta/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bb | 1 - 1 file changed, 1 deletion(-) diff --git a/meta/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bb b/meta/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bb

[yocto] more efficient debug kernel

Hi, I usually build a debug kernel with debug info included, which makes it run "suboptimal". Distros build the kernel with CONFIG_DEBUG_INFO enables, but strip symbols out of the resulting kernel and kernel modules, and place them in the separate debuginfo packages. This makes the kernel muc

[yocto] minimize size of SW update bundle

Hi, Imagine you have only a limited bandwidth to your devices available for SW update. So you would like to minimize what's uploaded (over the air) to your devices. How would you do this with yocto? [1] and [2] might be able to do incremental updates, but maybe there are more ideas out ther

Re: [yocto] image dependent pkg versions/pkg variations

Hi, On 2017-10-16 20:54, Andre McCurdy wrote: [1] http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#platdev-building-targets-with-multiple-configurations Good luck! Hehe you don't seem to be convinced that this works;) Regards, Robert --

Re: [yocto] image dependent pkg versions/pkg variations

Hi Andy, On 2017-10-12 01:08, Andre McCurdy wrote: What would you suggest? Create additional variants of the machine config to cover each case, e.g. myboard.conf, myboard-debug.conf, myboard-dummy.conf, etc The -debug, -dummy, etc variants can include the original base version of the machine

[yocto] image dependent pkg versions/pkg variations

Hi, I would like something like this: 1) Produce just a single toolchain like 2) Choose packages depending on image recipe So far so good. This should be pretty standard, but 3) Different package versions depending on the image recipe? Well actually I would like to have root file systems with

Re: [yocto] [meta-xilinx] How to include Xilinx DMA driver

Hi, On 2017-09-08 19:00, Fan Zhang wrote: Hi All, 1. How to include xilinx_dma.c driver in to the poky image build? In case you want to include out-of tree drivers it could work like this[1] in case you want in-tree it's just a kernel patch similar to[2]. Apparently you will need to turn

Re: [yocto] How do you build 2 versions of the same recipe and a specific version from bitbake cmd line

Hi, On 2017-07-14 23:32, Robert Joslyn wrote: Just to clarify, the typical way this is done is to put the major version number as part of the package name. For example, the recipes could be called zeromq3_3.2.2.bb and zeromq4_4.1.5.bb. This assumes zeromq can tolerate having multiple versions i

Re: [yocto] Determining Load Addresses

Hi, On 2017-07-12 08:23, Kenny Koller wrote: I'm trying to piece together the various load addresses used in the boot sequence. I have built core-image-minimal for a Beaglebone. How can I determine which load address and entry point is used when mkimage is called for the kernel? Should I dig i

Re: [yocto] setting groups and users other than root

Hi, On 2017-07-06 08:01, Khem Raj wrote: you can achieve it via already defined abstraction. Please read http://www.yoctoproject.org/docs/2.3/ref-manual/ref-manual.html#ref-classes-useradd You might want to read[1] "user and group configuration to be applied at the image level" as well [1]

[yocto] minimal image without GPLv3

Hi, I am yocto-izing people again and someone asked how to build a minimal Yocto image without GPLv3 components. I said like this[1] 1. Comment out the EXTRA_IMAGE_FEATURES line 2. Set INCOMPATIBLE_LICENSE = "GPL-3.0 LGPL-3.0 AGPL-3.0" ... and indeed a core-image-minimal was built with alternat

[yocto] empty packages

Hi, According to [1]: "By default, BitBake does not produce empty packages." This does not seem to be the case at least for Jethro. If I bitbake something like this[2] for qemuarm I see empty packages like e.g. the -dev package. Now it's getting even more interesting. [3] says: The list of p

[yocto] custom internal toolchain/glibc

Hi, I was wondering what's the process if someone wanted to use, say Jethro or Krogoth, but with different/custom versions of gcc, binutils, glibc e.g. to cook some syscalls and to compile ancient Linux kernels. I came across tcmode-default.inc[1] where such things are defined: GCCVERSION ?= "6.

[yocto] baremetal cross-compiler

Hi, According to the release notes it should be possible to build a baremetal (no glibc/Linux) cross compiler with the YP. I just can't find any information how this could be done. I would like to build a native compiler e.g. for a Cortex-A3 and compile FreeRTOS with it. Please advise, Robert .

Re: [yocto] How to include a own libary into the toolchain(SDK) for an embeeded Linux generated by Yocto?

Hi, On 05/31/2016 06:03 PM, s.jar...@esa-grimma.de wrote:> Hej, > > I am looking for an example where is shown how to include an own library > into the toolchain. > > Let's call the library "myLib". For it I created an recipe "myLib.bb" > and added: > > BBCLASSEXTEND = "native nativesdk" Like

Re: [yocto] docs: standardizing on "+=" versus "_append" for clarity

Hi, On 05/04/2016 02:20 PM, Robert P. J. Day wrote:> > i understand that there are times when you *want* _append to delay > processing until the end, and i understand that conditional appending > with OVERRIDES requires the "_append" syntax, but other than these > special cases, is there an encour

Re: [yocto] upgrade daisy -> jethro

Hi, On 03/23/2016 10:17 AM, Ruben Schwarz wrote: > Hi, > > we have a customized board with Texas Instruments AM335x Processor. It's > based on Beaglebone Black and EVM Starter Kit. > > We have a working yocto-daisy image running U-Boot 2013.07 and Kernel > 3.14. No we want to upgrade to jethro,

[yocto] CONFIG_LATENCYTOP fragment

Hi, That's what I currently use: meta-yocto-bsp= "heads/jethro:347347ad78c4c2502e83f2c2adff61f1ba8fed8b" multi-v7-ml = "heads/jethro-training-v4.1.x:e297c4f7c1baf38faecd6a2fcaa4cab0acea7dc1" The idea is to use a stable kernel + multi_v7_defconfig and add to this patches/configuration f

Re: [yocto] in-tree defconfig

Hi, This seems to do the trick: https://github.com/RobertBerger/meta-mainline/blob/jethro-training-v4.1.x/multi-v7-ml/recipes-kernel/linux/linux-yocto-custom.inc Regards, Robert ..."The scientific name for an animal that doesn't either run from or fight its enemies is lunch." - Michael Fried

[yocto] in-tree defconfig

Hi, What I wanted to do is to start from an in-tree defconfig like multi_v7_defconfig instead of a defconfig file in a kernel recipe (which works). Maybe we have a different definition of an in-tree defconfig file, but what I mean is the output of make multi_v7_defconfig, I guess what you mean is

Re: [yocto] VFAT patent EP 0 618 540

Hi On 10/09/2015 11:20 PM, Ayoub Zaki wrote: > TI Socs Boot Rom code can use Vfat but does not necessarly need it as > Bootloaders (spl, u-boot) can be loaded directly from Raw MMC/eMMC. I just discovered this recently. Something like: sudo dd if=./u-boot/MLO of=${DISK} count=1 seek=1 bs=128k s

Re: [yocto] VFAT patent EP 0 618 540

Hi, On 10/09/2015 10:58 PM, Christian Ege wrote: > A decent U-Boot can load the kernel from ext4. And I do not know any ROM > loader which needs vfat, except maybe this TI SOCs... Yep that's what I mean. The on-chip loader, which loads MLO,... Anyhow I tried to come up with a scenario where some

Re: [yocto] VFAT patent EP 0 618 540

Hi, On 10/09/2015 11:36 AM, Gorny Krystian wrote: > Hi, > > I have a question regarding the VFAT patent (EP 0 618 540) owned by > Microsoft. It’s about common name space for long and short filenames. I > have read that this patent was canceled by Germany / EU, but it’s still > available in the US

Re: [yocto] can any one please tell the difference between DEPENDS and RDEPENDS

On 10/07/2015 09:10 AM, Vivek Per wrote: > Hi, > Can any one please tell the what is the exact difference between > DEPENDS and RDEPENDS . DEPENDS: http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-DEPENDS RDEPENDS: http://www.yoctoproject.org/docs/latest/mega-manual/

[yocto] core-image-minimal + ARCHIVER_MODE[src] = xxx

Hi, With poky 1.8 I try to generate files for license compliance. = add to local.conf: INHERIT += "archiver" ARCHIVER_MODE[src] = "original" seems the only case which builds. = I would like to use ARCHIVER_MODE[src] = "configured" and get: NOTE: Preparing RunQueue ERROR: Task do_a

Re: [yocto] gcc reports sysroot is /not/exist!

Hi, I had a similar problem with you, but was able to fix it by replacing in some global makefile: CXX=${CROSS_COMPILE}g++ CC=${CROSS_COMPILE}gcc LINKER=${CROSS_COMPILE}gcc LOADER=${CROSS_COMPILE}ldd with: #CXX=${CROSS_COMPILE}g++ #CC=${CROSS_COMPILE}gcc #LINKER=${CROSS_COMPILE}gcc LINKER=$(CC)

Re: [yocto] dropbear is not working after including in IMAGE_FEATURES

On 09/10/2015 05:17 PM, Vivek Per wrote:> Hi, > I have included IMAGE_FEATURES += "ssh-server-dropbear" in my > recipe image. and created the image. So you have something like: image-features-image.bb with something like this? --> IMAGE_INSTALL = "packagegroup-core-boot packagegroup-base-

Re: [yocto] gdb/gdbserver vs. eclipse

On 09/05/2015 09:12 PM, Rudolf J Streif wrote: > Robert, > > What version of Poky/OpenEmbedded Core (meta) are you using? I am on the fido branch commit b50596d8f6e858e2e733f2d9913a19c6f3cd5863 plus my own meta layer (which pulls in a 4.1.2 kernel with my own config) and I build a core-image-sa

Re: [yocto] gdb/gdbserver vs. eclipse

Hi, On 09/05/2015 07:17 PM, Rudolf J Streif wrote:>> > I do not have to do that. As a matter of fact the executable on my target is > copied to /usr/bin from the Eclipse workspace. See "Remote Absolute File Path" > in the Debug Configuration. You are right. I erased the other folder on my target,

[yocto] gdb/gdbserver vs. eclipse

Hi, I managed to step form HelloWorld into the C library and friends with a .gdbinit file like this: # don't use default libs from x86/Ubuntu: set sysroot /opt/adt-target-sysroot/beagle-bone-black-ml set solib-absolute-prefix /opt/adt-target-sysroot/beagle-bone-black-ml set solib-search-path /op

[yocto] software upgrade - minimal amount of packages

Hi, Say I build a release with the YP and load this software onto some target. Then I keep on developing, make changes and make another release. At this point I would like to figure out the minimal amount of packages required to install on the target in order to update it to the new release. Co

Re: [yocto] Strange sstate problem

Hi, On 06/10/2015 10:58 PM, Gary Thomas wrote: > I'm building for two similar targets and sharing sstate between > them. Actually, I build for target A and use that sstate cache > in my SSTATE_MIRRORS for target B. If I understand correctly what should happen, then SSTATE_MIRRORS should point to

Re: [yocto] multi-user shared state

Hi, On 06/10/2015 10:25 PM, Luke (Lucas) Starrett wrote: > Hi, > > > > I’m trying to understand the feasibility of shared-state across multiple > users in a development environment. Does anyone have first-hand > experience with this? Am I asking for trouble? Have a look here [1] 3.2.1.2. Co

Re: [yocto] fido: funny ipk behavior

Hi, On 04/30/2015 10:35 PM, Gary Thomas wrote: > > On your target, what do you get from this? > # opkg list-installed libc6 Nothing, since I forgot EXTRA_IMAGE_FEATURES_append = " package-management" Thanks, Robert..."it doesn't matter how beautiful your theory is, it doesn't matter how sma

[yocto] fido: funny ipk behavior

Hi, I have a simple recipe like this: --- DESCRIPTION = "Simple helloworld application + git" SECTION = "examples" LICENSE = "MIT" LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302" FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:" SRCREV = "ecf1f0bc8

[yocto] How to properly add new qemu target + testimage support?

Hi, I hacked together a qemu target which supports vexpress-a9. In order to get core-image-minimal -c testimage to work as well I had to cook meta/lib/oeqa/utils/qemurunner.py scripts/runqemu scripts/runqemu-internal This does not seem to be a generic way to do such a thing. What's the prope

Re: [yocto] Layer model doomed, unless we all work together

Hi, On 11/19/2014 05:19 PM, Philip Balister wrote: > > http://layers.openembedded.org/layerindex/branch/master/duplicates/?l=91&l=123&l=30&l=147&l=168&l=148&l=31&l=65&l=66&l=32&l=124&l=164&l=67&l=149&l=77&l=101&l=118&l=33&l=3&l=34&l=142&l=169&l=35&l=137&l=171&l=139&l=108&l=162&l=81&l=82&l=95&l=12

Re: [yocto] Meta-toolchain, do_populate_sdk, packagegroup-cross-canadian problem

Hi, On 08/11/2014 08:45 AM, Lešek Franek wrote: > ERROR: Logfile of failure stored in: > /modemtec/linux/yocto-daisy/build-socfpga_cyclone5/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/meta-toolchain/1.0-r7/temp/log.do_populate_sdk.12635 Did you check this file? Regards, Robert ...Programming t

Re: [yocto] Meta-toolchain, do_populate_sdk, packagegroup-cross-canadian problem

Hi, On 08/11/2014 08:45 AM, Lešek Franek wrote: > ERROR: Logfile of failure stored in: > /modemtec/linux/yocto-daisy/build-socfpga_cyclone5/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/meta-toolchain/1.0-r7/temp/log.do_populate_sdk.12635 Did you check this file? Regards, Robert ...Programming t

[yocto] automated hardware testing

Hi, I just noticed this [1] and there are rumors that in the next release hardware testing will also work with yocto-autobuilder. I do have a couple of boards deployer in my lab and build with autobuilder images for them. The consoles of my boards are connected via conservers to ethernet and I c

Re: [yocto] [meta-raspberrypi] Problem building core-image-sato-sdk

On 03/09/2014 02:08 PM, Federico Vitali wrote: > Hi everyone, > > I've succesfully build core-image-sato for raspberry pi, but when I try > to build the sdk version I obtain the following error: > BTW I get the error also with core-image-sato: builder@ubuntu-srvr-lv:~/rpi/poky/raspberrypi/conf$

Re: [yocto] [meta-raspberrypi] Problem building core-image-sato-sdk

Hi, On 03/09/2014 02:08 PM, Federico Vitali wrote: > Hi everyone, > > I've succesfully build core-image-sato for raspberry pi, but when I try > to build the sdk version I obtain the following error: > > ERROR: Multiple .bb files are due to be built which each provide > virtual/libgles2 > (/home/

[yocto] fetcher from gitpod

Hi, I would like to fetch some get repos (currently u-boot and kernel) from a local git caching server[1]. This means if something changed on git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git since the last invocations it updates the changes, if nothing changed it provides the

Re: [yocto] u-boot 2013.10 LIC_FILES_CHKSUM points to an invalid file

Hi Paul, On 12/23/2013 10:56 PM, Paul Eggleton wrote: > >> How do I get it to build? > > In the absence of any other license statement, you'd have to point to one or > more of the source files and use beginline and endline to select just the > part > of the header specifying the license. Th

[yocto] u-boot 2013.10 LIC_FILES_CHKSUM points to an invalid file

Hi, I try to build instead of u-boot v2013.07 [1] the latest and greatest released version i.e. v2013.10[2]. ... which does not build because LIC_FILES_CHKSUM points to an invalid file ... ... and yes it does, since the COPYING file is gone ... The licencense info is contained in the source cod

Re: [yocto] Embedded Linux with Xenomai support

Hi, On 08/30/2013 07:56 PM, Darren Hart wrote: >> Is there any Linux distribution based on the Yocto project that lets >> me configure my embedded kernel with Xenomai? If not, has anybody got >> any experinece in adding Xenomai to the Yocto project? > > I am not aware of anyone using Xenomai wi

Re: [yocto] can not build yocto on NFS mounted NAS

Hi, Gary is, as usual, right ;) Now I have the following test setup: nfs server: Ubuntu 12.04.2 LTS server *(sync,insecure,rw,no_root_squash) client: : nfs auto,noatime,nolock,intr,tcp,actimeo=1800 0 0 mkdir -p /${HOSTNAME}/manual-build/ source oe-init-build-env /${HOSTNAME}/manual-buil

Re: [yocto] can not build yocto on NFS mounted NAS

Hi, On 08/20/2013 07:45 PM, lot...@denx.de wrote: > > Hi, > I have just two points here to ask: > > 1) Wouldn't simply using SSTATE_MIRRORS be a better solution here, instead? It's not the same. SSTATE and DL_DIR are on an nfs export anyhow and this works. The problem here is with TMP dir (a

Re: [yocto] can not build yocto on NFS mounted NAS

Hi, Just for the record I was able to remove the hard link with a small patch and now things look good (so far) - although it will consume more disk space. diff --git a/meta/lib/oe/path.py b/meta/lib/oe/path.py index faa0f61..3225993 100644 --- a/meta/lib/oe/path.py +++ b/meta/lib/oe/path.py @@ -

Re: [yocto] [Announcement] Yocto Project 1.5 Milestone 3 now available.

Hi, On 08/12/2013 12:44 PM, Paul Eggleton wrote: > > There's not much on the autobuilder side apart from ensuring the appropriate > configuration is set - one of the aims was to avoid too much intrusion into > the > autobuilder code. The main class is testimage.bbclass, so you can just do > I

Re: [yocto] [Announcement] Yocto Project 1.5 Milestone 3 now available.

Hi, On 08/12/2013 12:28 PM, Paul Eggleton wrote: > > I agree. In fact our test lab would probably be limited to the reference > boards that the Yocto Project officially supports within meta-yocto i.e. what > we > currently test on manually. I have the Yocto reference boards as well, but will

Re: [yocto] [Announcement] Yocto Project 1.5 Milestone 3 now available.

Hi, On 08/12/2013 02:30 PM, Björn Stenberg wrote: > Paul Eggleton wrote: >> Right, that's what we would be aiming for. Perhaps you could talk a little >> bit about how you manage your hardware testing and any additional software >> and scripts you make use of there? > > We run our tests from buil

Re: [yocto] [Announcement] Yocto Project 1.5 Milestone 3 now available.

Hi, On 08/10/2013 01:02 PM, Paul Eggleton wrote: > > The new framework replaces the old, is written in python and makes writing > tests much easier. As a result we are going through a process of adding many > more runtime tests than we had previously. I'm confused now. Is it autobuilder + new

Re: [yocto] [Announcement] Yocto Project 1.5 Milestone 3 now available.

Hi, On 08/10/2013 03:22 AM, Flanagan, Elizabeth wrote: > * Infrastructure for automated QA testing. More testcases will be > automated in the next milestone release. Are we talking about test automation using autobuilder here? As far as I can see runtime testing of images using QEMU is planned/al

Re: [yocto] can not build yocto on NFS mounted NAS

Hi, On 08/08/2013 08:52 PM, Gary Thomas wrote: > > I'm trying this now with my Ubuntu 12.04 laptop and the same NFS server. > Looks like it's working just fine, it's already made it through the first > phase of a fresh build (building all the necessary 'native' tools), so I > think it will work a

Re: [yocto] can not build yocto on NFS mounted NAS

Hi, On 08/08/2013 06:23 PM, Gary Thomas wrote: >> >> How you do this? >> >> Do you use some magic build setting for this or a symlink to the nfs? > > > I used the standard setup script, like this: > % . /local/poky/oe-init-build-env /MY_NFS_VOLUME/build_dir > > This will create a build tree o

Re: [yocto] can not build yocto on NFS mounted NAS

Hi, On 08/08/2013 05:53 PM, Gary Thomas wrote: > > Interesting. I'm building now - OEROOT on a local ext3 file system, > build/tmp on NFS - and it's working just fine. My host is Fedora (15). > /poky /beagle-xm /cache /conf /tmp<--- this /tmp? How you do this? Do you use s

[yocto] can not build yocto on NFS mounted NAS

Hi, I tried to build to build bitbake core-image-minimal-dev on some nfs mounted NAS. Pseudo is not present but is required, building this first before the main build Parsing recipes: 100% |###

Re: [yocto] gcov on beagle-xm with kernel module

Hi, Looks like it's an issue with the arm eabi compiler producing code, which the kernel gcov framework can't deal with. I guess there are 2 options: 1) toolchain not eabi (not feasible) 2) patch gcov framework in kernel Regards, Robert ..."In the beginning, there was software. And it wasn't g

[yocto] gcov on beagle-xm with kernel module

Hi, I still try to use gcov on the beagle-xm on a kernel module and I'm not sure this is the right mailing list to ask. I just build it with the following modification to the makefile: GCOV_PROFILE_debugfs.o := y and it builds;) ... but as soon as I try and insmod I get the following: insmod

Re: [yocto] gcov on target

Hi, After compiling with: GCOV_PROFILE := y I get: insmod debugfs.ko Error: could not insert module debugfs.ko: Invalid module format unknown relocation: 38 Is this a known issue, or am I doing something stupid? Regards, Robert ..."In the beginning, there was software. And it wasn't good.

Re: [yocto] gcov on target

Hi, After compiling with: GCOV_PROFILE := y I get: insmod debugfs.ko Error: could not insert module debugfs.ko: Invalid module format unknown relocation: 38 Is this a known issue, or am I doing something stupid? Regards, Robert ..."In the beginning, there was software. And it wasn't good.

Re: [yocto] gcov on target

Hi Thomas, On 01/11/2013 06:19 PM, Thomas Petazzoni wrote: >> Did someone manage to build/run gcov for an armv7a? >> ... or let's put it otherwise: Why doesn't it exist on the target? > > I supposed the idea is to generate to coverage data on the target, and > then analyze them with gcov on the bu

[yocto] gcov on target

Hi, I use Yocto Project, 1.3 "danny" for a beagle-xm and would like to show kernel code coverage with a core-image-sato-sdk. This image is pretty complete. Unfortunately there is no gcov available on the target. It looks like it's only built for the host. Did someone manage to build/run gcov for

Re: [yocto] Classes

Hi, How about these classes by the Linux Foundation? https://training.linuxfoundation.org/courses/linux-developer/building-embedded-linux-with-yocto-crash-course https://training.linuxfoundation.org/courses/linux-developer/building-embedded-linux-with-yocto ... and of course there is also custo

Re: [yocto] beagleboard not booting

On 07/18/2012 02:27 PM, Edward Vidal wrote: > Hello, > Close to the USB I see a C and close to speaker XM I am assuming the > This is XM-C OK > What would be the process to use > > 3.4.x kernel and a mainline u-boot. > I am new to poky and don't know much about bit bake and openembedded. > > Ca

Re: [yocto] beagleboard not booting

Hi, On 07/18/2012 03:54 AM, Edward Vidal wrote: > Hello, > The beagleboard that I am using is XM. Which revison? C? Can you try to build a mainline 3.4.x kernel and a mainline u-boot and see what happens? ..."I'm afraid that I've seen too many people fix bugs by looking at debugger output, and

Re: [yocto] beagleboard not booting

On 07/18/2012 01:40 PM, Edward Vidal wrote: > > # CONFIG_PREEMPT_RCU is not set > CONFIG_PREEMPT_NONE=y > # CONFIG_PREEMPT_VOLUNTARY is not set > # CONFIG_PREEMPT is not set > For beagleboard XM should this value be CONFIG_PREEMPT_NONE=n I guess this is what Bruce would like you to try out. ...

Re: [yocto] Not booting on BeagleBoard xM 0x2

Garry/Andrea, I am currently giving a training based on the Beagle-XM an this error happened at the same time on 5 boards with a 3.1 kernel. > error pattern. It hangs at this point: > Waiting for root device /dev/mmcblk0p2... > mmc0: error -110 whilst initialising SD card > The fix was to

Re: [yocto] Raspberry Pi

Hi, On 12/17/2011 01:37 AM, Chris Tapp wrote: > Not quite. It's been due 'any time now' for a couple of months, but it > looks as if it's now going to be early 2012. > > It looks like a few of us are going to be busy in the New Year... > > Chris Tapp According to (hopefully) reliable sources w

[yocto] qemu-system-mipsel

Hi, Can someone please tell me what needs to be done to build qemu-system-mipsel or provide a patch for it? openembedded seems to be able to build something like this, so maybe it would not be too difficult to cook some of the files from oe for yocto-poky. Please advise, Robert..."The IQ of the

Re: [yocto] Poky release is 5.0 "Bernard" confusion

Hi Scott, > > This suggests to me that your local git repository isn't up to date. The > tag has been moved at least once since it was created, and it sounds > like your repository is behind the most recent move of the tag. > > Note: if you use git fetch --all, that will fetch new tags but doesn

[yocto] Poky release is 5.0 "Bernard" confusion

Hi, Can someone please tell me if there is a tag in git://git.pokylinux.org/poky.git which corresponds to the official release tarball and what it is? What puzzles me is that if you check out bernard-5.0 from the git repository it does not correspond to http://www.yoctoproject.org/downloads/poky/

[yocto] Change Endianess for MIPS build

Hi, I was wondering what needs to be done to build (at least) a little endian qemu root file system for MIPS. Yocto builds this: ELF 32-bit MSB executable, MIPS, MIPS64 version 1 (SYSV), dynamically linked (uses shared libs), not stripped I would need this: ELF 32-bit LSB executable, MIPS, MIP

Re: [yocto] internal compiler error with qt building poky-image-lsb-sdk

Hi Khem, On 03/27/2011 08:32 AM, Khem Raj wrote: > On (26/03/11 17:53), Robert Berger wrote: >> Hi, >> >> The short version: >> >> With commit f8539239bc473279cc475b07c22e1e96514c6d2f Thu Mar 24 13:03:50 >> 2011 + both beagleboard and routerstation

[yocto] internal compiler error with qt building poky-image-lsb-sdk

Hi, The short version: With commit f8539239bc473279cc475b07c22e1e96514c6d2f Thu Mar 24 13:03:50 2011 + both beagleboard and routerstationpro fail to build due to an internal compiler error: ../../include/QtCore/../../src/corelib/tools/qstring.h:187:17: note: the mangling of 'va_list' has cha

Re: [yocto] run-time problem - poky-image-lsb-sdk-beagleboard

Hi, On 03/24/2011 02:53 PM, Gary Thomas wrote: > > What does /etc/network/interfaces show? Is it different between the two > images? > > n.b. I've not tried any of the LSB images, just poking in the dark. > To our both surprise they are identical (see below). ... and if you ask my uneducated

[yocto] run-time problem - poky-image-lsb-sdk-beagleboard

Hi, Using rpm instead of ipk I'm able to build poky-image-lsb-sdk-beagleboard even with the lastest and greatest from git (commit aeaa356a5ee77b4596c479451a9db289381a4d16 Sat Mar 19 01:30:12 2011 +) The problem I have now is, that on my beagle-xm networking does not seem to get an IP address

Re: [yocto] build failure 2 - poky-image-lsb-sdk-beagleboard with bernard-5.0

Hi Scott, On 03/23/2011 01:01 AM, Scott Garman wrote: > > Hi Robert, > > Could you please report this in our bugzilla? I seem to recall running > into something like this too. > > http://bugzilla.pokylinux.org > http://bugzilla.pokylinux.org/show_bug.cgi?id=924 > Thanks, > > Scott > Regar

Re: [yocto] build failure 2 - poky-image-lsb-sdk-beagleboard with bernard-5.0

I think it boils down to the fact, that meta/recipes-core/base-files/base-files/sysctl.conf meta/recipes-extended/procps/procps-3.2.8/sysctl.conf are different and both should end up at the rootfs. I guess I could just remove the procps package. But how to resolve this in a more elegant way and

[yocto] build failure 2 - poky-image-lsb-sdk-beagleboard with bernard-5.0

Hi, After resolving the first issue I did a fresh build from scratch using the bernard-5.0 tag and that's what I get: Collected errors: * resolve_conffiles: Existing conffile /work/rber/poky-bernard-5.0-build-bb/tmp/work/beagleboard-poky-linux-gnueabi/poky-image-lsb-sdk-1.0-r0/rootfs/etc/sysctl.

Re: [yocto] build failure - poky-image-lsb-sdk-beagleboard

Hi Scott, On 03/21/2011 06:42 PM, Scott Garman wrote: > > Hi Robert, > > I'm guessing you're building on a Debian-based host distro. Please > ensure both the groff and groff-base packages are installed. > > We just recently fixed our Quick Start guide to include the groff > package dependency f

[yocto] build failure - poky-image-lsb-sdk-beagleboard

Hi, I don't know if I'm posting to the right mailing list, but just wanted you to know that the latest and greatest from git fails when trying to build poky-image-lsb-sdk for beaglebaord. | make[3]: Leaving directory `/work/rber/poky-2011-03-20-snap-oe-build-bb/tmp/work/armv7a-poky-linux-gnueabi/

Re: [yocto] yocto supported freescale eval boards

Hi, We're currently using the following board. http://search.digikey.com/scripts/DkSearch/dksus.dll?PName?Name=MPC8315E-RDBA-ND&Site=US&Lang=EN Just FYI it looks like this board is not available in Europe from Digikey due to U.S. export controls. Some kind of top secret U

  1   2   >