Skip to contentSkip to conversation

perf: hard-code NO_LIBPERL/NO_LIBPYTHO

PATCH In review Bruce Ashfield 3 participants 5 messages Jan 25, 2011 – Jan 28, 2011

lore
Share & tools
lore

Bruce Ashfield

author
#0 lore raw

cover perf: hard-code NO_LIBPERL/NO_LIBPYTHO

We already had this fix in the 2.6.37 kernel (and it is staged temporarily there) so this is the same change for the -stable kernel to fix the perf build error reported by Gary this morning.

I went ahead and merged this to the kernel tree directly, since we may not loop back and do another fix for this on in the -stable kernel.

Compiled for atom-pc/beagleboard and routerstationpro.

Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: zedd/kernel-stable
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-stable

Thanks,
Bruce Ashfield <[email protected]>
---

Bruce Ashfield (1):
linux-yocto/stable: perf: hard-code NO_LIBPERL/NO_LIBPYTHO

 .../conf/distro/include/poky-default-revisions.inc |   18 +++++++++---------
 1 files changed, 9 insertions(+), 9 deletions(-)
author
#1 lore raw

PATCH 1/1 linux-yocto/stable: perf: hard-code NO_LIBPERL/NO_LIBPYTHO

Updating SRCREVs to reflect:

perf: hard-code NO_LIBPERL/NO_LIBPYTHON

ExtUtils::Embed ccopts is getting the host's -I/usr/local/include and using it to compile perf, which results in a compilation error that started appearing just recently.

This turns the code that makes use of ExtUtils::Embed off and simply hard-codes NO_LIBPERL.

It does the same for LIBPYTHON while we're at it, since it probably suffers from a similar underlying problem and just by chance hasn't broken anything yet.

This will be re-enabled after I familiarize myself with the perf recipe and am able to create a proper fix.

Signed-off-by Tom Zanussi <[email protected]>
Signed-off-by Bruce Ashfield <[email protected]>
Signed-off-by Bruce Ashfield <[email protected]>
---
 .../conf/distro/include/poky-default-revisions.inc |   18 +++++++++---------
 1 files changed, 9 insertions(+), 9 deletions(-)
meta/conf/distro/include/poky-default-revisions.inc +9 -9
index 8d98eef..dbb408a 100644
@@ -84,15 +84,15 @@ SRCREV_pn-linux-omap-zoomsync ??= "015cbaf1035cd9a61d33a27de2a22902555db3c5"
 SRCREV_pn-linux-omap2 ??= "d3b3ae0fe6c71641da19c8de466ec366d39847e3"
 SRCREV_pn-linux-omap3 ??= "de1121fdb899f762b9e717f44eaf3fae7c00cd3e"
 SRCREV_pn-linux-omap3-pm ??= "totallybroken"
-SRCREV_machine_pn-linux-yocto-stable_qemuarm ?= "8cc1674d61d0e0e1bf006164074cffd1071a3a52"
-SRCREV_machine_pn-linux-yocto-stable_qemumips ?= "4f4d1cecd1705dc2b065eb42a9623778bb269930"
-SRCREV_machine_pn-linux-yocto-stable_qemuppc ?= "ee9510116f63aabb852708747bd0e3c32eeaf5bf"
-SRCREV_machine_pn-linux-yocto-stable_qemux86 ?= "35521a5a70316785a67aca1de1d39a7b84c49ccf"
-SRCREV_machine_pn-linux-yocto-stable_qemux86-64 ?= "35521a5a70316785a67aca1de1d39a7b84c49ccf"
-SRCREV_machine_pn-linux-yocto-stable_atom-pc ?= "35521a5a70316785a67aca1de1d39a7b84c49ccf"
-SRCREV_machine_pn-linux-yocto-stable_routerstationpro ?= "b323ab98f055df012277f09d444951619fda24e3"
-SRCREV_machine_pn-linux-yocto-stable_mpc8315e-rdb ?= "0d19c4ab6185b2e093beb5f366ccff4746197166"
-SRCREV_machine_pn-linux-yocto-stable_beagleboard ?= "8e15b884ecf768fd9f898da5acf24938dfe81a83"
+SRCREV_machine_pn-linux-yocto-stable_qemuarm ?= "a2fb081b44d6368eff8d28e2fdb991c61b1f428e"
+SRCREV_machine_pn-linux-yocto-stable_qemumips ?= "c32d40f960e3c89d07f079bec4c96dcbfc749f0b"
+SRCREV_machine_pn-linux-yocto-stable_qemuppc ?= "96d6bc31d3caaf62a966255479cc5cee0e76b1e9"
+SRCREV_machine_pn-linux-yocto-stable_qemux86 ?= "72ca49ab08b8eb475cec82a10049503602325791"
+SRCREV_machine_pn-linux-yocto-stable_qemux86-64 ?= "72ca49ab08b8eb475cec82a10049503602325791"
+SRCREV_machine_pn-linux-yocto-stable_atom-pc ?= "72ca49ab08b8eb475cec82a10049503602325791"
+SRCREV_machine_pn-linux-yocto-stable_routerstationpro ?= "49745cd45c92a89e70c6e2334caa80818c134562"
+SRCREV_machine_pn-linux-yocto-stable_mpc8315e-rdb ?= "a1c0ed6bf4060c10874b2a8547d81b3169dcf16a"
+SRCREV_machine_pn-linux-yocto-stable_beagleboard ?= "ef7f944e773950d4016b7643f9ecf052bbe250cd"
 SRCREV_meta_pn-linux-yocto-stable ?= "e1f85a470934a0cf6abde5d95533e74501822c6b"
 # development SRCREVs
 SRCREV_machine_pn-linux-yocto_qemuarm ?= "4f86b5a0cb23faa4134cc004730d673f6640614b"
Signature · 1 line
1.7.0.4
#2 lore raw
In reply to Bruce Ashfield
Quoted 10 lines · Bruce Ashfield

We already had this fix in the 2.6.37 kernel (and it is staged temporarily there) so this is the same change for the -stable kernel to fix the perf build error reported by Gary this morning.

I went ahead and merged this to the kernel tree directly, since we may not loop back and do another fix for this on in the -stable kernel.

Compiled for atom-pc/beagleboard and routerstationpro.

Does this mean we can revert the patch in perl and python recipes?

Sau!

Quoted 20 lines

Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: zedd/kernel-stable
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-stable

Thanks,
Bruce Ashfield<[email protected]>
---

Bruce Ashfield (1):
linux-yocto/stable: perf: hard-code NO_LIBPERL/NO_LIBPYTHO

  .../conf/distro/include/poky-default-revisions.inc |   18 +++++++++---------
  1 files changed, 9 insertions(+), 9 deletions(-)

_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky

#3 lore raw
Quoted 6 lines · Saul Wold
Quoted 5 lines · Bruce Ashfield

We already had this fix in the 2.6.37 kernel (and it is staged temporarily there) so this is the same change for the -stable kernel to fix the perf build error reported by Gary this morning.

Quoted 7 lines
Quoted 6 lines

I went ahead and merged this to the kernel tree directly, since we may not loop back and do another fix for this on in the -stable kernel.

Compiled for atom-pc/beagleboard and routerstationpro.

Does this mean we can revert the patch in perl and python recipes?

I hadn't noticed if we had a patch there, I'll have a look. The other patch we had for this was for 2.6.37 and we are maintaining it out of tree (since it is temporary).

so right now, we shouldn't revert anything that I know of, and only add this one in for the 2.6.34 kernel.

Cheers,

Bruce

Quoted 31 lines

Sau!

Quoted 13 lines

Pull URL: git://git.pokylinux.org/poky-contrib.git
  Branch: zedd/kernel-stable
  Browse:
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-stable

Thanks,
    Bruce Ashfield<[email protected]>
---

Bruce Ashfield (1):
  linux-yocto/stable: perf: hard-code NO_LIBPERL/NO_LIBPYTHO

Quoted 9 lines

 .../conf/distro/include/poky-default-revisions.inc |   18
+++++++++---------

 1 files changed, 9 insertions(+), 9 deletions(-)

_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky

_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky

Signature · 2 lines
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
#4 lore raw
In reply to Bruce Ashfield
Quoted 22 lines · Bruce Ashfield

We already had this fix in the 2.6.37 kernel (and it is staged temporarily there) so this is the same change for the -stable kernel to fix the perf build error reported by Gary this morning.

I went ahead and merged this to the kernel tree directly, since we may not loop back and do another fix for this on in the -stable kernel.

Compiled for atom-pc/beagleboard and routerstationpro.

Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: zedd/kernel-stable
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-stable

Thanks,
Bruce Ashfield<[email protected]>
---

Bruce Ashfield (1):
linux-yocto/stable: perf: hard-code NO_LIBPERL/NO_LIBPYTHO

Quoted 8 lines
  .../conf/distro/include/poky-default-revisions.inc |   18 +++++++++---------
  1 files changed, 9 insertions(+), 9 deletions(-)

_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky

Pulled into Master

Thanks
Sau!