From: Saul Wold <sgw@linux.intel.com>
To: Joe Slater <jslater@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] acpid: modify CFLAGS
Date: Thu, 14 Feb 2013 12:24:49 -0800 [thread overview]
Message-ID: <511D4811.2080401@linux.intel.com> (raw)
In-Reply-To: <1360861770-30010-1-git-send-email-jslater@windriver.com>
On 02/14/2013 09:09 AM, Joe Slater wrote:
> Override the hard-coded CFLAGS used in Makefile
> to reference our CFLAGS.
>
Can you be clearer about this?
I just checked the output of the compile log and these flags are set
correctly. I also looked at the make -n output via a devshell.
This seems to be hardcoding the CFLAGS into this recipe.
Sounds like something else is going on.
Thanks
Sau!
> Upstream-Status: Pending
>
> Signed-off-by: Joe Slater <jslater@windriver.com>
> ---
> meta/recipes-bsp/acpid/acpid.inc | 4 +++-
> 1 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/meta/recipes-bsp/acpid/acpid.inc b/meta/recipes-bsp/acpid/acpid.inc
> index 3c0219f..1ffe6ff 100644
> --- a/meta/recipes-bsp/acpid/acpid.inc
> +++ b/meta/recipes-bsp/acpid/acpid.inc
> @@ -13,7 +13,9 @@ inherit update-rc.d
> INITSCRIPT_NAME = "acpid"
> INITSCRIPT_PARAMS = "defaults"
>
> -EXTRA_OEMAKE = ""
> +# Makefile ignores our CFLAGS, so override it.
> +#
> +EXTRA_OEMAKE = "CFLAGS='-W -Wall -Werror -Wundef -Wshadow ${CFLAGS} $(DEFS)'"
>
> do_compile () {
> oe_runmake 'CC=${CC} -D_GNU_SOURCE' 'CROSS=${HOST_PREFIX}'
>
next prev parent reply other threads:[~2013-02-14 20:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 17:09 [PATCH] acpid: modify CFLAGS Joe Slater
2013-02-14 20:24 ` Saul Wold [this message]
2013-02-15 19:16 ` Slater, Joseph
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=511D4811.2080401@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=jslater@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.