From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: "Burton\, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/3] ncurses: upgrade to 6.0+20160625
Date: Mon, 22 Aug 2016 13:21:27 +0200 [thread overview]
Message-ID: <lyshtxhww8.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <CAJTo0LY1L1zadYdw+AH=hVD6xu5r9sRap_G7+iALhf9q41Excw@mail.gmail.com> (Ross Burton's message of "Mon, 22 Aug 2016 11:18:22 +0100")
"Burton, Ross" <ross.burton@intel.com> writes:
>> 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 :(
>>
> ncurses isn't the first recipe we've had to patch over this...
ncurses is ugly because it uses its own private version of autoconf. We
will have to patch a lot of (compiled) 'configure' scripts, or (which I
prefer) create a local wrapper script for $CC.
I wrote an upstream bug report ([1]), but it probably has to go through
moderation first and is not visible yet.
Enrico
Footnotes:
[1] https://lists.gnu.org/archive/html/bug-ncurses/
prev parent reply other threads:[~2016-08-22 11:21 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
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 ` Enrico Scholz [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=lyshtxhww8.fsf@ensc-virt.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox