[yocto] Current Build Failures for d82f205cfa790b40e132e11b7937050bc3b97ff3

[João Henrique Freitas]

Hi,

I have two build machines:

x86 ubuntu 10.04 at work
x86_64 ubuntu 10.04 at home

At home all things goes ok. But at work perf has failed.

The problem is LIBPERL. I can't understand why but at work the
Makefile from perf does not have the flag NO_LIBPERL.

To 'solve'  it I put:

do_compile_perf() {
	oe_runmake -C ${S}/tools/perf CC="${CC}" LD="${LD}" prefix=${prefix}
NO_LIBPERL=1
}

in linux-tools.inc

Thanks.

On Thu, Jan 13, 2011 at 2:47 PM, Tom Zanussi <tom.zanussi at intel.com> wrote:
> On Thu, 2011-01-13 at 08:37 -0800, Bruce Ashfield wrote:
>> On 11-01-13 11:33 AM, Elizabeth Flanagan wrote:
>> > All,
>> >
>> > The current nightly based on d82f205cfa790b40e132e11b7937050bc3b97ff3 is
>> > showing 3 build failures so far.
>> >
>> > Machine: qemux86
>> > Failure: intermittent tasks_0.18 failure at do_compile
>> > Description: Tasks_0.18 has failed during one buildset, however it's not
>> > failing on the other.
>> >
>> >
>> > Machine: arm
>> > Failure: sanity tests time out and cause cascading failures.
>> > Description: I'm patching the autobuilder today so that sanity tests
>> > timing out shouldn't cause a cascading failure, however the arm sanity
>> > tests are still timing out.
>> >
>> > Machine: qemux86-64
>> > Failure: linux-yocto_git failing at do_compile_perf
>> > Description:
>> > |     CC util/scripting-engines/trace-event-perl.o
>> > | cc1: warnings being treated as errors
>> > | cc1: error: include location "/usr/local/include" is unsafe for
>> > cross-compilation
>>
>> I saw this one as well, but hadn't gone back to look at
>> it yet. Did something change underneath us?
>>
>> I haven't updated any parts of the recipes or kernel that
>> would have triggered the new failure. Or at least nothing
>> that has ever showed up in my testing.
>>
>
> Yeah, it's strange that this starts happening seemingly out of the blue
> - nothing wrt this has changed recently AFAICS.
>
>> Darren/Tom: you guys have been into perf/trace recently,
>> any ideas (or time) for a quick fix ? I'm going to be
>> pegged for the day trying to sort out some other items.
>>
>
> Coincidentally, I was going to look at perf scripting next week - guess
> I'll start this week instead.  Don't have a quick fix off the top of my
> head - will start looking into it later today/tonight...
>
> Tom
>
>> Cheers,
>>
>> Bruce
>>
>> > | make: *** [util/scripting-engines/trace-event-perl.o] Error 1
>> >
>> > _______________________________________________
>> > yocto mailing list
>> > yocto at yoctoproject.org
>> > https://lists.yoctoproject.org/listinfo/yocto
>>
>
>
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



-- 
-----------------------------------------------------------
João Henrique Freitas - joaohf_at_gmail.com
Campinas-SP-Brasil
BSD051283
LPI 1
http://www.joaohfreitas.eti.br