Git Product home page Git Product logo

intel-iot-refkit's Introduction

DISCONTINUATION OF PROJECT.

This project will no longer be maintained by Intel.

Intel has ceased development and contributions including, but not limited to, maintenance, bug fixes, new releases, or updates, to this project.

Intel no longer accepts patches to this project.

If you have an ongoing need to use this project, are interested in independently developing it, or would like to maintain patches for the open source software community, please create your own fork of this project.

intel-iot-refkit's People

Contributors

ashwinsoman avatar avalluri avatar dbkinder avatar epyeoh avatar ibarrajhumberto avatar ipuustin avatar jlaako avatar klihub avatar kraj avatar mythi avatar nvelux avatar okartau avatar pohly avatar rdower avatar tkatila avatar yinthong avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

intel-iot-refkit's Issues

Upstreaming `meta-refkit-core/recipes-extended/fwupd/fwupd` and related recipes to Yocto/OpenEmbedded

Hi all,

Created this issue to let you guys know that there are plan to move https://github.com/intel/intel-iot-refkit/blob/master/meta-refkit-core/recipes-extended/fwupd/fwupd_0.9.7.bb to upstream Yocto/OpenEmbedded.

I am just wondering if there are people at Intel or the OpenSouce that is interested in this effort and would help out. If not, I'll slowly upstream it when I get the chance.

Some discussion in OpenBMC: https://gerrit.openbmc-project.xyz/c/openbmc/openbmc/+/48513
fwupd Recipe Question: fwupd/fwupd#3938

Building locally using docker is not working

Hi, I'm trying the docker build but I am running this instruction docker/local-build.sh and it's not working.

my log:

root@SSID-iLBPG3:/home/ilab/work/intel-iot-refkit# docker/local-build.sh
unable to prepare context: unable to evaluate symlinks in context path: lstat /root/work/intel-iot-refkit/docker: no such file or directory
Unable to find image 'refkit:latest' locally
docker: Error response from daemon: repository refkit not found: does not exist or no pull access.
See 'docker run --help'.

Any ideas?

choosing image to build from docker

Sorry for the double posting but since it's a different issue I didn't want to mix them up.

I'm new in docker and I'm trying to choose which image the docker build should build. Where do I change the settings for the docker build to only build refkit-image-gateway and not build everything?

Also, inside the doc mentioned that we could play with the refkit-image-<profilename>-test. However, I do not see it built after running the docker inside my file listing ~/intel-iot-refkit/build/tmp-glibc/deploy/images/intel-quark. Is there a way I can change the docker build to also build the refkit-image-<profilename>-test?

My file listing inside ~/intel-iot-refkit/build/tmp-glibc/deploy/images/intel-quark

bzImage
bzImage--4.9.6+git0+6fd9dcbb3f_a0ddfd76aa-r0-intel-quark-20170225172115.bin
bzImage-intel-quark.bin
linuxia32.efi.stub
microcode_20160714.cpio
microcode.cpio
modules--4.9.6+git0+6fd9dcbb3f_a0ddfd76aa-r0-intel-quark-20170225172115.tgz
modules-intel-quark.tgz
README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt
refkit-image-common-intel-quark-2017-02-26_01-20-31-build-5.qemuboot.conf
refkit-image-common-intel-quark-2017-02-26_01-20-31-build-5.rootfs.manifest
refkit-image-common-intel-quark-2017-02-26_01-20-31-build-5.testdata.json
refkit-image-common-intel-quark-2017-02-26_01-20-31-build-5-uefiapp
refkit-image-common-intel-quark-2017-02-26_01-20-31-build-5.wic
refkit-image-common-intel-quark-2017-02-26_01-20-31-build-5.wic.bmap
refkit-image-common-intel-quark-2017-02-26_01-20-31-build-5.wic.xz
refkit-image-common-intel-quark-2017-02-26_01-20-31-build-5.wic.zip
refkit-image-common-intel-quark.manifest
refkit-image-common-intel-quark.qemuboot.conf
refkit-image-common-intel-quark.testdata.json
refkit-image-common-intel-quark.wic
refkit-image-common-intel-quark.wic.bmap
refkit-image-common-intel-quark.wic.xz
refkit-image-common-intel-quark.wic.zip
refkit-image-computervision-intel-quark-2017-02-26_01-20-31-build-5.qemuboot.conf
refkit-image-computervision-intel-quark-2017-02-26_01-20-31-build-5.rootfs.manifest
refkit-image-computervision-intel-quark-2017-02-26_01-20-31-build-5.testdata.json
refkit-image-computervision-intel-quark-2017-02-26_01-20-31-build-5-uefiapp
refkit-image-computervision-intel-quark-2017-02-26_01-20-31-build-5.wic
refkit-image-computervision-intel-quark-2017-02-26_01-20-31-build-5.wic.bmap
refkit-image-computervision-intel-quark-2017-02-26_01-20-31-build-5.wic.xz
refkit-image-computervision-intel-quark-2017-02-26_01-20-31-build-5.wic.zip
refkit-image-computervision-intel-quark.manifest
refkit-image-computervision-intel-quark.qemuboot.conf
refkit-image-computervision-intel-quark.testdata.json
refkit-image-computervision-intel-quark.wic
refkit-image-computervision-intel-quark.wic.bmap
refkit-image-computervision-intel-quark.wic.xz
refkit-image-computervision-intel-quark.wic.zip
refkit-image-gateway-intel-quark-2017-02-26_01-20-31-build-5.qemuboot.conf
refkit-image-gateway-intel-quark-2017-02-26_01-20-31-build-5.rootfs.manifest
refkit-image-gateway-intel-quark-2017-02-26_01-20-31-build-5.testdata.json
refkit-image-gateway-intel-quark-2017-02-26_01-20-31-build-5-uefiapp
refkit-image-gateway-intel-quark-2017-02-26_01-20-31-build-5.wic
refkit-image-gateway-intel-quark-2017-02-26_01-20-31-build-5.wic.bmap
refkit-image-gateway-intel-quark-2017-02-26_01-20-31-build-5.wic.xz
refkit-image-gateway-intel-quark-2017-02-26_01-20-31-build-5.wic.zip
refkit-image-gateway-intel-quark.manifest
refkit-image-gateway-intel-quark.qemuboot.conf
refkit-image-gateway-intel-quark.testdata.json
refkit-image-gateway-intel-quark.wic
refkit-image-gateway-intel-quark.wic.bmap
refkit-image-gateway-intel-quark.wic.xz
refkit-image-gateway-intel-quark.wic.zip
refkit-image-minimal-intel-quark-2017-02-26_01-20-31-build-5.qemuboot.conf
refkit-image-minimal-intel-quark-2017-02-26_01-20-31-build-5.rootfs.manifest
refkit-image-minimal-intel-quark-2017-02-26_01-20-31-build-5.testdata.json
refkit-image-minimal-intel-quark-2017-02-26_01-20-31-build-5-uefiapp
refkit-image-minimal-intel-quark.manifest
refkit-image-minimal-intel-quark.qemuboot.conf
refkit-image-minimal-intel-quark.testdata.json
refkit-initramfs-intel-quark-20170225172115.qemuboot.conf
refkit-initramfs-intel-quark-20170225172115.rootfs.cpio.gz
refkit-initramfs-intel-quark-20170225172115.rootfs.manifest
refkit-initramfs-intel-quark-20170225172115.testdata.json
refkit-initramfs-intel-quark.cpio.gz
refkit-initramfs-intel-quark.manifest
refkit-initramfs-intel-quark.qemuboot.conf
refkit-initramfs-intel-quark.testdata.json
rmc.db

Variables not set by default but still used

a distro cannot use meta-refkit as a layer because a number of variables aren't being set because they rely on a specific local.conf (or include from local.conf)

REFKIT_DMVERITY_PRIVATE_KEY

Full error:

ERROR: /path/../meta-refkit/recipes-image/images/initramfs-framework-refkit-dm-verity.bb: REFKIT_DMVERITY_PRIVATE_KEY is not set.
ERROR: ExpansionError during parsing /path/intel-iot-refkit/openembedded-core/../meta-refkit/recipes-image/images/refkit-image-gateway.bb

REFKIT_USE_DSK_IMAGES

ERROR: ExpansionError during parsing /path/meta-refkit/recipes-image/images/refkit-image-gateway.bb
Traceback (most recent call last):
bb.data_smart.ExpansionError: Failure expanding variable IMAGE_CLASSES, expression was qemuboot qemuboot ${@ 'image-dsk' if ${REFKIT_USE_DSK_IMAGES} else ''} image_types which triggered exception SyntaxError: invalid syntax (IMAGE_CLASSES, line 1)

fetch failure for pkg-config 0.29.2

There is fetch failure with 0.29.2. I tried going back, temporarily, to 0.29.1 and it works there with below change revert for time being.

 LICENSE = "GPLv2+"
 LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"

-SRCREV = "edf8e6f0ea77ede073f07bff0d2ae1fc7a38103b"
-PV = "0.29.2+git${SRCPV}"
+SRCREV = "87152c05be88ca8be71a3a563f275b3686d32c28"
+PV = "0.29.1+git${SRCPV}"

 SRC_URI = "git://anongit.freedesktop.org/pkg-config \
            file://pkg-config-native.in \
            file://fix-glib-configure-libtool-usage.patch \
+           file://0001-gdate-Move-warning-pragma-outside-of-function.patch \
            file://0001-glib-gettext.m4-Update-AM_GLIB_GNU_GETTEXT-to-match-.patch \

Nftables ruleset does not match valid MLD packets

Hi,

from my experiments with nftables (https://ao2.it/134) it looks like the rule used in this project for MLD packets is not enough to match valid MLD packets, I am referring to:

The problem is that for valid MLD packets the next header after the IPv6 one is not immediately the ICMPv6 one but the Hop-by-Hop Options header, so the rule you are using:

        # Allow multicast listener discovery on link-local addresses.
        ip6 nexthdr icmpv6 icmpv6 type {{
                mld-listener-query,
                ...

Should probably become something like:

        # Allow multicast listener discovery on link-local addresses.
        ip6 nexthdr hopopt hbh nexthdr ipv6-icmp icmpv6 type {{
                mld-listener-query,
                ...

See also the referenced blog post for more details.

I only tested this in a limited environment so I'd like some confirmation that this is actually an issue.

Ciao,
Antonio

Fail to build refkit image with docker

Tried to build refkit image with docker per README.rst, and run into below error. What am I missing? Any pointer would be appreciated. Thanks.

[tzeng@ttzeng-desktop:/Workspace/yocto/ref-os-iot/intel-iot-refkit]
$ git rev-parse HEAD
90c6298
[tzeng@ttzeng-desktop:
/Workspace/yocto/ref-os-iot/intel-iot-refkit]
$ docker/local-build.sh refkit-image-common
unable to prepare context: unable to evaluate symlinks in context path: lstat /home/tzeng/Workspace/yocto/refkit-intel-corei7-64/docker: no such file or directory
Unable to find image 'refkit:latest' locally
Pulling repository docker.io/library/refkit
docker: Error: image library/refkit:latest not found.
See 'docker run --help'.

Boot failed on Joule

Hi,

I'm trying to build and install the image on Joule board. Following the build and install instructions, I can boot the Joule, but always stay at

random: crng init done

I built without docker (develop build with default local.conf) and use dd to create a bootable usb. During the booting process, no error is reported. Does anyone know what's the problem here?

Thanks in advance!

No npm in gateway image

I'm using the latest RefKit gateway image with the IoT to Cloud Smart Home demo. Good news is: I'm able to run the IoT REST API service fine with the stock image configuration. Good work guys ๐Ÿ‘

What I would like to do is run the "cloud side" docker app to access the REST API. Unfortunately the requirements to install the binary version of Docker on RefKit aren't met. According to the Docker documentation a few packages are missing in the image:

https://docs.docker.com/engine/installation/binaries/#install-daemon-and-client-binaries-on-linux

What do you think about generating one dev image that can be used to modify and debug code on target regardless of the RefKit profile that is being used? Such an image should contain Autotools, compiler, git, all editors for Linux and header files for all packages, etc. Yes, the image would be rather large, but installing a large image installed once still beats the task to generate image(s) for the purpose of on-target development by far :-)

mraa doesn't compile python3 bindings.

because recipe inherits "distutils-base" instead of "distutils3-base", only python2 bindings are created.
mraa supports building for both python2 and 3, but recipe doesn't support it.

How to deploy refkit-image-gateway into Galileo Gen 2

Hi guys, I'm been trying to boot the Galileo Gen 2 with the refkit-image-gateway but I'm not too sure how to go about it.

So I've successfully compiled the intel-quark image by changing the settings from docker/local-build.sh

#TARGET_MACHINE="intel-corei7-64"
TARGET_MACHINE="intel-quark"

And I ended up with a bunch of files inside ~/intel-iot-refkit/build/tmp-glibc/deploy/images/intel-quark

bzImage
bzImage--4.9.6+git0+6fd9dcbb3f_a0ddfd76aa-r0-intel-quark-20170225172115.bin
bzImage-intel-quark.bin
linuxia32.efi.stub
microcode_20160714.cpio
microcode.cpio
modules--4.9.6+git0+6fd9dcbb3f_a0ddfd76aa-r0-intel-quark-20170225172115.tgz
modules-intel-quark.tgz
README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt
refkit-image-common-intel-quark-2017-02-26_01-20-31-build-5.qemuboot.conf
refkit-image-common-intel-quark-2017-02-26_01-20-31-build-5.rootfs.manifest
refkit-image-common-intel-quark-2017-02-26_01-20-31-build-5.testdata.json
refkit-image-common-intel-quark-2017-02-26_01-20-31-build-5-uefiapp
refkit-image-common-intel-quark-2017-02-26_01-20-31-build-5.wic
refkit-image-common-intel-quark-2017-02-26_01-20-31-build-5.wic.bmap
refkit-image-common-intel-quark-2017-02-26_01-20-31-build-5.wic.xz
refkit-image-common-intel-quark-2017-02-26_01-20-31-build-5.wic.zip
refkit-image-common-intel-quark.manifest
refkit-image-common-intel-quark.qemuboot.conf
refkit-image-common-intel-quark.testdata.json
refkit-image-common-intel-quark.wic
refkit-image-common-intel-quark.wic.bmap
refkit-image-common-intel-quark.wic.xz
refkit-image-common-intel-quark.wic.zip
refkit-image-computervision-intel-quark-2017-02-26_01-20-31-build-5.qemuboot.conf
refkit-image-computervision-intel-quark-2017-02-26_01-20-31-build-5.rootfs.manifest
refkit-image-computervision-intel-quark-2017-02-26_01-20-31-build-5.testdata.json
refkit-image-computervision-intel-quark-2017-02-26_01-20-31-build-5-uefiapp
refkit-image-computervision-intel-quark-2017-02-26_01-20-31-build-5.wic
refkit-image-computervision-intel-quark-2017-02-26_01-20-31-build-5.wic.bmap
refkit-image-computervision-intel-quark-2017-02-26_01-20-31-build-5.wic.xz
refkit-image-computervision-intel-quark-2017-02-26_01-20-31-build-5.wic.zip
refkit-image-computervision-intel-quark.manifest
refkit-image-computervision-intel-quark.qemuboot.conf
refkit-image-computervision-intel-quark.testdata.json
refkit-image-computervision-intel-quark.wic
refkit-image-computervision-intel-quark.wic.bmap
refkit-image-computervision-intel-quark.wic.xz
refkit-image-computervision-intel-quark.wic.zip
refkit-image-gateway-intel-quark-2017-02-26_01-20-31-build-5.qemuboot.conf
refkit-image-gateway-intel-quark-2017-02-26_01-20-31-build-5.rootfs.manifest
refkit-image-gateway-intel-quark-2017-02-26_01-20-31-build-5.testdata.json
refkit-image-gateway-intel-quark-2017-02-26_01-20-31-build-5-uefiapp
refkit-image-gateway-intel-quark-2017-02-26_01-20-31-build-5.wic
refkit-image-gateway-intel-quark-2017-02-26_01-20-31-build-5.wic.bmap
refkit-image-gateway-intel-quark-2017-02-26_01-20-31-build-5.wic.xz
refkit-image-gateway-intel-quark-2017-02-26_01-20-31-build-5.wic.zip
refkit-image-gateway-intel-quark.manifest
refkit-image-gateway-intel-quark.qemuboot.conf
refkit-image-gateway-intel-quark.testdata.json
refkit-image-gateway-intel-quark.wic
refkit-image-gateway-intel-quark.wic.bmap
refkit-image-gateway-intel-quark.wic.xz
refkit-image-gateway-intel-quark.wic.zip
refkit-image-minimal-intel-quark-2017-02-26_01-20-31-build-5.qemuboot.conf
refkit-image-minimal-intel-quark-2017-02-26_01-20-31-build-5.rootfs.manifest
refkit-image-minimal-intel-quark-2017-02-26_01-20-31-build-5.testdata.json
refkit-image-minimal-intel-quark-2017-02-26_01-20-31-build-5-uefiapp
refkit-image-minimal-intel-quark.manifest
refkit-image-minimal-intel-quark.qemuboot.conf
refkit-image-minimal-intel-quark.testdata.json
refkit-initramfs-intel-quark-20170225172115.qemuboot.conf
refkit-initramfs-intel-quark-20170225172115.rootfs.cpio.gz
refkit-initramfs-intel-quark-20170225172115.rootfs.manifest
refkit-initramfs-intel-quark-20170225172115.testdata.json
refkit-initramfs-intel-quark.cpio.gz
refkit-initramfs-intel-quark.manifest
refkit-initramfs-intel-quark.qemuboot.conf
refkit-initramfs-intel-quark.testdata.json
rmc.db

I'm now trying to play around with the refkit-image-gateway-intel-quark.wic by following the tutorial steps from doc/how-tos/Image-install.rst however, after I have dd into the sd card and tried booting the Galileo Gen 2 nothing happens.

I realized that the files inside the sd card is also different from the usual Galileo's files that I used to bitbake from Yocto. Previously whenever I bitbaked Galileo I would get these files:

image-full-quark.ext3
core-image-minimal-initramfs-quark.cpio.gz
bzImage
grub.efi
boot (directory)

However from .wic I got these:

EFI (directory)
EFI_internal_storage (directory)
rmc.db
emmc-partitions-data

I tried adding these files given from ~/intel-iot-refkit/build/tmp-glibc/deploy/images/intel-quark in as well but doesn't work:

bzImage*
linuxia32.efi.stub*
microcode.cpio
modules-intel-quark.tgz
refkit-image-gateway-intel-quark.bmap
refkit-image-gateway-intel-quark.manifest
refkit-initramfs-intel-quark.cpio.gz
rmc.db
systemd-bootia32.efi*

Any pointers or advice that could help with this?

Compile issue

Hello Guys,

I tried to use your recipe and endup with compilation error

NOTE: Executing RunQueue Tasks
ERROR: openblas-0.2.19-r0 do_compile: oe_runmake failed
ERROR: openblas-0.2.19-r0 do_compile: Function failed: do_compile (log file is located at ../build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/openblas/0.2.19-r0/temp/log.do_compile.2836)
ERROR: Logfile of failure stored in: ../build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/openblas/0.2.19-r0/temp/log.do_compile.2836
Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: make -j 4 HOSTCC=gcc  CC=arm-poky-linux-gnueabi-gcc  --sysroot=../build/tmp/sysroots/ ONLY_CBLAS=1 BINARY=32 TARGET=arm
| make[1]: warning: -jN forced in submake: disabling jobserver mode.
| make[1]: Entering directory '../build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/openblas/0.2.19-r0/OpenBLAS-0.2.19/interface'
| arm-poky-linux-gnueabi-gcc  --sysroot=../build/tmp/sysroots/  -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=../build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/openblas/0.2.19-r0=/usr/src/debug/openblas/0.2.19-r0 -fdebug-prefix-map=../build/tmp/sysroots/x86_64-linux= -fdebug-prefix-map=../build/tmp/sysroots/=  -O2 -DMAX_STACK_ALLOC=2048 -Wall -DF_INTERFACE_GFORT -fPIC -DNO_LAPACK -DNO_LAPACKE -DSMP_SERVER -DNO_WARMUP -DMAX_CPU_NUMBER=4 -DASMNAME= -DASMFNAME=_ -DNAME=_ -DCNAME= -DCHAR_NAME=\"_\" -DCHAR_CNAME=\"\" -DNO_AFFINITY -I. -O2 -DMAX_STACK_ALLOC=2048 -Wall -DF_INTERFACE_GFORT -fPIC -DNO_LAPACK -DNO_LAPACKE -DSMP_SERVER -DNO_WARMUP -DMAX_CPU_NUMBER=4 -DASMNAME=cblas_isamax -DASMFNAME=cblas_isamax_ -DNAME=cblas_isamax_ -DCNAME=cblas_isamax -DCHAR_NAME=\"cblas_isamax_\" -DCHAR_CNAME=\"cblas_isamax\" -DNO_AFFINITY -I.. -I. -UDOUBLE  -UCOMPLEX -DCBLAS -c -DUSE_ABS -UUSE_MIN imax.c -o cblas_isamax.o
| arm-poky-linux-gnueabi-gcc  --sysroot=../build/tmp/sysroots/  -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=../build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/openblas/0.2.19-r0=/usr/src/debug/openblas/0.2.19-r0 -fdebug-prefix-map=../build/tmp/sysroots/x86_64-linux= -fdebug-prefix-map=../build/tmp/sysroots/=  -O2 -DMAX_STACK_ALLOC=2048 -Wall -DF_INTERFACE_GFORT -fPIC -DNO_LAPACK -DNO_LAPACKE -DSMP_SERVER -DNO_WARMUP -DMAX_CPU_NUMBER=4 -DASMNAME= -DASMFNAME=_ -DNAME=_ -DCNAME= -DCHAR_NAME=\"_\" -DCHAR_CNAME=\"\" -DNO_AFFINITY -I. -O2 -DMAX_STACK_ALLOC=2048 -Wall -DF_INTERFACE_GFORT -fPIC -DNO_LAPACK -DNO_LAPACKE -DSMP_SERVER -DNO_WARMUP -DMAX_CPU_NUMBER=4 -DASMNAME=cblas_sasum -DASMFNAME=cblas_sasum_ -DNAME=cblas_sasum_ -DCNAME=cblas_sasum -DCHAR_NAME=\"cblas_sasum_\" -DCHAR_CNAME=\"cblas_sasum\" -DNO_AFFINITY -I.. -I. -UDOUBLE  -UCOMPLEX -DCBLAS -c asum.c -o cblas_sasum.o
| arm-poky-linux-gnueabi-gcc  --sysroot=../build/tmp/sysroots/  -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=../build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/openblas/0.2.19-r0=/usr/src/debug/openblas/0.2.19-r0 -fdebug-prefix-map=../build/tmp/sysroots/x86_64-linux= -fdebug-prefix-map=../build/tmp/sysroots/=  -O2 -DMAX_STACK_ALLOC=2048 -Wall -DF_INTERFACE_GFORT -fPIC -DNO_LAPACK -DNO_LAPACKE -DSMP_SERVER -DNO_WARMUP -DMAX_CPU_NUMBER=4 -DASMNAME= -DASMFNAME=_ -DNAME=_ -DCNAME= -DCHAR_NAME=\"_\" -DCHAR_CNAME=\"\" -DNO_AFFINITY -I. -O2 -DMAX_STACK_ALLOC=2048 -Wall -DF_INTERFACE_GFORT -fPIC -DNO_LAPACK -DNO_LAPACKE -DSMP_SERVER -DNO_WARMUP -DMAX_CPU_NUMBER=4 -DASMNAME=cblas_saxpy -DASMFNAME=cblas_saxpy_ -DNAME=cblas_saxpy_ -DCNAME=cblas_saxpy -DCHAR_NAME=\"cblas_saxpy_\" -DCHAR_CNAME=\"cblas_saxpy\" -DNO_AFFINITY -I.. -I. -UDOUBLE  -UCOMPLEX -DCBLAS -c axpy.c -o cblas_saxpy.o
| arm-poky-linux-gnueabi-gcc  --sysroot=../build/tmp/sysroots/  -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=../build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/openblas/0.2.19-r0=/usr/src/debug/openblas/0.2.19-r0 -fdebug-prefix-map=../build/tmp/sysroots/x86_64-linux= -fdebug-prefix-map=../build/tmp/sysroots/=  -O2 -DMAX_STACK_ALLOC=2048 -Wall -DF_INTERFACE_GFORT -fPIC -DNO_LAPACK -DNO_LAPACKE -DSMP_SERVER -DNO_WARMUP -DMAX_CPU_NUMBER=4 -DASMNAME= -DASMFNAME=_ -DNAME=_ -DCNAME= -DCHAR_NAME=\"_\" -DCHAR_CNAME=\"\" -DNO_AFFINITY -I. -O2 -DMAX_STACK_ALLOC=2048 -Wall -DF_INTERFACE_GFORT -fPIC -DNO_LAPACK -DNO_LAPACKE -DSMP_SERVER -DNO_WARMUP -DMAX_CPU_NUMBER=4 -DASMNAME=cblas_scopy -DASMFNAME=cblas_scopy_ -DNAME=cblas_scopy_ -DCNAME=cblas_scopy -DCHAR_NAME=\"cblas_scopy_\" -DCHAR_CNAME=\"cblas_scopy\" -DNO_AFFINITY -I.. -I. -UDOUBLE  -UCOMPLEX -DCBLAS -c copy.c -o cblas_scopy.o
| <command-line>:0:0: warning: "ASMNAME" redefined
| <command-line>:0:0: warning: "ASMNAME" redefined
| <command-line>:0:0: note: this is the location of the previous definition
| <command-line>:0:0: warning: "ASMFNAME" redefined
| <command-line>:0:0: note: this is the location of the previous definition
| <command-line>:0:0: warning: "NAME" redefined
| <command-line>:0:0: note: this is the location of the previous definition
| <command-line>:0:0: warning: "CNAME" redefined
| <command-line>:0:0: note: this is the location of the previous definition
| <command-line>:0:0: warning: "CHAR_NAME" redefined
| <command-line>:0:0: note: this is the location of the previous definition
| <command-line>:0:0: warning: "CHAR_CNAME" redefined
| <command-line>:0:0: note: this is the location of the previous definition
| <command-line>:0:0: warning: "ASMNAME" redefined
| <command-line>:0:0: note: this is the location of the previous definition
| <command-line>:0:0: warning: "ASMFNAME" redefined
| <command-line>:0:0: note: this is the location of the previous definition
| <command-line>:0:0: warning: "NAME" redefined
| In file included from ../build/tmp/sysroots//usr/include/features.h:392:0,
|                  from ../build/tmp/sysroots//usr/include/stdio.h:27,
|                  from imax.c:39:
| ../build/tmp/sysroots//usr/include/gnu/stubs.h:7:29: fatal error: gnu/stubs-soft.h: No such file or directory
|  # include <gnu/stubs-soft.h>
|                              ^
| compilation terminated.
| <command-line>:0:0: note: this is the location of the previous definition
| <command-line>:0:0: warning: "CNAME" redefined
| <command-line>:0:0: note: this is the location of the previous definition
| <command-line>:0:0: warning: "CHAR_NAME" redefined
| <command-line>:0:0: note: this is the location of the previous definition
| <command-line>:0:0: warning: "CHAR_CNAME" redefined
| <command-line>:0:0: note: this is the location of the previous definition
| <command-line>:0:0: note: this is the location of the previous definition
| <command-line>:0:0: warning: "ASMFNAME" redefined
| <command-line>:0:0: note: this is the location of the previous definition
| <command-line>:0:0: warning: "NAME" redefined
| <command-line>:0:0: note: this is the location of the previous definition
| <command-line>:0:0: warning: "CNAME" redefined
| <command-line>:0:0: note: this is the location of the previous definition
| <command-line>:0:0: warning: "CHAR_NAME" redefined
| <command-line>:0:0: note: this is the location of the previous definition
| <command-line>:0:0: warning: "CHAR_CNAME" redefined
| <command-line>:0:0: note: this is the location of the previous definition
| <command-line>:0:0: warning: "ASMNAME" redefined
| <command-line>:0:0: note: this is the location of the previous definition
| <command-line>:0:0: warning: "ASMFNAME" redefined
| <command-line>:0:0: note: this is the location of the previous definition
| <command-line>:0:0: warning: "NAME" redefined
| <command-line>:0:0: note: this is the location of the previous definition
| <command-line>:0:0: warning: "CNAME" redefined
| <command-line>:0:0: note: this is the location of the previous definition
| <command-line>:0:0: warning: "CHAR_NAME" redefined
| In file included from ../build/tmp/sysroots//usr/include/features.h:392:0,
|                  from ../build/tmp/sysroots//usr/include/stdio.h:27,
|                  from axpy.c:39:
| ../build/tmp/sysroots//usr/include/gnu/stubs.h:7:29: fatal error: gnu/stubs-soft.h: No such file or directory
|  # include <gnu/stubs-soft.h>
|                              ^
| <command-line>:0:0: note: this is the location of the previous definition
| <command-line>:0:0: warning: "CHAR_CNAME" redefined
| <command-line>:0:0: note: this is the location of the previous definition
| ERROR: oe_runmake failed
| In file included from ../build/tmp/sysroots//usr/include/features.h:392:0,
|                  from ../build/tmp/sysroots//usr/include/stdio.h:27,
|                  from asum.c:39:
| ../build/tmp/sysroots//usr/include/gnu/stubs.h:7:29: fatal error: gnu/stubs-soft.h: No such file or directory
|  # include <gnu/stubs-soft.h>
|                              ^
| compilation terminated.
| In file included from ../build/tmp/sysroots//usr/include/features.h:392:0,
|                  from ../build/tmp/sysroots//usr/include/stdio.h:27,
|                  from copy.c:39:
| ../build/tmp/sysroots//usr/include/gnu/stubs.h:7:29: fatal error: gnu/stubs-soft.h: No such file or directory
|  # include <gnu/stubs-soft.h>
|                              ^
| compilation terminated.
| compilation terminated.
| Makefile:1351: recipe for target 'cblas_isamax.o' failed
| make[1]: *** [cblas_isamax.o] Error 1
| make[1]: *** Waiting for unfinished jobs....
| Makefile:1375: recipe for target 'cblas_sasum.o' failed
| make[1]: *** [cblas_sasum.o] Error 1
| Makefile:1447: recipe for target 'cblas_scopy.o' failed
| make[1]: *** [cblas_scopy.o] Error 1
| Makefile:1435: recipe for target 'cblas_saxpy.o' failed
| make[1]: *** [cblas_saxpy.o] Error 1
| make[1]: Leaving directory '../build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/openblas/0.2.19-r0/OpenBLAS-0.2.19/interface'
| Makefile:133: recipe for target 'libs' failed
| make: *** [libs] Error 1
| ERROR: Function failed: do_compile (log file is located at ../build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/openblas/0.2.19-r0/temp/log.do_compile.2836)
ERROR: Task (../sources/meta-fsl-bsp-release/imx/meta-bsp/recipes-graphics/openblas/openblas_0.2.19.bb:do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 433 tasks of which 432 didn't need to be rerun and 1 failed.


Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.