Swi-fx30-catm_3.0.0 build error in swi-linux

IoT Gateways FX30
41

yes, with sandboxed : false its showing correct time.

42

So there are two solutions:

  1. use unsandboxed app
  2. use legato API to get clock
43

@cchenry , I am running into the same problem here. I can build fine after a make clean but then I need to configure the kernel for CIFS support ( bitbake linux-quic -c menuconfig which I configure as a kernel module) after which make fails with:

ERROR: sierra-git-r0 do_package: QA Issue: sierra-lowtempfix is listed in PACKAGES multiple times, this leads to packaging errors. [packages-list]
ERROR: sierra-git-r0 do_package: Fatal QA errors found, failing task.
ERROR: sierra-git-r0 do_package: Function failed: do_package
ERROR: Logfile of failure stored in: /home/dcchurchill/myWorkspace/swi-linux-src/build_bin/tmp/work/armv7a-neon-poky-linux-gnueabi/sierra/git-r0/temp/log.do_package.32137
ERROR: Task (/home/dcchurchill/myWorkspace/swi-linux-src/meta-swi-extras/meta-swi-mdm9x28-bin/recipes/sierra/sierra_git.bb:do_package) failed with exit code '1'

Is there any way around this catch-22 where I can only successfully build after a make clean but that wipes out any kernel customizations in swi-linux-src/build_bin? Can this share state cache be used as a solution? If so, what is the sequence exactly? I know I have to enable it in my local.conf but can I point it to a local copy of the cache, instructions that I’ve found seem to indicate that it must be hosted on an HTTP, FTP or NFS server?

44

Hi @david.churchill, @ravishkrishnan.kunch ,

You can definitely use the bitbake command to modify your kernel config, but this command isn’t ideal since it modifies your patched kernel workspace.

A couple of way to try adding your kernel options:

  1. Modified the original source directly by editing the FX30 specific defconfig
    Edit the file “/kernel/arch/arm/configs/mdm9607-fx30_defconfig”
    This contains the additional FX30 kernel options. When yocto builds the kernel, these options are pulled into the kernel workspace.

  2. Add the kernel options within your recipe. Yocto is supposed to easily add kernel options by reading a CFG file within a recipe. There’s a built-in cfg added for this purpose here:
    “meta-columbia-x/meta-columbia-x-bsp/recipes-kernel/linux/files/kernel-opts.cfg”

You should be able to just add your options here, and these will be added to the .config file when the kernel recipe builds.

To build using local sstate cache, you should be able to do something like this:

  1. Build your workspace

  2. Copy the cache to the location of your choice, for ex. “~/mycache”

  3. Build your new workspace that points to the cache:

$ cd <workspace>
$ make SSTATE_DIR=~/mycache

Hope this helps.
BR,
Chris