From: Denys Dmytriyenko <denys@ti.com>
To: Trevor Woerner <twoerner@gmail.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: amx3-cm3 build failure on master
Date: Tue, 28 Aug 2018 16:55:32 -0400 [thread overview]
Message-ID: <20180828205531.GC11110@beryl> (raw)
In-Reply-To: <20180706184025.GM5464@beryl>
On Fri, Jul 06, 2018 at 02:40:25PM -0400, Denys Dmytriyenko wrote:
> On Fri, Jul 06, 2018 at 02:20:44PM -0400, Trevor Woerner wrote:
> > Hi,
> >
> > Has anyone else been seeing this?
>
> Yes. This is due to gcc-8 being PITA. I haven't had time to fix it yet - need
> to keep compatibility with older gcc too...
BTW, this is still an issue and the suggested workaround remains to use gcc-7
for now by setting below in distro config or local.conf:
GCCVERSION = "7.%"
> > Build Configuration:
> > BB_VERSION = "1.39.0"
> > BUILD_SYS = "x86_64-linux"
> > NATIVELSBSTRING = "opensuseleap-15.0"
> > TARGET_SYS = "arm-oe-linux-gnueabi"
> > MACHINE = "beaglebone"
> > DISTRO = "nodistro"
> > DISTRO_VERSION = "nodistro.0"
> > TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard"
> > TARGET_FPU = "hard"
> > meta-ti = "master:63a2ec1c7f4ef0a2c355b3bc0ea1506ae3bc8534"
> > meta = "master:416a8c241aff0dca6b8b123e52cf8e2d40c74c8d"
> >
> > Initialising tasks: 100% |##################################################################################################################| Time: 0:00:02
> > NOTE: Executing SetScene Tasks
> > NOTE: Executing RunQueue Tasks
> > ERROR: amx3-cm3-1.9.2-r0 do_compile: Function failed: do_compile (log file is located at /z/build-master/bbb/build/tmp-glibc/work/armv7at2hf-neon-oe-linux-gnueabi/amx3-cm3/1.9.2-r0/temp/log.do_compile.21045)
> > ERROR: Logfile of failure stored in: /z/build-master/bbb/build/tmp-glibc/work/armv7at2hf-neon-oe-linux-gnueabi/amx3-cm3/1.9.2-r0/temp/log.do_compile.21045
> > Log data follows:
> > | DEBUG: Executing shell function do_compile
> > | CC src/pm_services/dpll_43xx.o
> > | cc1: error: -mfloat-abi=hard: selected processor lacks an FPU
> > | make: *** [Makefile:51: src/pm_services/dpll_43xx.o] Error 1
> > | WARNING: /z/build-master/bbb/build/tmp-glibc/work/armv7at2hf-neon-oe-linux-gnueabi/amx3-cm3/1.9.2-r0/temp/run.do_compile.21045:1 exit 2 from 'make CROSS_COMPILE="arm-oe-linux-gnueabi-" CC="arm-oe-linux-gnueabi-gcc --sysroot=/z/build-master/bbb/build/tmp-glibc/work/armv7at2hf-neon-oe-linux-gnueabi/amx3-cm3/1.9.2-r0/recipe-sysroot -mfloat-abi=hard"'
> > | ERROR: Function failed: do_compile (log file is located at /z/build-master/bbb/build/tmp-glibc/work/armv7at2hf-neon-oe-linux-gnueabi/amx3-cm3/1.9.2-r0/temp/log.do_compile.21045)
> > ERROR: Task (/opt/oe/configs/z/build-master/bbb/layers/meta-ti/recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb:do_compile) failed with exit code '1'
> >
> > --
> > _______________________________________________
> > meta-ti mailing list
> > meta-ti@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/meta-ti
> --
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
prev parent reply other threads:[~2018-08-28 20:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 18:20 amx3-cm3 build failure on master Trevor Woerner
2018-07-06 18:40 ` Denys Dmytriyenko
2018-08-28 20: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=20180828205531.GC11110@beryl \
--to=denys@ti.com \
--cc=meta-ti@yoctoproject.org \
--cc=twoerner@gmail.com \
/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.