Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] cmake: don't use any header available in $(HOST_DIR)/usr/include
Date: Thu, 5 Mar 2015 13:52:58 +0200	[thread overview]
Message-ID: <20150305115258.GZ15668@tarshish> (raw)
In-Reply-To: <20150305123148.3702fccc@free-electrons.com>

Hi Thomas,

On Thu, Mar 05, 2015 at 12:31:48PM +0100, Thomas Petazzoni wrote:
> On Thu, 5 Mar 2015 09:02:55 +0200, Baruch Siach wrote:
> > On Thu, Mar 05, 2015 at 01:45:33AM +0100, Fabio Porcedda wrote:
> > > +# Get rid of -I* options to prevent that a header avaiable in
> > > +# $(HOST_DIR)/usr/include is used instead of a cmake one, e.g. lzma*
> > > +# headers of the xz package
> > > +HOST_CMAKE_CFLAGS = $(shell echo $(HOST_CFLAGS) | sed s/-I[^\ ]*//)
> > 
> > How about (untested):
> > 
> > 	HOST_CMAKE_CFLAGS = $(filter-out -I%,$(HOST_CFLAGS))
> 
> It unfortunately works only if the form:
> 
> 	-I/foo/bar
> 
> is used. If you use:
> 
> 	-I /foo/bar
> 
> which is valid for gcc, then filter-out will filter the -I but
> not /foo/bar.

Right. But the original sed expression doesn't work either. This one seems to 
work:

	s/[[:space:]]-I[[:space:]]*[^\ ]*//

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

  reply	other threads:[~2015-03-05 11:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-05  0:45 [Buildroot] [PATCH v2] cmake: don't use any header available in $(HOST_DIR)/usr/include Fabio Porcedda
2015-03-05  7:02 ` Baruch Siach
2015-03-05  7:23   ` Fabio Porcedda
2015-03-05 11:31   ` Thomas Petazzoni
2015-03-05 11:52     ` Baruch Siach [this message]
2015-03-05 13:11       ` Samuel Martin
2015-03-06  4:22       ` Fabio Porcedda
2015-03-07  8:30         ` Fabio Porcedda
2015-03-05 13:13 ` Samuel Martin
2015-03-05 13:19   ` Fabio Porcedda
2015-03-05 13:47     ` Samuel Martin

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=20150305115258.GZ15668@tarshish \
    --to=baruch@tkos.co.il \
    --cc=buildroot@busybox.net \
    /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