UPDATE : It started to bitbake!!
I now get the following error, and it stops to bitbake core-image-minimal in the middle:
Initialising tasks: 100% |##################################################################################################################| Time: 0:00:04
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: systemd-1_232-r0 do_patch: Command Error: 'quilt --quiltrc /home/rama/repositories/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/systemd/1_232-r0/recipe-sysroot-native/etc/quiltrc push' exited with 0 Output:
Applying patch 0001-systemd-udevd.service.in-set-MountFlags-shared.patch
patching file units/systemd-udevd.service.in
Hunk #1 FAILED at 21.
1 out of 1 hunk FAILED -- rejects in file units/systemd-udevd.service.in
Patch 0001-systemd-udevd.service.in-set-MountFlags-shared.patch does not apply (enforce with -f)
ERROR: systemd-1_232-r0 do_patch: Function failed: patch_do_patch
ERROR: Logfile of failure stored in: /home/rama/repositories/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/systemd/1_232-r0/temp/log.do_patch.1928
ERROR: Task (/home/rama/repositories/poky/meta/recipes-core/systemd/systemd_232.bb:do_patch) failed with exit code '1'
NOTE: Tasks Summary: Attempted 1156 tasks of which 1105 didn't need to be rerun and 1 failed.
Summary: 1 task failed:
/home/rama/repositories/poky/meta/recipes-core/systemd/systemd_232.bb:do_patch
Summary: There were 2 WARNING messages shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
This is the build configuration output of bitbake I finally get:
Build Configuration:
BB_VERSION = "1.34.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal-4.8"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "apalis-imx6"
DISTRO = "poky"
DISTRO_VERSION = "2.3.2"
TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard cortexa9"
TARGET_FPU = "hard"
meta
meta-poky
meta-yocto-bsp
meta-toradex = "pyro:a75a2f4272226e924d8c9deb699a19ca9e606a5b"
meta-mender-core = "pyro:302111e4a79e4844cad536fcc9475764eb254611"
meta-freescale = "pyro:06178400afbd641a6709473fd21d893dcd3cfbfa"
meta-freescale-3rdparty = "pyro:9613dbc02ca970122a01c935bc9e5789ced73a9d"
EDIT : as suggested by #Anders I replaced meta-fsl-arm and meta-fsl-arm-extra which were on pyro branch (I checked) with meta-freescale-3rdparty. I now get the following error:
ERROR: Layer 'fsl-arm-extra' depends on layer 'freescale-layer', but this layer is not enabled in your configuration
ERROR: Layer 'fsl-arm-extra' depends on layer 'freescale-layer', but this layer is not enabled in your configuration
EDIT: It said the file is missing so I supplied it the following file from here http://cgit.openembedded.org/openembedded-core/tree/meta/classes/image_types_uboot.bbclass?h=daisy
created a file and now I get the following error:
ERROR: /home/rama/repositories/poky/meta-fsl-arm/recipes-fsl/images/fsl-image-mfgtool-initramfs.bb: No IMAGE_CMD defined for IMAGE_FSTYPES entry 'sdimg' - possibly invalid type name or missing support class
ERROR: Failed to parse recipe: /home/rama/repositories/poky/meta-fsl-arm/recipes-fsl/images/fsl-image-mfgtool-initramfs.bb
I tried bitbaking a file, when I did I get the following error:
ERROR: ParseError at /home/rama/repositories/poky/meta/classes/image.bbclass:185: Could not inherit file classes/image_types_uboot.bbclass
I have the following meta-layers, all on the pyro branch, I tried playing around with the branches I still get the same error somehow :
meta
meta-mender-core
meta-toradex
meta-fsl-arm
meta-fsl-arm-extra
meta-qt5
If I add the meta-angstrom to the above I get the following error:
ERROR: ExpansionError during parsing /home/rama/repositories/poky/meta-angstrom/recipes-angstrom/angstrom/angstrom-version.bb
Traceback (most recent call last):
bb.data_smart.ExpansionError: Failure expanding variable do_install, expression was install -d /home/rama/repositories/poky/build/tmp/work/apalis_imx6-poky-linux-gnueabi/angstrom-version/2_2.3.2-r12/image/etc
echo "Angstrom 2.3.2 (Core edition)" > /home/rama/repositories/poky/build/tmp/work/apalis_imx6-poky-linux-gnueabi/angstrom-version/2_2.3.2-r12/image/etc/angstrom-version
echo "Built from branch: pyro" >> /home/rama/repositories/poky/build/tmp/work/apalis_imx6-poky-linux-gnueabi/angstrom-version/2_2.3.2-r12/image/etc/angstrom-version
echo "Revision: a75a2f4272226e924d8c9deb699a19ca9e606a5b" >> /home/rama/repositories/poky/build/tmp/work/apalis_imx6-poky-linux-gnueabi/angstrom-version/2_2.3.2-r12/image/etc/angstrom-version
echo "Target system: arm-poky-linux-gnueabi" >> /home/rama/repositories/poky/build/tmp/work/apalis_imx6-poky-linux-gnueabi/angstrom-version/2_2.3.2-r12/image/etc/angstrom-version
echo "${#get_layers(bb, d)}" > /home/rama/repositories/poky/build/tmp/work/apalis_imx6-poky-linux-gnueabi/angstrom-version/2_2.3.2-r12/image/etc/angstrom-build-info
echo "VERSION=\"2.3.2\"" > /home/rama/repositories/poky/build/tmp/work/apalis_imx6-poky-linux-gnueabi/angstrom-version/2_2.3.2-r12/image/etc/os-release
echo "VERSION_ID=\"2.3.2\"" > /home/rama/repositories/poky/build/tmp/work/apalis_imx6-poky-linux-gnueabi/angstrom-version/2_2.3.2-r12/image/etc/os-release
echo "NAME=\"Angstrom\"" >> /home/rama/repositories/poky/build/tmp/work/apalis_imx6-poky-linux-gnueabi/angstrom-version/2_2.3.2-r12/image/etc/os-release
echo "ID=\"angstrom\"" >> /home/rama/repositories/poky/build/tmp/work/apalis_imx6-poky-linux-gnueabi/angstrom-version/2_2.3.2-r12/image/etc/os-release
echo "PRETTY_NAME=\"The Ångström Distribution 2.3.2\"" >> /home/rama/repositories/poky/build/tmp/work/apalis_imx6-poky-linux-gnueabi/angstrom-version/2_2.3.2-r12/image/etc/os-release
echo "ANSI_COLOR=\"1;35\"" >> /home/rama/repositories/poky/build/tmp/work/apalis_imx6-poky-linux-gnueabi/angstrom-version/2_2.3.2-r12/image/etc/os-release
echo "HOME_URL=\"http://www.angstrom-distribution.org\"" >> /home/rama/repositories/poky/build/tmp/work/apalis_imx6-poky-linux-gnueabi/angstrom-version/2_2.3.2-r12/image/etc/os-release
install -d /home/rama/repositories/poky/build/tmp/work/apalis_imx6-poky-linux-gnueabi/angstrom-version/2_2.3.2-r12/image/usr/bin
install -m 0755 /home/rama/repositories/poky/build/tmp/work/apalis_imx6-poky-linux-gnueabi/angstrom-version/2_2.3.2-r12/lsb_release /home/rama/repositories/poky/build/tmp/work/apalis_imx6-poky-linux-gnueabi/angstrom-version/2_2.3.2-r12/image/usr/bin/
which triggered exception AttributeError: 'module' object has no attribute 'getVar'
I need to bitbake file and install it on my apalis imx6, do I need this meta-angstrom layer?
If I change the machine to qemux64 and I remove the toradex,fsl,angstrom layers, it starts to bitabke just fine! So its definitely a problem with those layers.
Any help is appreciated!
I am executing this on Ubuntu 14.04
EDIT: Switching to master branch on meta-angstrom I was able to solve the second, error however I still get the first error. Hope this helps somebody else.
EDIT: It seems the problem has recurred, no idea why still investigating
EDIT: When I bit bake I get stuff this like :
Loading cache: 100% |############################################################################################################################################| Time: 0:00:00
Loaded 158 entries from dependency cache.
NOTE: /home/rama/repositories/poky/meta-qt5/recipes-qt/qt5/qttools_git.bb: base_contains is deprecated, please use bb.utils.contains instead. | ETA: 0:00:16
NOTE: /home/rama/repositories/poky/meta-qt5/recipes-qt/qt5/qttools_git.bb: base_contains is deprecated, please use bb.utils.contains instead.
NOTE: /home/rama/repositories/poky/meta-qt5/recipes-qt/qt5/qtdeclarative_git.bb: base_contains is deprecated, please use bb.utils.contains instead.
NOTE: /home/rama/repositories/poky/meta-qt5/recipes-qt/qt5/qttools_git.bb: base_contains is deprecated, please use bb.utils.contains instead.
NOTE: /home/rama/repositories/poky/meta-qt5/recipes-qt/qt5/qttools_git.bb: base_contains is deprecated, please use bb.utils.contains instead.
No info on the layers.
My layers are all upto date, and I have switched them to master.
How else can I get layer info?
EDIT:
This is what I get from bitbake, no other information whatsoever
bitbake core-image-minimal
WARNING: Host distribution "ubuntu-14.04" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution.
NOTE: /home/rama/repositories/poky/meta-qt5/recipes-qt/qt5/qttools_git.bb: base_contains is deprecated, please use bb.utils.contains instead. | ETA: 0:00:16
NOTE: /home/rama/repositories/poky/meta-qt5/recipes-qt/qt5/qttools_git.bb: base_contains is deprecated, please use bb.utils.contains instead.
NOTE: /home/rama/repositories/poky/meta-qt5/recipes-qt/qt5/qtwebkit-examples_git.bb: base_contains is deprecated, please use bb.utils.contains instead.
NOTE: /home/rama/repositories/poky/meta-qt5/recipes-qt/qt5/qtwebkit-examples_git.bb: base_contains is deprecated, please use bb.utils.contains instead.
NOTE: /home/rama/repositories/poky/meta-qt5/recipes-qt/qt5/qttools_git.bb: base_contains is deprecated, please use bb.utils.contains instead.
NOTE: /home/rama/repositories/poky/meta-qt5/recipes-qt/qt5/qttools_git.bb: base_contains is deprecated, please use bb.utils.contains instead.
NOTE: /home/rama/repositories/poky/meta-qt5/recipes-qt/qt5/qttools_git.bb: base_contains is deprecated, please use bb.utils.contains instead. | ETA: 0:00:17
NOTE: /home/rama/repositories/poky/meta-qt5/recipes-qt/qt5/qttools_git.bb: base_contains is deprecated, please use bb.utils.contains instead.
EDIT : local.conf
MACHINE ?= "apalis-imx6"
MENDER_FEATURES_ENABLE_append = " mender-uboot"
DISTRO ?= "poky"
PACKAGE_CLASSES ?= "package_rpm"
#SDKMACHINE ?= "i686"
EXTRA_IMAGE_FEATURES ?= "debug-tweaks"
USER_CLASSES ?= "buildstats image-mklibs image-prelink"
PATCHRESOLVE = "noop"
BB_DISKMON_DIRS = "\
STOPTASKS,${TMPDIR},1G,100K \
STOPTASKS,${DL_DIR},1G,100K \
STOPTASKS,${SSTATE_DIR},1G,100K \
STOPTASKS,/tmp,100M,100K \
ABORT,${TMPDIR},100M,1K \
ABORT,${DL_DIR},100M,1K \
ABORT,${SSTATE_DIR},100M,1K \
ABORT,/tmp,10M,1K"
PACKAGECONFIG_append_pn-qemu-native = " sdl"
PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl"
MENDER_ARTIFACT_NAME = "demo-mender-artifact"
INHERIT += "mender-full"
INHERIT += "rm_work"
DISTRO_FEATURES_append = " systemd"
VIRTUAL-RUNTIME_init_manager = "systemd"
DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit"
VIRTUAL-RUNTIME_initscripts = ""
IMAGE_FSTYPES = "ext4"
bblayers.conf:
# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
POKY_BBLAYERS_CONF_VERSION = "2"
BBPATH = "${TOPDIR}"
BBFILES ?= ""
BBLAYERS ?= " \
/home/rama/repositories/poky/meta \
/home/rama/repositories/poky/meta-poky \
/home/rama/repositories/poky/meta-yocto-bsp \
/home/rama/repositories/meta-mender/meta-mender-core \
/home/rama/repositories/poky/meta-toradex \
/home/rama/repositories/poky/meta-fsl-arm \
/home/rama/repositories/poky/meta-fsl-arm-extra \
/home/rama/repositories/poky/meta-qt5 \
"
I remove meta-angstrom from the layers, it seems to give me some other errors as well.
Am I missing some layers?
I tried adding the meta-openembedded layers like meta-oe and so on, I got some errors like :
ERROR: ParseError at /home/rama/repositories/poky/meta-openembedded/meta-oe/recipes-support/maliit/maliit-plugins_git.bb:7: Could not inherit file classes/qt4x11.bbclass
so I removed it as well.
Your error:
ERROR: /home/rama/repositories/poky/meta-fsl-arm/recipes-fsl/images/fsl-image-mfgtool-initramfs.bb: No IMAGE_CMD defined for IMAGE_FSTYPES entry 'sdimg' - possibly invalid type name or missing support class
ERROR: Failed to parse recipe: /home/rama/repositories/poky/meta-fsl-arm/recipes-fsl/images/fsl-image-mfgtool-initramfs.bb
suggests that one of your layers aren't updated to pyro. Looking further at your issue, meta-fsl-arm is severely outdated! (No pyro branch etc). This layer has been replaces by meta-freescale.
You probably will have to take a closer look at eg meta-fsl-arm-extra too, to see if it's currently maintained and updated or not.
This is the reason I asked you about the exact branches and versions of each layer. There is no pyro branch for meta-fsl-arm!
Related
I'm trying run guix package install for following manifest:
(specifications->manifest
'("noguix-hugo" ;; A CUSTOM MODULE implemented in /module/root-1/site-lisp/nonguix-hugo.scm
"go"))
The custom module in the manifest is declared as follows:
(define-module (nonguix-hugo)
;; implementation detail
;; ....
)
And the installation command looks like:
guix package --load-path="/module/root1/site-lisp" \
--load-path="/module/root-2/site-lisp" \
--manifest="/path/to/manifest.scm" \
--profile="/path/to/profile"
The command fails with error message:
guix package: error: noguix-hugo: unknown package
However, building the noguix-hugo using guix build command works just fine
guix build --load-path="/module/root1/site-lisp" \
--load-path="/module/root-2/site-lisp" \
nonguix-package
# The command builds and outputs the module location as expected
# /gnu/store/7js349wb17371225njzll9gma8kmwf-nonguix-hugo-1.0
My question:
Why does Guix succeed to locate the module when building it,
but can't seem to locate it when specified in a manifest file.
I even tried adding a (use-modules (nonguix-hugo)) to the manifest and setting GUIX_PACKAGE_PATH as specified in[1], yet the install still fails.
References
[1] https://guix.gnu.org/manual/en/html_node/Package-Modules.html
Okay, turns out this was a typo in the manifest:
(specifications->manifest
'("noguix-hugo"
"go"))
which should be corrected to:
(specifications->manifest
'("nonguix-hugo" ;; <= this line
"go"))
Sheesh!....
I created new question, because I felt the previous one had been answered and this belongs in a new place.
I run bitbake core-image-minimal and I get the following error:
ERROR: systemd-1_232-r0 do_patch: Command Error: 'quilt --quiltrc /home/rama/repositories/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/systemd/1_232-r0/recipe-sysroot-native/etc/quiltrc push' exited with 0 Output:
Applying patch 0001-systemd-udevd.service.in-set-MountFlags-shared.patch
patching file units/systemd-udevd.service.in
Hunk #1 FAILED at 21.
1 out of 1 hunk FAILED -- rejects in file units/systemd-udevd.service.in
Patch 0001-systemd-udevd.service.in-set-MountFlags-shared.patch does not apply (enforce with -f)
ERROR: systemd-1_232-r0 do_patch: Function failed: patch_do_patch
ERROR: Logfile of failure stored in: /home/rama/repositories/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/systemd/1_232-r0/temp/log.do_patch.5314
ERROR: Task (/home/rama/repositories/poky/meta/recipes-core/systemd/systemd_232.bb:do_patch) failed with exit code '1'
I located the place where the patch is written in file meta-toradex/recipes-core/systemd/systemd_%.bbappend :
FILESEXTRAPATHS_prepend := "${THISDIR}/systemd:"
SRC_URI += " \
file://rndis.network \
file://0001-systemd-udevd.service.in-set-MountFlags-shared.patch \
"
PACKAGECONFIG_append = " networkd"
do_install_append() {
# The network files need to be in /usr/lib/systemd, not ${systemd_unitdir}...
install -d ${D}${prefix}/lib/systemd/network/
install -m 0644 ${WORKDIR}/rndis.network ${D}${prefix}/lib/systemd/network/
}
FILES_${PN} += " \
${nonarch_base_libdir}/systemd/network \
I was told that I can :
Remove the patch.
Apply it manually.
To remove the path, Should I just remove it from SRC_URI list?
How does one apply patch manually? I tried to google this, I did not quite get how this can be done.
Any help is appreciated, Thank you.
When looking at repo manifest, meta-toradex is not used, and in meta-toradex, it says oe-core BSP layer (obsolete). I think you're not using the right environment.
Nevertheless, if you want to check patch problem, you can use devshell with bitbake -c devshell systemd, then type quilt push in new console. You then need to analyze with patch fails to apply by looking at patch file and corresponding source code.
You should not modify existing layer, and create your own layer overriding recipes, but if you want to, you can indeed remove patch to SRC_URI, then use bitbake -c clean systemd; bitbake systemd and it should be OK.
In Toradex developer knowledge-base, if you are making a new environment, i think you need to look at V2.1 and Later Images section.
I installed Isabelle2015 and I ran Isabelle2015/Isabelle2015.
When I try of using the tptp_isabelle tool I got the following error:
$ ./isabelle tptp_isabelle 10 foo.tptp
Unknown logic "HOL-TPTP" -- no heap file found in:
/home/asr/.isabelle/Isabelle2015/heaps/polyml-5.5.2_x86-linux
/home/asr/src/isabelle/Isabelle2015/heaps/polyml-5.5.2_x86-linux
Do I need to set up something else?
You probably have to build the HOL-TPTP session:
isabelle build -b HOL-TPTP
In runCommand of MSDdeploy, we get following warning
Warning: The process 'C:\Windows\system32\cmd.exe' (command line '') exited with code '0x0'.
The command is
Package\OurProject.csproj.deploy.cmd
[some other options]
"-postSync:runCommand='powershell -inputformat none c:\AfterDeploy.ps1'"
You have to add parameter successReturnCodes, e.g. successReturnCodes=0.
e.g.
Package\OurProject.csproj.deploy.cmd
[some other options]
"-postSync:runCommand='powershell -inputformat none c:\AfterDeploy.ps1',successReturnCodes=0"
See Web Deploy runCommand Provider
I am trying to develop a plugin to frama-c.
I did build the application, which has several files, and then created the makefile referencing all the files i needed.
I am able to use make and then make install and execute the plugin. My problem appears when i call functions from the ocamlyices library in a function...
I am still able to do the make and make install and when i try to execute i get the following error:
[kernel] warning: cannot load plug-in 'name' (incompatible with Fluorine-20130601).
[kernel] user error: option `<name>' is unknown.
use `frama-c -help' for more information.
[kernel] Frama-C aborted: invalid user input.
So it says it is incompatible when I add the call to ocamlyices functions. Is there any option/configuration I am missing somewhere?
Thank you for your help.
The final solution looked like this:
FRAMAC_SHARE := $(shell frama-c.byte -print-path)
FRAMAC_LIBDIR := $(shell frama-c.byte -print-libpath)
PLUGIN_NAME = Fact
# All needed files
PLUGIN_CMO = ../base/basic_types concolic_search run_fact ../lib/lib
PLUGIN_DOCFLAGS = -I ../base -I ../lib -I $(YICES) -I /usr/lib/ocaml/batteries -I ../instrumentation
PLUGIN_BFLAGS = -I ../base -I ../lib -I $(YICES) -I ../instrumentation
PLUGIN_OFLAGS = -I ../base -I ../lib -I $(YICES) -I ../instrumentation
PLUGIN_EXTRA_BYTE = $(YICES)/ocamlyices.cma
PLUGIN_EXTRA_OPT = $(YICES)/ocamlyices.cmxa
include $(FRAMAC_SHARE)/Makefile.dynamic
The variable $(YICES) is defined as
export YICES="/usr/local/lib/ocaml/3.12.1/ocamlyices"
As mentioned by Anne, if your plug-in uses an external library that is not already included by Frama-C itself, you need a few more steps than for a basic plug-in, especially setting PLUGIN_EXTRA_BYTE and PLUGIN_EXTRA_OPT to the external libraries that you want to be linked to your plug-in. It might also be necessary to adapt the flags passed to the linker with PLUGIN_LINK_BFLAGS and PLUGIN_LINK_OFLAGS, but this is heavily dependent on ocamlyices itself. More information on the variables that can be used to customize the compilation of your plug-in can be found in section 5.3.3 of Frama-C's development guide.