Re: [OE-core] [PATCH v3] gcc-sanitizers: fix -Werror=maybe-uninitialized issue

On 2019年04月18日 01:14, Khem Raj wrote: On Wed, Apr 17, 2019 at 12:45 AM Yu, Mingli wrote: On 2019年04月17日 02:00, Khem Raj wrote: On Tue, Apr 16, 2019 at 1:40 AM Yu, Mingli wrote: On 2019年04月16日 00:21, Adrian Bunk wrote: On Mon, Apr 15, 2019 at 07:19:13AM -0700, Khem Raj wrote: What

Re: [OE-core] [PATCH v3] gcc-sanitizers: fix -Werror=maybe-uninitialized issue

On Wed, Apr 17, 2019 at 12:45 AM Yu, Mingli wrote: > > > > On 2019年04月17日 02:00, Khem Raj wrote: > > On Tue, Apr 16, 2019 at 1:40 AM Yu, Mingli wrote: > >> > >> > >> > >> On 2019年04月16日 00:21, Adrian Bunk wrote: > >>> On Mon, Apr 15, 2019 at 07:19:13AM -0700, Khem Raj wrote: > > What

Re: [OE-core] [PATCH v3] gcc-sanitizers: fix -Werror=maybe-uninitialized issue

On 2019年04月17日 02:00, Khem Raj wrote: On Tue, Apr 16, 2019 at 1:40 AM Yu, Mingli wrote: On 2019年04月16日 00:21, Adrian Bunk wrote: On Mon, Apr 15, 2019 at 07:19:13AM -0700, Khem Raj wrote: What are you trying to convey ? That’s what I mentioned before I began my reply however to

Re: [OE-core] [PATCH v3] gcc-sanitizers: fix -Werror=maybe-uninitialized issue

On Tue, Apr 16, 2019 at 1:40 AM Yu, Mingli wrote: > > > > On 2019年04月16日 00:21, Adrian Bunk wrote: > > On Mon, Apr 15, 2019 at 07:19:13AM -0700, Khem Raj wrote: > >> > >> What are you trying to convey ? That’s what I mentioned before I began my > >> reply however to reiterate my point was if a

Re: [OE-core] [PATCH v3] gcc-sanitizers: fix -Werror=maybe-uninitialized issue

On 2019年04月16日 00:21, Adrian Bunk wrote: On Mon, Apr 15, 2019 at 07:19:13AM -0700, Khem Raj wrote: What are you trying to convey ? That’s what I mentioned before I began my reply however to reiterate my point was if a package is not usually built and tested with this combination which is

Re: [OE-core] [PATCH v3] gcc-sanitizers: fix -Werror=maybe-uninitialized issue

On Mon, Apr 15, 2019 at 07:19:13AM -0700, Khem Raj wrote: > > What are you trying to convey ? That’s what I mentioned before I began my > reply however to reiterate my point was if a package is not usually built > and tested with this combination which is evident because it fails to build > then

Re: [OE-core] [PATCH v3] gcc-sanitizers: fix -Werror=maybe-uninitialized issue

On Mon, Apr 15, 2019 at 2:38 AM Adrian Bunk wrote: > On Mon, Apr 08, 2019 at 08:53:49PM -0700, Khem Raj wrote: > > On Mon, Apr 8, 2019 at 7:32 PM wrote: > > > > > > From: Mingli Yu > > > > > > When DEBUG_BUILD = "1" added in local.conf, there > > > comes below build error when "bitbake

Re: [OE-core] [PATCH v3] gcc-sanitizers: fix -Werror=maybe-uninitialized issue

On Mon, Apr 08, 2019 at 08:53:49PM -0700, Khem Raj wrote: > On Mon, Apr 8, 2019 at 7:32 PM wrote: > > > > From: Mingli Yu > > > > When DEBUG_BUILD = "1" added in local.conf, there > > comes below build error when "bitbake gcc-sanitizers": > > | > >

Re: [OE-core] [PATCH v3] gcc-sanitizers: fix -Werror=maybe-uninitialized issue

On 2019年04月09日 11:53, Khem Raj wrote: On Mon, Apr 8, 2019 at 7:32 PM wrote: From: Mingli Yu When DEBUG_BUILD = "1" added in local.conf, there comes below build error when "bitbake gcc-sanitizers": |

Re: [OE-core] [PATCH v3] gcc-sanitizers: fix -Werror=maybe-uninitialized issue

On Mon, Apr 8, 2019 at 7:32 PM wrote: > > From: Mingli Yu > > When DEBUG_BUILD = "1" added in local.conf, there > comes below build error when "bitbake gcc-sanitizers": > | > ./../../../../../../../../work-shared/gcc-8.3.0-r0/gcc-8.3.0/libsanitizer/libbacktrace/../../libbacktrace/elf.c: > In

[OE-core] [PATCH v3] gcc-sanitizers: fix -Werror=maybe-uninitialized issue

From: Mingli Yu When DEBUG_BUILD = "1" added in local.conf, there comes below build error when "bitbake gcc-sanitizers": | ./../../../../../../../../work-shared/gcc-8.3.0-r0/gcc-8.3.0/libsanitizer/libbacktrace/../../libbacktrace/elf.c: In function 'elf_is_symlink': |