From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] wireshark: not put the CC options into CFLAGS_FOR_BUILD
Date: Tue, 23 Sep 2014 18:58:16 +0200 [thread overview]
Message-ID: <20140923165816.GD25706@jama> (raw)
In-Reply-To: <1410930481-10381-1-git-send-email-rongqing.li@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 3583 bytes --]
On Wed, Sep 17, 2014 at 01:08:01PM +0800, rongqing.li@windriver.com wrote:
> From: "Roy.Li" <rongqing.li@windriver.com>
Is it still needed for 1.12.1 version? If yes, please rebase (on
wireshark upgrade patch and resend.
> Signed-off-by: Roy Li <rongqing.li@windriver.com>
> ---
> .../files/Do-not-set-CC_FOR_BUILD-flags.patch | 46 ++++++++++++++++++++
> .../recipes-support/wireshark/wireshark_1.12.0.bb | 1 +
> 2 files changed, 47 insertions(+)
> create mode 100644 meta-networking/recipes-support/wireshark/files/Do-not-set-CC_FOR_BUILD-flags.patch
>
> diff --git a/meta-networking/recipes-support/wireshark/files/Do-not-set-CC_FOR_BUILD-flags.patch b/meta-networking/recipes-support/wireshark/files/Do-not-set-CC_FOR_BUILD-flags.patch
> new file mode 100644
> index 0000000..64a08ad
> --- /dev/null
> +++ b/meta-networking/recipes-support/wireshark/files/Do-not-set-CC_FOR_BUILD-flags.patch
> @@ -0,0 +1,46 @@
> +[PATCH] Do not set CC_FOR_BUILD flags
> +
> +Upstream-status: Pending
> +
> +AC_WIRESHARK_COMPILER_FLAGS_CHECK() is checking which options CC is supported,
> +and put the supported options into CFLAGS, but it should not put them into
> +CFLAGS_FOR_BUILD. since CC and BUILD_CC can be different, CFLAGS_FOR_BUILD is
> +used by BUILD_CC
> +
> +BUILD_CC is used to generated host tools, do not use the gcc's optimised options,
> +do not effect the running of host tools. so do not set CC_FOR_BUILD flags.
> +
> +Signed-off-by: Roy.Li <rongqing.li@windriver.com>
> +---
> + acinclude.m4 | 8 --------
> + 1 file changed, 8 deletions(-)
> +
> +diff --git a/acinclude.m4 b/acinclude.m4
> +index 136fc27..8d3d360 100644
> +--- a/acinclude.m4
> ++++ b/acinclude.m4
> +@@ -1755,10 +1755,6 @@ if test "x$ac_supports_gcc_flags" = "xyes" ; then
> + # just the new option.
> + #
> + CFLAGS="$CFLAGS_saved $GCC_OPTION"
> +- #
> +- # Add it to the flags we use when building build tools.
> +- #
> +- CFLAGS_FOR_BUILD="$CFLAGS_FOR_BUILD $GCC_OPTION"
> + ],
> + [
> + AC_MSG_RESULT(yes)
> +@@ -1771,10 +1767,6 @@ if test "x$ac_supports_gcc_flags" = "xyes" ; then
> + # just the new option.
> + #
> + CFLAGS="$CFLAGS_saved $GCC_OPTION"
> +- #
> +- # Add it to the flags we use when building build tools.
> +- #
> +- CFLAGS_FOR_BUILD="$CFLAGS_FOR_BUILD $GCC_OPTION"
> + fi
> + ],
> + [
> +--
> +1.9.1
> +
> diff --git a/meta-networking/recipes-support/wireshark/wireshark_1.12.0.bb b/meta-networking/recipes-support/wireshark/wireshark_1.12.0.bb
> index 39a24dc..675519b 100644
> --- a/meta-networking/recipes-support/wireshark/wireshark_1.12.0.bb
> +++ b/meta-networking/recipes-support/wireshark/wireshark_1.12.0.bb
> @@ -30,6 +30,7 @@ EXTRA_OECONF = "--with-qt=no --enable-usr-local=no --enable-tshark --with-c-ares
> LIC_FILES_CHKSUM = "file://README.linux;md5=631e077455b7972172eb149195e065b0"
> SRC_URI = " \
> http://wiresharkdownloads.riverbed.com/wireshark/src/wireshark-1.12.0.tar.bz2 \
> + file://Do-not-set-CC_FOR_BUILD-flags.patch \
> "
>
> PE = "1"
> --
> 1.7.10.4
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
prev parent reply other threads:[~2014-09-23 16:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 5:08 [PATCH] wireshark: not put the CC options into CFLAGS_FOR_BUILD rongqing.li
2014-09-23 16:58 ` Martin Jansa [this message]
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=20140923165816.GD25706@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@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