All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Burton, Ross" <ross.burton@intel.com>
To: Hongxu Jia <hongxu.jia@windriver.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 18/18] gconf: fix buildpaths QA issue
Date: Mon, 21 Mar 2016 14:47:51 +0000	[thread overview]
Message-ID: <CAJTo0LbbXz4PkHzW97csmTBjnffFJwJnR6JauecLrXc-nH3_BQ@mail.gmail.com> (raw)
In-Reply-To: <ee2f2af704cb828dd936d435cb98c88de74db825.1458397812.git.hongxu.jia@windriver.com>

[-- Attachment #1: Type: text/plain, Size: 397 bytes --]

On 19 March 2016 at 14:56, Hongxu Jia <hongxu.jia@windriver.com> wrote:

> +PACKAGECONFIG[debug] = "--enable-debug=yes, --enable-debug=no"
>

There's an explicit --enable-debug in EXTRA_OECONF, and reading the
configure --help shows that the "off" mode should be --enable-debug=minimum
as "no" removes the GLib checks which can result in crashes if bad data is
passed to the API.

Ross

[-- Attachment #2: Type: text/html, Size: 839 bytes --]

  reply	other threads:[~2016-03-21 14:48 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-18  9:01 [PATCH V3 00/18] fix buildpaths QA issue Hongxu Jia
2016-03-18  9:01 ` [PATCH 01/18] gcc-5.3/gcc-4.9:replace build path with target path in __FILE__ Hongxu Jia
2016-03-18  9:01 ` [PATCH 02/18] gcc-5.3/gcc-4.9:Reuse -fdebug-prefix-map to replace -ffile-prefix-map Hongxu Jia
2016-03-18  9:01 ` [PATCH 03/18] kernel.bbclass: fix buildpath QA issue Hongxu Jia
2016-03-18  9:01 ` [PATCH 04/18] valgrind: " Hongxu Jia
2016-03-18  9:01 ` [PATCH 05/18] dtc.inc: fix buildpaths " Hongxu Jia
2016-03-18 12:01   ` Jussi Kukkonen
2016-03-18 13:04     ` Hongxu Jia
2016-03-18  9:01 ` [PATCH 06/18] fix_buildpaths.bbclass: add bbclass to fix build path Hongxu Jia
2016-03-18  9:01 ` [PATCH 07/18] icu: fix buildpaths QA issue Hongxu Jia
2016-03-18  9:01 ` [PATCH 08/18] tcl: fix buildpath " Hongxu Jia
2016-03-18  9:01 ` [PATCH 09/18] python2/3: " Hongxu Jia
2016-03-18  9:01 ` [PATCH 10/18] bbclass distutils/distutils3: fix .pyc/.pyo buildpath Hongxu Jia
2016-03-18  9:01 ` [PATCH 11/18] bbclass distutils/distutils3/setuptools/setuptools3: clean up DISTUTILS_INSTALL_ARGS Hongxu Jia
2016-03-18  9:01 ` [PATCH 12/18] python-setuptools/python3-setuptools: use old-style install Hongxu Jia
2016-03-18  9:01 ` [PATCH 13/18] python3-pip: " Hongxu Jia
2016-03-18  9:01 ` [PATCH 14/18] waf.bbclass: support do patch on extracted files Hongxu Jia
2016-03-18  9:01 ` [PATCH 15/18] python-pycairo: fix buildpath QA issue Hongxu Jia
2016-03-18  9:01 ` [PATCH 16/18] openssl: " Hongxu Jia
2016-03-18  9:01 ` [PATCH 17/18] gconf: fix buildpaths " Hongxu Jia
2016-03-18 16:28   ` Burton, Ross
2016-03-19  9:09     ` Hongxu Jia
2016-03-18  9:02 ` [PATCH 18/18] epiphany: " Hongxu Jia
2016-03-19 14:56 ` [PATCH V4 00/18] " Hongxu Jia
2016-03-19 14:56   ` [PATCH 06/18] fix_buildpaths.bbclass: add bbclass to fix build path Hongxu Jia
2016-03-19 14:56   ` [PATCH 07/18] icu: fix buildpaths QA issue Hongxu Jia
2016-03-19 14:56   ` [PATCH 09/18] python2/3: fix buildpath " Hongxu Jia
2016-03-19 14:56   ` [PATCH 16/18] openssl: " Hongxu Jia
2016-03-19 14:56   ` [PATCH 18/18] gconf: fix buildpaths " Hongxu Jia
2016-03-21 14:47     ` Burton, Ross [this message]
2016-03-22  1:16       ` Hongxu Jia

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=CAJTo0LbbXz4PkHzW97csmTBjnffFJwJnR6JauecLrXc-nH3_BQ@mail.gmail.com \
    --to=ross.burton@intel.com \
    --cc=hongxu.jia@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.