From: Saul Wold <saul.wold@intel.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] kernel.bbclass: fix INC directory for SLANG
Date: Fri, 24 Aug 2012 11:47:44 -0700 [thread overview]
Message-ID: <5037CC50.2050805@intel.com> (raw)
In-Reply-To: <6bfd8089c0dade4775adfac96644215ffdfc0f4e.1345785364.git.bruce.ashfield@windriver.com>
On 08/23/2012 10:18 PM, Bruce Ashfield wrote:
> From: Liang Li <liang.li@windriver.com>
>
> In the kernel's tools/perf/Makefile CFLAGS was previously hard coded to
> contain "-I/usr/include/slang" to work with hosts that have
> "/usr/include/slang/slang.h" as well as hosts that have
> "/usr/include/slang.h". This path can cause compile warnings like:
>
> cc1: warning: '/usr/include/slang' doesn't exists.
>
> or
>
> cc1: warning: include location "/usr/include/slang" is unsafe for
> cross-compilation [-Wpoison-system-directories]
>
> Then in some cases warnings become errors if WERROR is enabled hence
> build errors.
>
> In coordination with a kernel fix, we can fix this error for all
> kernels by modifying the perf Makefile within the staged kernel
> source.
>
> Signed-off-by: Liang Li <liang.li@windriver.com>
> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
> ---
> meta/classes/kernel.bbclass | 3 +++
> .../recipes-kernel/linux/linux-yocto/noslang.patch | 20 --------------------
> meta/recipes-kernel/linux/linux-yocto_3.0.bb | 2 --
> meta/recipes-kernel/linux/linux-yocto_3.2.bb | 2 --
> meta/recipes-kernel/linux/linux-yocto_3.4.bb | 2 --
> 5 files changed, 3 insertions(+), 26 deletions(-)
> delete mode 100644 meta/recipes-kernel/linux/linux-yocto/noslang.patch
>
> diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
> index f34e632..fdef1be 100644
> --- a/meta/classes/kernel.bbclass
> +++ b/meta/classes/kernel.bbclass
> @@ -204,6 +204,9 @@ kernel_do_install() {
> for entry in $bin_files; do
> rm -f $kerneldir/$entry
> done
> +
> + # Fix SLANG_INC for slang.h
> + sed -i 's#-I/usr/include/slang#-I=/usr/include/slang#g' $kerneldir/tools/perf/Makefile
> }
>
> sysroot_stage_all_append() {
> diff --git a/meta/recipes-kernel/linux/linux-yocto/noslang.patch b/meta/recipes-kernel/linux/linux-yocto/noslang.patch
> deleted file mode 100644
> index 9cada34..0000000
> --- a/meta/recipes-kernel/linux/linux-yocto/noslang.patch
> +++ /dev/null
> @@ -1,20 +0,0 @@
> -We (OE) install slang into /usr/include so we never need to look into
> -/usr/include/slang/. We never want to look into a hardcoded path like this
> -since it triggers host infection issues. For now, simply remove this
> -since it causes us problems.
> -
> -Upstream-Status: Pending (would need rework)
> -
> -Index: tools/perf/Makefile
> -===================================================================
> ---- linux.orig/tools/perf/Makefile 2012-08-07 10:29:43.020149620 +0000
> -+++ linux/tools/perf/Makefile 2012-08-07 10:30:08.128148098 +0000
> -@@ -504,7 +504,7 @@
> - BASIC_CFLAGS += -DNO_NEWT_SUPPORT
> - else
> - # Fedora has /usr/include/slang/slang.h, but ubuntu /usr/include/slang.h
> -- BASIC_CFLAGS += -I/usr/include/slang
> -+ # BASIC_CFLAGS += -I/usr/include/slang
> - EXTLIBS += -lnewt -lslang
> - LIB_OBJS += $(OUTPUT)util/ui/setup.o
> - LIB_OBJS += $(OUTPUT)util/ui/browser.o
> diff --git a/meta/recipes-kernel/linux/linux-yocto_3.0.bb b/meta/recipes-kernel/linux/linux-yocto_3.0.bb
> index 4d19664..b9e5036 100644
> --- a/meta/recipes-kernel/linux/linux-yocto_3.0.bb
> +++ b/meta/recipes-kernel/linux/linux-yocto_3.0.bb
> @@ -24,8 +24,6 @@ PV = "${LINUX_VERSION}+git${SRCPV}"
>
> SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.0;protocol=git;bareclone=1;branch=${KBRANCH},meta;name=machine,meta"
>
> -SRC_URI += "file://noslang.patch"
> -
> COMPATIBLE_MACHINE = "qemuarm|qemux86|qemuppc|qemumips|qemux86-64"
>
> # Functionality flags
> diff --git a/meta/recipes-kernel/linux/linux-yocto_3.2.bb b/meta/recipes-kernel/linux/linux-yocto_3.2.bb
> index c3fb252..6a162dd 100644
> --- a/meta/recipes-kernel/linux/linux-yocto_3.2.bb
> +++ b/meta/recipes-kernel/linux/linux-yocto_3.2.bb
> @@ -24,8 +24,6 @@ KMETA = "meta"
>
> SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.2;protocol=git;bareclone=1;branch=${KBRANCH},meta;name=machine,meta"
>
> -SRC_URI += "file://noslang.patch"
> -
> COMPATIBLE_MACHINE = "qemuarm|qemux86|qemuppc|qemumips|qemux86-64"
>
> # Functionality flags
> diff --git a/meta/recipes-kernel/linux/linux-yocto_3.4.bb b/meta/recipes-kernel/linux/linux-yocto_3.4.bb
> index 691d789..6fa4920 100644
> --- a/meta/recipes-kernel/linux/linux-yocto_3.4.bb
> +++ b/meta/recipes-kernel/linux/linux-yocto_3.4.bb
> @@ -13,8 +13,6 @@ SRCREV_meta ?= "28bcd46af1d592dab39bd8a0891c872454fde8bc"
>
> SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.4.git;protocol=git;nocheckout=1;branch=${KBRANCH},meta;name=machine,meta"
>
> -SRC_URI += "file://noslang.patch"
> -
> LINUX_VERSION ?= "3.4.7"
>
> PR = "${INC_PR}.0"
>
Is a PR bump needed here?
Sau!
next prev parent reply other threads:[~2012-08-24 18:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 5:18 [PATCH 0/1] kernel.bbclass: fix INC directory for SLANG Bruce Ashfield
2012-08-24 5:18 ` [PATCH 1/1] " Bruce Ashfield
2012-08-24 18:47 ` Saul Wold [this message]
2012-08-24 18:57 ` Bruce Ashfield
2012-08-24 19:13 ` Bruce Ashfield
2012-08-27 15:45 ` [PATCH 0/1] " Saul Wold
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=5037CC50.2050805@intel.com \
--to=saul.wold@intel.com \
--cc=bruce.ashfield@windriver.com \
--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 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.