Current Build Failures for d82f205cfa790b40e132e11b7937050bc3b97ff3

DISCUSSION Elizabeth Flanagan 5 participants 8 messages Jan 13, 2011 – Jan 14, 2011

lore

Share & tools

lore

Elizabeth Flanagan

author

2011-01-13 16:32 UTC #0 lore raw

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
| make: *** [util/scripting-engines/trace-event-perl.o] Error 1

Bruce Ashfield

2011-01-13 16:37 UTC #1 lore raw

Quoted 17 lines · Elizabeth Flanagan

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.

Quoted 7 lines

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.

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.

Cheers,

Bruce

Quoted 6 lines

| make: *** [util/scripting-engines/trace-event-perl.o] Error 1
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Tom Zanussi

2011-01-13 16:48 UTC #2 lore raw

Quoted 26 lines · Bruce Ashfield

Quoted 17 lines · Elizabeth Flanagan
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.
Quoted 7 lines
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

Quoted 7 lines

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.

Quoted 4 lines

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

Quoted 11 lines

Cheers,
Bruce
Quoted 6 lines
| make: *** [util/scripting-engines/trace-event-perl.o] Error 1
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

João Henrique Freitas

2011-01-14 01:37 UTC #3 lore raw

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.

Quoted 67 lines · Tom Zanussi

Quoted 26 lines · Bruce Ashfield
Quoted 17 lines · Elizabeth Flanagan
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.
Quoted 7 lines
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
Quoted 7 lines
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.
Quoted 4 lines
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
Quoted 11 lines
Cheers,
Bruce
Quoted 6 lines
| make: *** [util/scripting-engines/trace-event-perl.o] Error 1
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Signature · 6 lines

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

Bruce Ashfield

2011-01-14 01:41 UTC #4 lore raw

Quoted 8 lines · 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.

Are your package lists identical ? Sounds like host contamination to me and perf is deciding to build perl or not perl based on what the host has installed.

Quoted 9 lines

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

This works .. or to get the functionality back, we get perl in the package list and kindly ask perf to look in our sysroot for what it needs :)

Thanks for the digging on this.

Bruce

Quoted 77 lines

}
in linux-tools.inc
Thanks.
Quoted 67 lines · Tom Zanussi
Quoted 26 lines · Bruce Ashfield
Quoted 17 lines · Elizabeth Flanagan
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.
Quoted 7 lines
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
Quoted 7 lines
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.
Quoted 4 lines
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
Quoted 11 lines
Cheers,
Bruce
Quoted 6 lines
| make: *** [util/scripting-engines/trace-event-perl.o] Error 1
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Xu, Jiajun

2011-01-14 01:59 UTC #7 lore raw

In reply to Elizabeth Flanagan

Quoted 11 lines

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.

Quoted 6 lines

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.

What's the patch you made for autobuilder? I think the patch I sent out yesterday can prevent the cascading failure but it has not been checked in yet.

Quoted 10 lines

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 | make: *** [util/scripting-engines/trace-event-perl.o] Error 1
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Best Regards,
Jiajun

Tom Zanussi

2011-01-14 06:34 UTC #5 lore raw

In reply to Bruce Ashfield

Quoted 20 lines · Bruce Ashfield

Quoted 8 lines · 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.
Are your package lists identical ? Sounds like host contamination to me and perf is deciding to build perl or not perl based on what the host has installed.
Quoted 6 lines
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:

Quoted 8 lines

Quoted 3 lines
do_compile_perf() {
	oe_runmake -C ${S}/tools/perf CC="${CC}" LD="${LD}" prefix=${prefix}
NO_LIBPERL=1
This works .. or to get the functionality back, we get perl in the package list and kindly ask perf to look in our sysroot for what it needs :)

One thing I notice is that recipes-devtools/perl/perl_5.12.2.bb doesn't install ExtUtils, which perl_5.8.8.bb did.

The logic in perf that decides whether to define NO_LIBPERL depends on the output of ExtUtils::Embed - it looks like it may be picking up the host's ccopts instead, which might explain the /usr/local/include in the error message:

cc1: error: include location "/usr/local/include" is unsafe for cross-compilation

Will look into it more tomorrow...

Tom

Quoted 82 lines

Thanks for the digging on this.
Bruce
Quoted 77 lines
}
in linux-tools.inc
Thanks.
Quoted 67 lines · Tom Zanussi
Quoted 26 lines · Bruce Ashfield
Quoted 17 lines · Elizabeth Flanagan
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.
Quoted 7 lines
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
Quoted 7 lines
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.
Quoted 4 lines
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
Quoted 11 lines
Cheers,
Bruce
Quoted 6 lines
| make: *** [util/scripting-engines/trace-event-perl.o] Error 1
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Bruce Ashfield

2011-01-14 15:48 UTC #6 lore raw

Quoted 25 lines · Tom Zanussi

Quoted 24 lines · Bruce Ashfield
Quoted 8 lines · 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.
Are your package lists identical ? Sounds like host contamination to me and perf is deciding to build perl or not perl based on what the host has installed.
Quoted 9 lines
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

Quoted 7 lines

Quoted 4 lines
This works .. or to get the functionality back, we get perl in the package list and kindly ask perf to look in our sysroot for what it needs :)
One thing I notice is that recipes-devtools/perl/perl_5.12.2.bb doesn't install ExtUtils, which perl_5.8.8.bb did.

That would explain the "what changed under us?" if this turns out to be the cause.

Quoted 7 lines

The logic in perf that decides whether to define NO_LIBPERL depends on the output of ExtUtils::Embed - it looks like it may be picking up the host's ccopts instead, which might explain the /usr/local/include in the error message:
cc1: error: include location "/usr/local/include" is unsafe for cross-compilation

Sounds like we are on the right track.

Quoted 2 lines

Will look into it more tomorrow...

Many thanks!

Bruce

Quoted 87 lines

Tom
Quoted 82 lines
Thanks for the digging on this.
Bruce
Quoted 77 lines
}
in linux-tools.inc
Thanks.
Quoted 67 lines · Tom Zanussi
Quoted 26 lines · Bruce Ashfield
Quoted 17 lines · Elizabeth Flanagan
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.
Quoted 7 lines
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
Quoted 7 lines
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.
Quoted 4 lines
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
Quoted 11 lines
Cheers,
Bruce
Quoted 6 lines
| make: *** [util/scripting-engines/trace-event-perl.o] Error 1
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto