From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/3] ncurses: upgrade to 6.0+20160625
Date: Mon, 22 Aug 2016 11:40:59 +0200 [thread overview]
Message-ID: <ly1t1hjg44.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <f2d0736dd176c21c4ef1d539a7e82dbfd1367f2a.1471246475.git.hongxu.jia@windriver.com> (Hongxu Jia's message of "Mon, 15 Aug 2016 03:35:59 -0400")
Hongxu Jia <hongxu.jia-CWA4WttNNZF54TAoqtyWWQ@public.gmane.org> writes:
> "
> # commit id corresponds to the revision in package version
> -SRCREV = "05af40f7d3af1e43144ed5315e31c7044c122fab"
> +SRCREV = "63dd558cb8e888d6fab5f00bbf7842736a2356b9"
This breaks the build with OE because it tries to split our $CC.
E.g. with
| CC = ccache arm-linux-gnueabi-gcc -march=armv7ve ... --sysroot=...
configure will warn
| your environment misuses the CC variable to hold CFLAGS/CPPFLAGS options
and messes up CFLAGS completely so that 'arm-linux-gnuebi-gcc' becomes
part of it :(
See CF_CC_ENV_FLAGS in various aclocal.m4 files.
Enrico
next prev parent reply other threads:[~2016-08-22 9:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 7:35 [PATCH 0/3] packages upgrade: man-pages/gnupg/ncurses Hongxu Jia
2016-08-15 7:35 ` [PATCH 1/3] man-pages: upgrade to 4.07 Hongxu Jia
2016-08-15 7:35 ` [PATCH 2/3] gnupg: upgrade to 2.1.14 Hongxu Jia
2016-08-15 7:35 ` [PATCH 3/3] ncurses: upgrade to 6.0+20160625 Hongxu Jia
2016-08-22 9:40 ` Enrico Scholz [this message]
2016-08-22 10:18 ` Burton, Ross
2016-08-22 11:15 ` sysroot flags in $CC (was: [PATCH 3/3] ncurses: upgrade to 6.0+20160625) Enrico Scholz
2016-08-22 11:21 ` [PATCH 3/3] ncurses: upgrade to 6.0+20160625 Enrico Scholz
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=ly1t1hjg44.fsf@ensc-virt.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--cc=openembedded-core@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