I can "bitbake jack" without any errors, but when I add jack to my recipe, I get an error that jack not found in the base feeds. Is jack missing from the imx6qsabresd feed?
build$ bitbake jack
WARNING: Unable to get checksum for linux-boundary SRC_URI entry defconfig: file could not be found######################################### | ETA: 00:00:00
Parsing recipes: 100% |#######################################################################################################################| Time: 00:00:56
Parsing of 1340 .bb files complete (0 cached, 1340 parsed). 1732 targets, 77 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "1.20.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "Ubuntu-12.04"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "imx6qsabresd"
DISTRO = "poky"
DISTRO_VERSION = "1.5"
TUNE_FEATURES = "armv7a vfp neon callconvention-hard cortexa9"
TARGET_FPU = "vfp-neon"
meta
meta-yocto = "(nobranch):faf8f8660fae26a14578738b642fdeb08bcb9d54"
meta-oe = "(nobranch):513e7ca20ddd0a5c3b649bf292a67c3e0473d3a8"
meta-fsl-arm = "(nobranch):520339d3266bfd07bb2e593f70489efe4d98baa2"
meta-fsl-arm-extra = "(nobranch):b17d250c7f53a84855fd9a364a996ac5503c7693"
meta-fsl-demos = "(nobranch):cd6275042cdd2d87490521f6cbeb65972ed37a66"
meta-test = "<unknown>:<unknown>"
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Tasks Summary: Attempted 859 tasks of which 846 didn't need to be rerun and all succeeded.
Summary: There was 1 WARNING message shown.
test-image.bb:
COMMON_INSTALL = " \
base-files \
base-passwd \
busybox \
${@base_contains("MACHINE_FEATURES", "systemd", "${SYSTEMD_INSTALL}", "${SYSV_INSTALL}", d)} \
packagegroup-base \
jack \
...
build$ bitbake test-image
Loading cache: 100% |#########################################################################################################################| ETA: 00:00:00
Loaded 1733 entries from dependency cache.
Parsing recipes: 100% |#######################################################################################################################| Time: 00:00:00
Parsing of 1340 .bb files complete (1339 cached, 1 parsed). 1732 targets, 77 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
NOTE: multiple providers are available for jpeg (jpeg, libjpeg-turbo)
NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg
NOTE: multiple providers are available for jpeg-native (jpeg-native, libjpeg-turbo-native)
NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg-native
Build Configuration:
BB_VERSION = "1.20.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "Ubuntu-12.04"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "imx6qsabresd"
DISTRO = "poky"
DISTRO_VERSION = "1.5"
TUNE_FEATURES = "armv7a vfp neon callconvention-hard cortexa9"
TARGET_FPU = "vfp-neon"
meta
meta-yocto = "(nobranch):faf8f8660fae26a14578738b642fdeb08bcb9d54"
meta-oe = "(nobranch):513e7ca20ddd0a5c3b649bf292a67c3e0473d3a8"
meta-fsl-arm = "(nobranch):520339d3266bfd07bb2e593f70489efe4d98baa2"
meta-fsl-arm-extra = "(nobranch):b17d250c7f53a84855fd9a364a996ac5503c7693"
meta-fsl-demos = "(nobranch):cd6275042cdd2d87490521f6cbeb65972ed37a66"
meta-test = "<unknown>:<unknown>"
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: Function failed: do_rootfs (log file is located at /media/work/dora/fsl-community-bsp/build/tmp/work/imx6qsabresd-poky-linux-gnueabi/test-image/0.0+cvs20600815-r1/temp/log.do_rootfs.9775)
ERROR: Logfile of failure stored in: /media/work/dora/fsl-community-bsp/build/tmp/work/imx6qsabresd-poky-linux-gnueabi/test-image/0.0+cvs20600815-r1/temp/log.do_rootfs.9775
Log data follows:
| DEBUG: Executing python function rootfs_process_ignore
| DEBUG: Python function rootfs_process_ignore finished
| DEBUG: Executing python function rootfs_runtime_mapping
| DEBUG: Python function rootfs_runtime_mapping finished
| DEBUG: Executing shell function do_rootfs
| Note: configuring RPM platform settings
| Note: configuring RPM system provides
| Note: configuring RPM DB settings
| Note: configuring Smart settings
|
| Note: adding Smart channel imx6qsabresd (65)
|
| Note: adding Smart channel cortexa9hf_vfp_neon_mx6 (60)
|
| Note: adding Smart channel cortexa9hf_vfp_neon (55)
|
| Note: adding Smart channel all (10)
|
| Note: configuring RPM cross-install scriptlet_wrapper
|
| Updating cache... ######################################## [100%]
|
| Saving cache...
|
| Error: jack not found in the base feeds (imx6qsabresd cortexa9hf-vfp-neon-mx6 cortexa9hf-vfp-neon cortexa9hf-vfp armv7ahf-vfp-neon armv7ahf-vfp armv6hf-vfp armv5ehf-vfp armv5hf-vfp noarch any all).
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_rootfs (log file is located at /media/work/dora/fsl-community-bsp/build/tmp/work/imx6qsabresd-poky-linux-gnueabi/test-image/0.0+cvs20600815-r1/temp/log.do_rootfs.9775)
ERROR: Task 7 (/media/work/dora/fsl-community-bsp/sources/meta-test/recipes-qt/images/test-image.bb, do_rootfs) failed with exit code '1'
NOTE: Tasks Summary: Attempted 4447 tasks of which 4445 didn't need to be rerun and 1 failed.
No currently running tasks (4446 of 4448)
Summary: 1 task failed:
/media/work/dora/fsl-community-bsp/sources/meta-test/recipes-qt/images/test-image.bb, do_rootfs
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
build$
Solved! Go to Solution.
I was able to get the correct answer from the [meta-freescale] mail group.
On Thu, Oct 31, 2013 at 1:15 PM, Doug Schwanke <doug.schwanke@firstviewconsultants.com> wrote:
> I can "bitbake jack" without any errors, but when I add “jack” to my recipe, I get an error that jack not found in the base feeds.
>
> Is “jack” missing from the imx6qsabresd feed or do I need to add some kind of depends?
Neither; this is common for people starting to Yocto to make this mistake. Basically you need to check the binary packages it builds.
When you do:
$: bitbake jack
You are saying ... hey bitbake, please process jack recipe. This has no direct relation to the binaries you get as result.
When you add something in IMAGE_INSTALL or similar, you are asking for the image to install the /binary/. For jack case, the binaries are:
Most probably, you're looking for jack-server binary.
=========================
Adding the following line to my recipe fixed the issue:
libjack jack-server jack-utils \ |
COMMON_INSTALL is included as part of IMAGE_INSTALL. I used qte-in-use-image from the meta-fsl-demos as my template since I need multiple ways to build my image.
IMAGE_INSTALL is actually in my test-common.inc file. All of my other packages that I include into COMMON_INSTALL work. jack is the exception.
My actual test-image.bb look like this:
require test-common.inc
IMAGE_INSTALL = " \
${COMMON_INSTALL} \
\
${QT_DEMOS} \
qt-in-industrial-embedded-smarthome-e \
pciutils \
usbutils \
alsa-utils \
"
The error message "Error: jack not found" indicates to me it was parsed by bitbake.
NOt sure what is going on. Last check: do a search under the sources folder and filter the recipe (find | grep jack). Then make sure the layer is on the bblayers.conf file.
Leo
I was able to get the correct answer from the [meta-freescale] mail group.
On Thu, Oct 31, 2013 at 1:15 PM, Doug Schwanke <doug.schwanke@firstviewconsultants.com> wrote:
> I can "bitbake jack" without any errors, but when I add “jack” to my recipe, I get an error that jack not found in the base feeds.
>
> Is “jack” missing from the imx6qsabresd feed or do I need to add some kind of depends?
Neither; this is common for people starting to Yocto to make this mistake. Basically you need to check the binary packages it builds.
When you do:
$: bitbake jack
You are saying ... hey bitbake, please process jack recipe. This has no direct relation to the binaries you get as result.
When you add something in IMAGE_INSTALL or similar, you are asking for the image to install the /binary/. For jack case, the binaries are:
Most probably, you're looking for jack-server binary.
=========================
Adding the following line to my recipe fixed the issue:
libjack jack-server jack-utils \ |
Great! Also, one way to know the REAL name, is to bake the recipe, then check the subfolders of tmp/work/.../jack/../../packages-split. Most of the times you find the jack-dev, -locale and in the case of jack, you may find the -server or -utils one. Just a tip for the future. So just add the jack-* in your local.conf.
Leo
I'm trying to create an SDK for an image that uses jack. when I bitbake my-image, everything is happy, but when I enter bitbake my-image -c populate_sdk, it complains with
| * satisfy_dependencies_for: Cannot satisfy the following dependencies for jack-dev:
| * jack (= 0.121.0-r0) *
| * opkg_install_cmd: Cannot install package jack-dev.
When I look at tmp/work/../jack/../packages-split I see:
drwx------ 1 dcd dcd 0 Jan 28 13:56 jack
drwx------ 1 dcd dcd 6 Jan 28 13:56 jack-dbg
drwx------ 1 dcd dcd 6 Jan 28 13:56 jack-dev
drwx------ 1 dcd dcd 6 Jan 28 13:56 jack-doc
drwx------ 1 dcd dcd 0 Jan 28 13:56 jack-locale
drwx------ 1 dcd dcd 6 Jan 28 13:56 jack-server
-rw-r--r-- 1 dcd dcd 38 Jan 28 13:56 jack-server.shlibdeps
drwx------ 1 dcd dcd 0 Jan 28 13:56 jack-staticdev
drwx------ 1 dcd dcd 6 Jan 28 13:56 jack-utils
-rw-r--r-- 1 dcd dcd 130 Jan 28 13:56 jack-utils.shlibdeps
drwx------ 1 dcd dcd 6 Jan 28 13:56 libjack
-rw-r--r-- 1 dcd dcd 67 Jan 28 13:56 libjack.shlibdeps
but, the jack directory is empty, and if I look in the deploy-ipks/cortexa9hf-vfp-neon directory I see this:
-rw-r--r-- 2 dcd dcd 1010372 Jan 28 13:56 jack-dbg_0.121.0-r0_cortexa9hf-vfp-neon.ipk
-rw-r--r-- 2 dcd dcd 32324 Jan 28 13:56 jack-dev_0.121.0-r0_cortexa9hf-vfp-neon.ipk
-rw-r--r-- 2 dcd dcd 177666 Jan 28 13:56 jack-doc_0.121.0-r0_cortexa9hf-vfp-neon.ipk
-rw-r--r-- 2 dcd dcd 10234 Jan 28 13:56 jack-server_0.121.0-r0_cortexa9hf-vfp-neon.ipk
-rw-r--r-- 2 dcd dcd 89390 Jan 28 13:56 jack-utils_0.121.0-r0_cortexa9hf-vfp-neon.ipk
-rw-r--r-- 2 dcd dcd 181590 Jan 28 13:56 libjack_0.121.0-r0_cortexa9hf-vfp-neon.ipk
Something changed in my build that made this stop working but I don't know how to resolve it
can you create a higher version recipe and see if that fixes it?
I was not able to find or alter an image that included jack that would create an SDK. I ended up removing it from our image. Note that it builds and installs normally, it's only the populate_sdk that fails.
can you add this into the jack recipe?
ALLOW_EMPTY_${PN}-dev = "1"
Thanks for the pointer and sorry for the long delay. The jack recipe is sort of messed up, because it doesn't create a jack package. Your suggestion failed with this:
| Collected errors:
| * satisfy_dependencies_for: Cannot satisfy the following dependencies for jack-dev:
| * jack (= 0.121.0-r0) *
| * opkg_install_cmd: Cannot install package jack-dev.
However, changing it to
ALLOW_EMPTY_${PN} = "1"
at least allows the populate_sdk task to complete. thanks.
isn't it IMAGE_INSTALL instead of COMMON_INSTALL?
Leo