From: "Denys Dmytriyenko" <denys@ti.com>
To: Daniel Ammann <daniel.ammann@bytesatwork.ch>
Cc: <meta-ti@lists.yoctoproject.org>
Subject: Re: [meta-ti] am437x-evm zeus image
Date: Thu, 20 Feb 2020 13:55:52 -0500 [thread overview]
Message-ID: <20200220185552.GA22205@beryl> (raw)
In-Reply-To: <b7af4338-6409-457d-5bf4-173ebcb92b38@bytesatwork.ch>
On Thu, Feb 20, 2020 at 11:21:46AM +0100, Daniel Ammann wrote:
> Hi Denys
>
> Thanks for the answer.
>
> My build configuration looks like this:
>
> Build Configuration:
> BB_VERSION = "1.44.0"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING = "universal"
> TARGET_SYS = "arm-poky-linux-gnueabi"
Ah, "poky" toolchain, which doesn't use "gnueabihf" suffix... Probably need
the same hack as for the generic "oe" toolchain - I'll take a look.
> MACHINE = "am437x-evm"
> DISTRO = "poky"
> DISTRO_VERSION = "3.0.2"
> TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard"
> TARGET_FPU = "hard"
> meta
> meta-poky
> meta-yocto-bsp = "zeus:5e1f52edb7a9f790fb6cb5d96502f3690267c1b1"
> meta-oe
> meta-networking
> meta-python = "zeus:bb65c27a772723dfe2c15b5e1b27bcc1a1ed884c"
> meta-ti = "zeus:19a73c96bd05a74711a36a61077e8a7b88b55c63"
>
> See below for the error messgage.
>
> Thanks and kind regards
>
> Daniel
>
>
> ERROR: ti-sgx-ddk-km-1.17.4948957-r3v do_compile: oe_runmake failed
> ERROR: ti-sgx-ddk-km-1.17.4948957-r3v do_compile: Execution of '/home/daniel/workspace/reference/am335x-evm-poky/build/tmp/work/am437x_evm-poky-linux-gnueabi/ti-sgx-ddk-km/1.17.4948957-r3v/temp/run.do_compile.19460' failed with exit code 1:
> grep: /home/daniel/workspace/reference/am335x-evm-poky/build/tmp/work-shared/am437x-evm/kernel-source/include/linux/amba: Is a directory
> grep: /home/daniel/workspace/reference/am335x-evm-poky/build/tmp/work-shared/am437x-evm/kernel-source/include/linux/avf: Is a directory
> grep: /home/daniel/workspace/reference/am335x-evm-poky/build/tmp/work-shared/am437x-evm/kernel-source/include/linux/bcma: Is a directory
> .
> .
> .
> grep: /home/daniel/workspace/reference/am335x-evm-poky/build/tmp/work-shared/am437x-evm/kernel-source/include/linux/unaligned: Is a directory
> grep: /home/daniel/workspace/reference/am335x-evm-poky/build/tmp/work-shared/am437x-evm/kernel-source/include/linux/usb: Is a directory
> grep: /home/daniel/workspace/reference/am335x-evm-poky/build/tmp/work-shared/am437x-evm/kernel-source/include/linux/wimax: Is a directory
> ../config/compiler.mk:96: host gcc
> ../config/compiler.mk:185: target arm-poky-linux-gnueabi-gcc -mno-thumb-interwork -marm -fuse-ld=bfd -fmacro-prefix-map=/home/daniel/workspace/reference/am335x-evm-poky/build/tmp/work/am437x_evm-poky-linux-gnueabi/ti-sgx-ddk-km/1.17.4948957-r3v=/usr/src/debug/ti-sgx-ddk-km/1.17.4948957-r3v -fdebug-prefix-map=/home/daniel/workspace/reference/am335x-evm-poky
> /build/tmp/work/am437x_evm-poky-linux-gnueabi/ti-sgx-ddk-km/1.17.4948957-r3v=/usr/src/debug/ti-sgx-ddk-km/1.17.4948957-r3v -fdebug-prefix-map=/home/daniel/workspace/reference/am335x-evm-poky/build/tmp/work/am437x_evm-poky-linux-gnueabi/ti-sgx-ddk-km/1.17.4948957-r3v/recipe-sysroot= -fdebug-prefix-map=/home/daniel/workspace/reference/am3
> 35x-evm-poky/build/tmp/work/am437x_evm-poky-linux-gnueabi/ti-sgx-ddk-km/1.17.4948957-r3v/recipe-sysroot-native= -fdebug-prefix-map=/home/daniel/workspace/reference/am335x-evm-poky/build/tmp/work-shared/am437x-evm/kernel-source=/usr/src/kernel
> ******* Multiarch build: no
> ******* Primary arch: target_armel
> ******* Secondary arch: none
> ../config/core.mk:513: $(KERNELDIR)/vmlinux does not exist. Kbuild may fail.
> eurasiacon/build/linux2/toplevel.mk:230: eurasiacon/build/linux2/moduledefs/target_armel.mk: No such file or directory
> make[1]: *** No rule to make target 'eurasiacon/build/linux2/moduledefs/target_armel.mk'. Stop.
> make: *** [../config/core.mk:789: build] Error 2
> WARNING: exit code 1 from a shell command.
>
> ERROR: Logfile of failure stored in: /home/daniel/workspace/reference/am335x-evm-poky/build/tmp/work/am437x_evm-poky-linux-gnueabi/ti-sgx-ddk-km/1.17.4948957-r3v/temp/log.do_compile.19460
>
>
>
> On 2/19/20 8:00 PM, Denys Dmytriyenko wrote:
> >Daniel,
> >
> >You are not providing any useful info, such as error messages or logs.
> >
> >In general, yes, am437x-evm on Zeus is ready and has been building fine in
> >many different configurations.
> >
> >Denys
> >
> >
> >On Wed, Feb 19, 2020 at 11:27:55AM +0100, Daniel Ammann wrote:
> >>Hi all
> >>
> >>I'm trying to build a zeus image for am437x-evm. How do I go about that? Is
> >>meta-ti branch zeus ready yet?
> >>
> >>First, I tried a simple poky build with meta-openembedded and meta-ti, building
> >>core-image-base. But compiling of ti-sgx-ddk-km fails.
> >>
> >>Then I followed the instructions in the arago wiki [1], but the build fails
> >>with qtbase because qtbase doesn't run configure successfully.
> >>
> >>What is the recommended way to compile a development image? The goal is to compile
> >>a qt5 application with qtwebengine that needs eglfs support.
> >>
> >>[1] http://arago-project.org/wiki/index.php/Setting_Up_Build_Environment
> >>
> >>Thanks and kind regards
> >>
> >>Daniel
>
> --
> bytes at work
> Technoparkstrasse 7
> CH-8406 Winterthur
> Switzerland
>
> phone: +41 52 550 50 67
prev parent reply other threads:[~2020-02-20 18:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 10:27 am437x-evm zeus image Daniel Ammann
2020-02-19 19:00 ` [meta-ti] " Denys Dmytriyenko
2020-02-20 10:21 ` Daniel Ammann
2020-02-20 18:55 ` Denys Dmytriyenko [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200220185552.GA22205@beryl \
--to=denys@ti.com \
--cc=daniel.ammann@bytesatwork.ch \
--cc=meta-ti@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.