> That leaves only few issues in our internal components and strange failure
> with perf which fails to include various header files:
> perf/1.0-r9/perf-1.0/tools/perf/util/include/asm/byteorder.h:2:10: fatal
> error: ../../../../include/uapi/linux/swab.h: No such file or directory
>
On Thu, May 17, 2018 at 3:46 AM, Martin Jansa wrote:
> On Thu, May 10, 2018 at 09:11:45PM +0200, Martin Jansa wrote:
>> > > 5) nativesdk-libxcrypt fails to build (not sure which change caused
>> > > this, it build OK with sumo since the -std=gnu99 addition.
>> > >
On Thu, May 10, 2018 at 09:11:45PM +0200, Martin Jansa wrote:
> > > 5) nativesdk-libxcrypt fails to build (not sure which change caused
> > > this, it build OK with sumo since theĀ -std=gnu99 addition.
> > > ../git/crypt-sunmd5.c:189:13: error: 'snprintf' output may be truncated
> > > before the
On Mon, May 14, 2018 at 10:33:41AM -0600, Dan McGregor wrote:
> On 10 May 2018 at 12:53, Khem Raj wrote:
> > Hi Dan,
> >
> > Thanks for testing
> >
> > On 5/10/18 7:34 AM, Dan McGregor wrote:
> >>
> >> On 4 May 2018 at 18:26, Khem Raj wrote:
> >>>
> >>> Hi
On 10 May 2018 at 12:53, Khem Raj wrote:
> Hi Dan,
>
> Thanks for testing
>
> On 5/10/18 7:34 AM, Dan McGregor wrote:
>>
>> On 4 May 2018 at 18:26, Khem Raj wrote:
>>>
>>> Hi All
>>>
>>> As you might have noticed that gcc 8.1 was released this week, I am
Hi Ross
I pushed a few more fixes to branch which fixes
kernel build issue
ovmf build issue
python2 build issue (your fix)
I could not reproduce the mesa issues that is shown on AB
With this I think we should be in better shape. Can you retry
Hi Ross
Thanks for testing
I looked at failures and one of them is
RESULTS - kernelmodule.KernelModuleTest.test_kernel_module - Testcase
1541: FAILED
and this is the compile error.
pager.c: In function 'pager_preexec':
pager.c:36:12: error: passing argument 2 to restrict-qualified
parameter
I threw the branch at the Yocto Project autobuilder today, produced a
number of failures:
http://errors.yoctoproject.org/Errors/Latest//?filter=b23dba19607412c8cc7d267d95354d65f5631088=commit
Ross
On 5 May 2018 at 01:26, Khem Raj wrote:
> Hi All
>
> As you might have
On Thu, May 10, 2018 at 6:16 PM, Khem Raj wrote:
> On Thu, May 10, 2018 at 6:11 PM, Andre McCurdy wrote:
>> On Thu, May 10, 2018 at 6:06 PM, Khem Raj wrote:
>>> On Thu, May 10, 2018 at 6:00 PM, Andre McCurdy
On Thu, May 10, 2018 at 6:11 PM, Andre McCurdy wrote:
> On Thu, May 10, 2018 at 6:06 PM, Khem Raj wrote:
>> On Thu, May 10, 2018 at 6:00 PM, Andre McCurdy wrote:
>>> On Thu, May 10, 2018 at 5:55 PM, Khem Raj
On Thu, May 10, 2018 at 6:06 PM, Khem Raj wrote:
> On Thu, May 10, 2018 at 6:00 PM, Andre McCurdy wrote:
>> On Thu, May 10, 2018 at 5:55 PM, Khem Raj wrote:
>>> On Thu, May 10, 2018 at 4:11 PM, Andre McCurdy
On Thu, May 10, 2018 at 6:00 PM, Andre McCurdy wrote:
> On Thu, May 10, 2018 at 5:55 PM, Khem Raj wrote:
>> On Thu, May 10, 2018 at 4:11 PM, Andre McCurdy wrote:
>>> On Thu, May 10, 2018 at 3:50 PM, Martin Jansa
On Thu, May 10, 2018 at 5:55 PM, Khem Raj wrote:
> On Thu, May 10, 2018 at 4:11 PM, Andre McCurdy wrote:
>> On Thu, May 10, 2018 at 3:50 PM, Martin Jansa wrote:
>>> On Thu, May 10, 2018 at 03:40:53PM -0700, Andre McCurdy wrote:
On Thu, May 10, 2018 at 4:11 PM, Andre McCurdy wrote:
> On Thu, May 10, 2018 at 3:50 PM, Martin Jansa wrote:
>> On Thu, May 10, 2018 at 03:40:53PM -0700, Andre McCurdy wrote:
>>> On Thu, May 10, 2018 at 3:38 PM, Martin Jansa
On Thu, May 10, 2018 at 4:32 PM, Martin Jansa wrote:
> On Thu, May 10, 2018 at 04:11:00PM -0700, Andre McCurdy wrote:
>> On Thu, May 10, 2018 at 3:50 PM, Martin Jansa wrote:
>> > On Thu, May 10, 2018 at 03:40:53PM -0700, Andre McCurdy wrote:
>> >>
On Thu, May 10, 2018 at 04:11:00PM -0700, Andre McCurdy wrote:
> On Thu, May 10, 2018 at 3:50 PM, Martin Jansa wrote:
> > On Thu, May 10, 2018 at 03:40:53PM -0700, Andre McCurdy wrote:
> >> On Thu, May 10, 2018 at 3:38 PM, Martin Jansa
> >> wrote:
On Thu, May 10, 2018 at 3:50 PM, Martin Jansa wrote:
> On Thu, May 10, 2018 at 03:40:53PM -0700, Andre McCurdy wrote:
>> On Thu, May 10, 2018 at 3:38 PM, Martin Jansa wrote:
>> > see
>> >
On Thu, May 10, 2018 at 03:40:53PM -0700, Andre McCurdy wrote:
> On Thu, May 10, 2018 at 3:38 PM, Martin Jansa wrote:
> > see
> > http://lists.openembedded.org/pipermail/openembedded-core/2018-May/150654.html
>
> Removing -fno-omit-frame-pointer isn't the same as adding
>
On Thu, May 10, 2018 at 3:38 PM, Martin Jansa wrote:
> see
> http://lists.openembedded.org/pipermail/openembedded-core/2018-May/150654.html
Removing -fno-omit-frame-pointer isn't the same as adding
-fomit-frame-pointer. Frame pointers may get enabled depending on the
see
http://lists.openembedded.org/pipermail/openembedded-core/2018-May/150654.html
On Fri, May 11, 2018 at 12:38 AM Andre McCurdy wrote:
> On Thu, May 10, 2018 at 3:07 PM, Martin Jansa
> wrote:
> > On Thu, May 10, 2018 at 11:43:25PM +0200, Martin
On Thu, May 10, 2018 at 3:07 PM, Martin Jansa wrote:
> On Thu, May 10, 2018 at 11:43:25PM +0200, Martin Jansa wrote:
>> On Thu, May 10, 2018 at 12:27:50PM -0700, Andre McCurdy wrote:
>> > On Thu, May 10, 2018 at 12:11 PM, Martin Jansa
>> > wrote:
On Thu, May 10, 2018 at 3:07 PM, Martin Jansa wrote:
> On Thu, May 10, 2018 at 11:43:25PM +0200, Martin Jansa wrote:
>> On Thu, May 10, 2018 at 12:27:50PM -0700, Andre McCurdy wrote:
>> > On Thu, May 10, 2018 at 12:11 PM, Martin Jansa
>> > wrote:
On Thu, May 10, 2018 at 11:43:25PM +0200, Martin Jansa wrote:
> On Thu, May 10, 2018 at 12:27:50PM -0700, Andre McCurdy wrote:
> > On Thu, May 10, 2018 at 12:11 PM, Martin Jansa
> > wrote:
> > > On Thu, May 10, 2018 at 11:50:02AM -0700, Khem Raj wrote:
> > >> Hi Martin
>
On Thu, May 10, 2018 at 12:27:50PM -0700, Andre McCurdy wrote:
> On Thu, May 10, 2018 at 12:11 PM, Martin Jansa wrote:
> > On Thu, May 10, 2018 at 11:50:02AM -0700, Khem Raj wrote:
> >> Hi Martin
> >>
> >> Thanks for testing and reporting back
> >>
> >> On 5/9/18 2:38 AM,
On Thu, May 10, 2018 at 12:11 PM, Martin Jansa wrote:
> On Thu, May 10, 2018 at 11:50:02AM -0700, Khem Raj wrote:
>> Hi Martin
>>
>> Thanks for testing and reporting back
>>
>> On 5/9/18 2:38 AM, Martin Jansa wrote:
>> > My initial tests show couple issues, but usually
On Thu, May 10, 2018 at 11:50:02AM -0700, Khem Raj wrote:
> Hi Martin
>
> Thanks for testing and reporting back
>
> On 5/9/18 2:38 AM, Martin Jansa wrote:
> > My initial tests show couple issues, but usually caused by other changes
> > in that branch, not the gcc-8 itself.
> >
> > 1)
Hi Dan,
Thanks for testing
On 5/10/18 7:34 AM, Dan McGregor wrote:
On 4 May 2018 at 18:26, Khem Raj wrote:
Hi All
As you might have noticed that gcc 8.1 was released this week, I am
calling out for some testing help on testing branch so we can weed out
issues you might
Hi Martin
Thanks for testing and reporting back
On 5/9/18 2:38 AM, Martin Jansa wrote:
My initial tests show couple issues, but usually caused by other changes
in that branch, not the gcc-8 itself.
1) strace-4.22 from
On 4 May 2018 at 18:26, Khem Raj wrote:
> Hi All
>
> As you might have noticed that gcc 8.1 was released this week, I am
> calling out for some testing help on testing branch so we can weed out
> issues you might see in your setups. so if you have your
> builders idling over
My initial tests show couple issues, but usually caused by other changes in
that branch, not the gcc-8 itself.
1) strace-4.22 from
http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/gcc-8=af33a8b721cc9caebd3f5226b4c5903f666ab654
fails to build with ptest enabled (it builds with
30 matches
Mail list logo