From: "S. Lockwood-Childs" <sjl@vctlabs.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Reg: Yocto build error( gcc_4.8)
Date: Tue, 7 Jun 2016 22:47:04 -0700 [thread overview]
Message-ID: <20160608054704.GW7939@vctlabs.com> (raw)
In-Reply-To: <5757ADF4.2080507@mlbassoc.com>
On Wed, Jun 08, 2016 at 07:32:36AM +0200, Gary Thomas wrote:
> On 2016-06-08 07:20, Praveenreddy Padamati wrote:
> >Hi all,
> >
> >Please find the "gcc_4.8.bb, > do_compile failed with exit code". error log below
>
> Do you have any files using NFS (the Poky/Yocto tree, or the build tree)?
> That's not supported because of issues like this.
>
> Also as mentioned, you have really old version - you should consider updating.
>
> >| configure: loading cache ./config.cache
> >| configure: error: `CC' has changed since the previous run:
> >| configure: former value: `arm-poky-linux-gnueabi-gcc -march=armv7-a -mthumb-interwork -mfloat-abi=hard -mfpu=neon -mtune=cortex-a9 --sysroot=/home/kumarn/fsl-release-bsp/build/tmp/sysroots/imx6dlsabresd'
> >| configure: current value: `arm-poky-linux-gnueabi-gcc -march=armv7-a -mthumb-interwork -mfloat-abi=hard -mfpu=neon -mtune=cortex-a9 --sysroot=/home/kumarn/fsl-release-bsp/build/tmp/sysroots/imx6qsabresd'
> >| configure: error: in `/home/kumarn/fsl-release-bsp/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/gcc/4.8.2-r0/gcc-4.8.2/build.arm-poky-linux-gnueabi.arm-poky-linux-gnueabi/fixincludes':
> >| configure: error: changes in the environment can compromise the build
> >| configure: error: run `make distclean' and/or `rm ./config.cache' and start over
> >| configure: error: `CC' has changed since the previous run:
> >| configure: former value: `arm-poky-linux-gnueabi-gcc -march=armv7-a -mthumb-interwork -mfloat-abi=hard -mfpu=neon -mtune=cortex-a9 --sysroot=/home/kumarn/fsl-release-bsp/build/tmp/sysroots/imx6dlsabresd'
> >| configure: current value: `arm-poky-linux-gnueabi-gcc -march=armv7-a -mthumb-interwork -mfloat-abi=hard -mfpu=neon -mtune=cortex-a9 --sysroot=/home/kumarn/fsl-release-bsp/build/tmp/sysroots/imx6qsabresd'
> >| configure: error: in `/home/kumarn/fsl-release-bsp/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/gcc/4.8.2-r0/gcc-4.8.2/build.arm-poky-linux-gnueabi.arm-poky-linux-gnueabi/libiberty':
> >| configure: error: changes in the environment can compromise the build
> >| configure: error: run `make distclean' and/or `rm ./config.cache' and start over
> >| make[1]: *** [configure-fixincludes] Error 1
> >| make[1]: *** Waiting for unfinished jobs....
> >| make[1]: *** [configure-libiberty] Error 1
Yes 1.6 version was a while ago... bitbake got better at figuring out what to
rebuild in modern times. Probably need to clobber the whole build/tmp area
after switching config from imx6dlsabresd to imx6qsabresd, to force a clean
start instead of assuming that an old bitbake will clean up everything that it
needs to.
next prev parent reply other threads:[~2016-06-08 5:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 14:03 Reg: Yocto build error( gcc_4.8) Praveenreddy Padamati
2016-06-07 14:28 ` Gary Thomas
2016-06-08 5:20 ` Praveenreddy Padamati
2016-06-08 5:32 ` Gary Thomas
2016-06-08 5:47 ` S. Lockwood-Childs [this message]
2016-06-21 22:10 ` Khem Raj
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=20160608054704.GW7939@vctlabs.com \
--to=sjl@vctlabs.com \
--cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox