Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Henning Heinold <heinold@inf.fu-berlin.de>
To: Liang Li <liang.li@windriver.com>
Cc: darren.hart@intel.com, openembedded-core@lists.openembedded.org
Subject: Re: [discussion] perf: specify SLANG_INC dir for perf
Date: Tue, 21 Aug 2012 10:51:39 +0200	[thread overview]
Message-ID: <20120821085138.GA29885@mi.fu-berlin.de> (raw)
In-Reply-To: <20120821050825.GB27917@localhost>

On Tue, Aug 21, 2012 at 01:08:25PM +0800, Liang Li wrote:
> --- a/meta/classes/kernel.bbclass
> +++ b/meta/classes/kernel.bbclass
> @@ -190,6 +190,9 @@ kernel_do_install() {
>  	for entry in $bin_files; do
>  	        rm -f $kerneldir/$entry
>  	done
> +
> +	# Fix SLNAG_INC for slang.h
> +	sed -i 's#-I/usr/include/slang#-I=/usr/include/slang#g' $kerneldir/tools/perf/Makefile
Hm,

is this "-I=" a new special feature of gcc?

-I/usr/include/slang
-I=/usr/include/slang

Bye Henning



  reply	other threads:[~2012-08-21  9:03 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-03 15:43 [PATCH] perf: pass STAGING_INCDIR(sysroot) to perf Liang Li
2012-08-07 12:56 ` Bruce Ashfield
2012-08-07 14:12   ` Richard Purdie
2012-08-07 14:19     ` Bruce Ashfield
2012-08-07 14:27       ` Richard Purdie
2012-08-07 14:02 ` Richard Purdie
2012-08-07 14:07   ` Bruce Ashfield
2012-08-07 14:22     ` Richard Purdie
2012-08-07 14:29       ` Bruce Ashfield
2012-08-07 14:44         ` Richard Purdie
2012-08-07 15:26           ` Bruce Ashfield
2012-08-07 15:41             ` Richard Purdie
2012-08-07 15:54               ` Bruce Ashfield
2012-08-07 16:02                 ` Richard Purdie
2012-08-08  3:37   ` Liang Li
2012-08-09  0:36     ` Darren Hart
2012-08-09  1:24       ` Liang Li
2012-08-09  1:41         ` Darren Hart
2012-08-09  1:52           ` Liang Li
2012-08-09  3:54             ` Darren Hart
2012-08-09  1:33       ` Bruce Ashfield
2012-08-14  2:17     ` [discussion] perf: specify SLANG_INC dir for perf Liang Li
2012-08-16 15:33       ` Bruce Ashfield
2012-08-16 15:58         ` Richard Purdie
2012-08-16 16:00           ` Bruce Ashfield
2012-08-16 16:12           ` McClintock Matthew-B29882
2012-08-17  3:32           ` Liang Li
2012-08-17  9:35             ` Richard Purdie
2012-08-17 10:00               ` Liang Li
2012-08-17 10:53                 ` Richard Purdie
2012-08-17 12:55                   ` Bruce Ashfield
2012-08-17 13:01                   ` Liang Li
2012-08-17 13:05                     ` Liang Li
2012-08-20 14:48                       ` Bruce Ashfield
2012-08-21  5:08                         ` Liang Li
2012-08-21  8:51                           ` Henning Heinold [this message]
2012-08-21  9:19                             ` Liang Li
2012-08-21 10:40                             ` Richard Purdie
2012-08-21 13:07                           ` Bruce Ashfield
2012-08-22  3:01                             ` Liang Li
2012-08-22  5:41                               ` Bruce Ashfield
2012-08-22  8:17                                 ` Liang Li
2012-08-17 14:35                     ` Darren Hart

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=20120821085138.GA29885@mi.fu-berlin.de \
    --to=heinold@inf.fu-berlin.de \
    --cc=darren.hart@intel.com \
    --cc=liang.li@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox