All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerone Young <jyoung5-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Hollis Blanchard <hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel
	<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	kvm-ppc-devel
	<kvm-ppc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [kvm-ppc-devel] [PATCH 1/2] [v1] consolidate i386 &	x86-64	user dir make rules
Date: Tue, 23 Oct 2007 10:35:50 -0500	[thread overview]
Message-ID: <1193153750.5735.4.camel@thinkpad> (raw)
In-Reply-To: <1193153041.22407.11.camel@basalt>


On Tue, 2007-10-23 at 10:24 -0500, Hollis Blanchard wrote:
> On Tue, 2007-10-23 at 10:21 -0500, Hollis Blanchard wrote:
> > 
> > > -CFLAGS += -I $(KERNELDIR)/include $(autodepend-flags) -g -fomit-frame-pointer \
> > > -     -Wall
> > > +CFLAGS += $(autodepend-flags) -g -fomit-frame-pointer -Wall 
> > >  CFLAGS += $(call cc-option, -fno-stack-protector, "")
> > >  CFLAGS += $(call cc-option, -fno-stack-protector-all, "")
> > 
> > You seem to be adding "-I $(KERNELDIR)/include" twice: once here, and
> > once in each config-*.mak file.
> 
> My bad; I read the diff backwards. :)
> 
> Are you sure about that move though? Why doesn't every arch need that -I
> switch?

Actually no. For our powerpc stuff having -I $(KERNELDIR)/include causes
hell with errno.h & it's definitions. Since we do not include any of the
kernel headers in our codes we don't need this, but x86 does as it
includes nice headears like "linux/paravirt.h".

Now including kernel headers is a totally different argument. But
basically from what I know is you should "never" do it. 

> 


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

  reply	other threads:[~2007-10-23 15:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-23  5:57 [PATCH 1/2] [v1] consolidate i386 & x86-64 user dir make rules Jerone Young
2007-10-23 15:21 ` [kvm-ppc-devel] " Hollis Blanchard
2007-10-23 15:24   ` Hollis Blanchard
2007-10-23 15:35     ` Jerone Young [this message]
2007-10-23 15:45   ` Jerone Young
2007-10-23 15:52     ` Hollis Blanchard
2007-10-23 16:06       ` Jerone Young
2007-10-23 18:10         ` Hollis Blanchard

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=1193153750.5735.4.camel@thinkpad \
    --to=jyoung5-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
    --cc=hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=kvm-ppc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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.