From: Hongxu Jia <hongxu.jia@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 17/18] gconf: fix buildpaths QA issue
Date: Sat, 19 Mar 2016 17:09:25 +0800 [thread overview]
Message-ID: <56ED1745.2070306@windriver.com> (raw)
In-Reply-To: <CAJTo0LZOnFNpsyDe3NRZjY6Tygb_uHSK=+hdGTJFEnOHN-DJyQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 934 bytes --]
On 03/19/2016 12:28 AM, Burton, Ross wrote:
>
> On 18 March 2016 at 09:01, Hongxu Jia <hongxu.jia@windriver.com
> <mailto:hongxu.jia@windriver.com>> wrote:
>
> In ${S}/gconf/gconfd.c, we have:
> ...
> /* -- Debug only */
>
> if (addresses == NULL)
> {
> gconf_log(GCL_DEBUG, _("gconfd compiled with debugging;
> trying to load gconf.path from the source directory"));
> conffile = g_strconcat(GCONF_SRCDIR, "/gconf/gconf.path", NULL);
> addresses = gconf_load_source_path(conffile, NULL);
> g_free(conffile);
> }
>
> /* -- End of Debug Only */
>
>
> This seems like a lot of effort to remove a build path from the
> binaries. Can we just disable the debugging support instead? GConf
> is effectively unmaintained these days anyway.
>
Of course yes, I will update it to disable debug support
//Hongxu
> Ross
[-- Attachment #2: Type: text/html, Size: 2456 bytes --]
next prev parent reply other threads:[~2016-03-19 9:09 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 [this message]
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
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=56ED1745.2070306@windriver.com \
--to=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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