Re: [yocto] [RFC 0/8] Integrate yocto documentation into eclipse
Hi, Rifenbark, Scott M wrote, On 19.07.2012 16:39: Very nice... thanks -Original Message- From: Timo Müller [mailto:m...@timomueller.eu] Sent: Wednesday, July 18, 2012 11:57 PM To: Rifenbark, Scott M Cc: yocto@yoctoproject.org; Timo Mueller Subject: Re: [yocto] [RFC 0/8] Integrate yocto documentation into eclipse Hi, Rifenbark, Scott M wrote, On 18.07.2012 17:03: Hi, This seems like a very cool idea. What about when things change structurally for the Yocto Docs? For example, right now I am restructuring much of the Eclipse information that is in the ADT manual to move it to the development manual as part of an application development flow. It looks like your patch here includes the ADT manual and the Quick Start. The changes I am working on will eventually require the YP development manual as well. I wanted to make sure that it is possible to generate eclipse help from the documentation and integrate it into eclipse. Starting with the development manual and the quick start guide was the obvious choice. But, as I didn't encounter any problems using the docbook eclipse stylesheet on the documentation, I suspect that integrating the other documents is also possible. I will give it a try and let you know about the results. As I suspected I didn't encounter any problems generating eclipse help documentation from all documentation parts (dev-manual, kernel-manual, ...). So it will be straight-forward and easy to add them to the eclipse plugin as well. Scott snip Regards, Timo ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to set environment variables inside a recipe?
On Thursday 19 July 2012 18:16:45 Bodke, Kishore K wrote:
The driver needs a bunch of environmental variables to be set ( specific to
driver only ) to build.
Right now to move forward I am doing like below in my recipe to build it.
export AAA = ${S}
export BBB = ${B}
export CCC = {S}/build-system
export DDD = {S}/env-files
Is this right way to do? Are there any other ways to set the environment
variables inside a recipe?
This is valid; I would recommend setting them within the function though (e.g.
do_configure) rather than at the recipe level, assuming that works for your
case.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] beagleboard not booting yacto 1.2.1
Hello, git clone -b denzil git://git.yoctoproject.org/poky.git Yocto Project 1.2.1 The default beagleboard kernel 3.0 would not find the mmc as in Yocto Project 1.2 modified the file meta-yocto/conf/machine/beagleboard.conf PREFERRED_VERSION_linux-yocto ?= 3.0% -- PREFERRED_VERSION_linux-yocto ?= 3.2% git status # On branch denzil # Changes not staged for commit: # (use git add file... to update what will be committed) # (use git checkout -- file... to discard changes in working directory) # #modified: meta-yocto/conf/machine/beagleboard.conf # # Untracked files: # (use git add file... to include in what will be committed) # #build/ no changes added to commit (use git add and/or git commit -a) MACHINE=beagleboard bitbake -v -D -D -D core-image-sato mkfs.vfat -F 16 -n boot /dev/sdb1 /dev/sdb1 W95 FAT32 (LBA) (Bootable) mke2fs -j -L rootfs /dev/sdb2 /dev/sdb2 Ext3 (version 1.0) cd /home/vidal/poky/build/tmp/deploy/images cp MLO-beagleboard-1.5.0+git1+9f94c6577e3a018b6b75cbe39f32bb331871f915-r0 /run/media/vidal/boot/MLO cp u-boot-beagleboard-v2011.06+git12+b1af6f532e0d348b153d5c148369229d24af361a-r1.bin /run/media/vidal/boot/u-boot.bin cp uImage-3.2.18+git1+49f931bc294d5b6be60502bbd448cff5aa766235_1+90e3138c5a2a390dd6ddf2ed84fe5a9756d43397-r1-beagleboard-20120720032419.bin /run/media/vidal/boot/uImage cp /home/vidal/uEnv.txt /run/media/vidal/boot/ cd /run/media/vidal/rootfs/ tar jxf /home/vidal/poky/build/tmp/deploy/images/core-image-sato-beagleboard-20120720032419.rootfs.tar.bz2 * - * Qodem 0.1.2 Capture Generated Fri, 20 Jul 2012 06:02:09 -0600 BEGIN * - * Texas Instruments X-Loader 1.5.0 (Jul 19 2012 - 17:05:29) Beagle xM Reading boot sector Loading u-boot.bin from mmc U-Boot 2011.06 (Jul 19 2012 - 21:25:33) OMAP3630/3730-GP ES2.1, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz OMAP3 Beagle board + LPDDR/NAND I2C: ready DRAM: 512 MiB NAND: 0 MiB MMC: OMAP SD/MMC: 0 *** Warning - readenv() failed, using default environment In:serial Out: serial Err: serial Beagle unknown 0x02 No EEPROM on expansion board Die ID #15829ff80160a7450b02602d Hit any key to stop autoboot: 10 9 8 7 6 5 4 3 2 1 0 SD/MMC found on device 0 reading uEnv.txt 130 bytes read Importing environment from mmc ... reading uImage 3375856 bytes read Booting from mmc ... ## Booting kernel from Legacy Image at 8200 ... Image Name: Linux-3.2.9-yocto-standard Image Type: ARM Linux Kernel Image (uncompressed) Data Size:3375792 Bytes = 3.2 MiB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. Initializing cgroup subsys cpuset Initializing cgroup subsys cpu Linux version 3.2.9-yocto-standard (vi...@ws009.swbell.net) (gcc version 4.6.4 20120303 (prerelease) (GCC) ) #1 Thu Jul 19 21:30:00 MDT 2012 CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7d CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache Machine: OMAP3 Beagle Board Reserving 16777216 bytes SDRAM for VRAM Memory policy: ECC disabled, Data cache writeback OMAP3630 ES1.2 (l2cache iva sgx neon isp 192mhz_clk ) Clocking rate (Crystal/Core/MPU): 26.0/332/600 MHz Built 1 zonelists in Zone order, mobility grouping on. Total pages: 125952 Kernel command line: console=tty0 console=ttyO2,115200n8 mpurate=auto vram=16M omapfb.mode=dvi:hd720 omapfb.vram=0:8M,1:4M,2:4M omapfb.debug=y omapdss.def_disp=dv i root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait PID hash table entries: 2048 (order: 1, 8192 bytes) Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) allocated 2097152 bytes of page_cgroup please try 'cgroup_disable=memory' option if you don't want memory cgroups Memory: 496MB = 496MB total Memory: 493816k/493816k available, 30472k reserved, 0K highmem Virtual kernel memory layout: vector : 0x - 0x1000 ( 4 kB) fixmap : 0xfff0 - 0xfffe ( 896 kB) vmalloc : 0xe080 - 0xf800 ( 376 MB) lowmem : 0xc000 - 0xe000 ( 512 MB) modules : 0xbf00 - 0xc000 ( 16 MB) .text : 0xc0008000 - 0xc06540a4 (6449 kB) .init : 0xc0655000 - 0xc06ab000 ( 344 kB) .data : 0xc06ac000 - 0xc0710868 ( 403 kB) .bss : 0xc071088c - 0xc075486c ( 272 kB) SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 NR_IRQS:410 IRQ: Found an INTC at 0xfa20 (revision 4.0) with 96 interrupts Total of 96 interrupts on 1 active controller OMAP clockevent source: GPTIMER12 at 32768 Hz sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 131071999ms Console: colour dummy device 80x30 console [tty0] enabled Calibrating delay loop... 503.12 BogoMIPS (lpj=1966080) pid_max: default: 32768 minimum: 301 Security Framework initialized Mount-cache hash table entries: 512 Initializing cgroup subsys debug
Re: [yocto] [RFC 0/8] Integrate yocto documentation into eclipse
This will be a nice feature. Thanks! Scott -Original Message- From: Timo Müller [mailto:m...@timomueller.eu] Sent: Thursday, July 19, 2012 11:41 PM To: Rifenbark, Scott M Cc: yocto@yoctoproject.org; Timo Mueller Subject: Re: [yocto] [RFC 0/8] Integrate yocto documentation into eclipse Hi, Rifenbark, Scott M wrote, On 19.07.2012 16:39: Very nice... thanks -Original Message- From: Timo Müller [mailto:m...@timomueller.eu] Sent: Wednesday, July 18, 2012 11:57 PM To: Rifenbark, Scott M Cc: yocto@yoctoproject.org; Timo Mueller Subject: Re: [yocto] [RFC 0/8] Integrate yocto documentation into eclipse Hi, Rifenbark, Scott M wrote, On 18.07.2012 17:03: Hi, This seems like a very cool idea. What about when things change structurally for the Yocto Docs? For example, right now I am restructuring much of the Eclipse information that is in the ADT manual to move it to the development manual as part of an application development flow. It looks like your patch here includes the ADT manual and the Quick Start. The changes I am working on will eventually require the YP development manual as well. I wanted to make sure that it is possible to generate eclipse help from the documentation and integrate it into eclipse. Starting with the development manual and the quick start guide was the obvious choice. But, as I didn't encounter any problems using the docbook eclipse stylesheet on the documentation, I suspect that integrating the other documents is also possible. I will give it a try and let you know about the results. As I suspected I didn't encounter any problems generating eclipse help documentation from all documentation parts (dev-manual, kernel-manual, ...). So it will be straight-forward and easy to add them to the eclipse plugin as well. Scott snip Regards, Timo ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH] mpc8315: build u-boot v2012.04 by default.
On Thu, 2012-07-19 at 20:01 -0400, Paul Gortmaker wrote: Validated on real hardware: U-Boot 2012.04.01 (Jun 29 2012 - 13:48:03)MPC83XX Reset Status: Software Hard, External/Internal Soft, External/Internal Hard CPU: e300c3, MPC8315E, Rev: 1.2 at 400 MHz, CSB: 133.333 MHz Board: Freescale MPC8315ERDB Rev 1.0 I2C: ready DRAM: 128 MiB (DDR2, 32-bit, ECC off, 266.667 MHz) Flash: 8 MiB NAND: 32 MiB PCIE0: No link PCIE1: No link In:serial Out: serial Err: serial Net: eTSEC0, eTSEC1 Hit any key to stop autoboot: 0 [YOCTO #943] Signed-off-by: Paul Gortmaker paul.gortma...@windriver.com --- [Resending, since the OE core changes this depended on are now in, and having an old u-boot _may_ also be the cause of YOCTO #2775 ] Merged to master, thanks. Richard ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 0/1] meta-intel: emgd package reorder fix
From: Tom Zanussi tom.zanu...@intel.com
The recent package reorder changes broke emgd - this patch fixes
that and gets crownbay et al graphics working again.
The following changes since commit 41d385015243dc02f8eea96a3ec3198dae7d2d27:
Khem Raj (1):
va-intel.bb: Add compatible host x86/x86_64
are available in the git repository at:
git://git.yoctoproject.org/meta-intel.git tzanussi/emgd-package-reorder-fix
http://git.yoctoproject.org/cgit.cgi//log/?h=tzanussi/emgd-package-reorder-fix
Tom Zanussi (1):
emgd-driver-bin: remove FILES_${PN}-dev addition
.../xorg-xserver/emgd-driver-bin_1.10.bb |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 1/1] emgd-driver-bin: remove FILES_${PN}-dev addition
From: Tom Zanussi tom.zanu...@intel.com
The package reordering patches exposed a problem in that the files
specified in the FILES_${PN}-dev shouldn't really be put in the -dev
package in the first place - this removes them.
Signed-off-by: Tom Zanussi tom.zanu...@intel.com
---
.../xorg-xserver/emgd-driver-bin_1.10.bb |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/common/recipes-graphics/xorg-xserver/emgd-driver-bin_1.10.bb
b/common/recipes-graphics/xorg-xserver/emgd-driver-bin_1.10.bb
index 53a43cd..5779e5d 100644
--- a/common/recipes-graphics/xorg-xserver/emgd-driver-bin_1.10.bb
+++ b/common/recipes-graphics/xorg-xserver/emgd-driver-bin_1.10.bb
@@ -7,7 +7,7 @@ to LICENSE_FLAGS_WHITELIST += \License_emgd-driver-bin_1.10\
to your \
local.conf in order to enable it in a build.
LICENSE = Intel-binary-only
LICENSE_FLAGS = license_${PN}_${PV}
-PR = r0
+PR = r1
EMGD_LIC_DIR = IEMGD_HEAD_Linux/License
EMGD_RPM_DIR = IEMGD_HEAD_Linux/MeeGo1.2
@@ -26,7 +26,6 @@ SRC_URI[sha256sum] =
acea5f0f93a31553553428623c007d7ed0c604cf715fd87dfe075751da
INSANE_SKIP_${PN} = ldflags
FILES_${PN} += ${libdir}/dri ${libdir}/gstreamer-0.10
${libdir}/xorg/modules/drivers
-FILES_${PN}-dev += ${libdir}/dri ${libdir}/xorg/modules/drivers
FILES_${PN}-dbg += ${libdir}/xorg/modules/drivers/.debug ${libdir}/dri/.debug
S = ${WORKDIR}/${EMGD_RPM_DIR}
--
1.7.0.4
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-intel][PATCH] va-intel.bb: Add compatible host x86/x86_64
On Thu, 2012-07-19 at 19:53 -0700, Khem Raj wrote:
This lets meta-intel to play well in multi-bsp
setup
Pulled into meta-intel/master, thanks!
Tom
Signed-off-by: Khem Raj raj.k...@gmail.com
---
common/recipes-multimedia/libva/va-intel.bb |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/common/recipes-multimedia/libva/va-intel.bb
b/common/recipes-multimedia/libva/va-intel.bb
index 3ce857a..69633aa 100644
--- a/common/recipes-multimedia/libva/va-intel.bb
+++ b/common/recipes-multimedia/libva/va-intel.bb
@@ -18,3 +18,4 @@ ALLOW_EMPTY = 1
RDEPENDS_va-intel = \
${VA_IMPL} \
+COMPATIBLE_HOST = '(i.86|x86_64).*-linux*'
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to set environment variables inside a recipe?
-Original Message-
From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com]
Sent: Friday, July 20, 2012 3:14 AM
To: Bodke, Kishore K
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] How to set environment variables inside a recipe?
On Thursday 19 July 2012 18:16:45 Bodke, Kishore K wrote:
The driver needs a bunch of environmental variables to be set ( specific to
driver only ) to build.
Right now to move forward I am doing like below in my recipe to build it.
export AAA = ${S}
export BBB = ${B}
export CCC = {S}/build-system
export DDD = {S}/env-files
Is this right way to do? Are there any other ways to set the environment
variables inside a recipe?
This is valid; I would recommend setting them within the function though (e.g.
do_configure) rather than at the recipe level, assuming that works for your
case.
If I set outside the do_configure it builds fine.
But If I do inside
do_confiugre() {
export AAA = ${S}
export BBB = ${B}
export CCC = {S}/build-system
export DDD = {S}/env-files
}
run.do_configure.20832: line 78: export: `=': not a valid identifier
NOTE: task do_configure: Failed
Is the syntax wrong here? What is the correct syntax?
Thanks
Kishore.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to set environment variables inside a recipe?
On Fri, 20 Jul 2012, Bodke, Kishore K wrote:
-Original Message-
From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com]
Sent: Friday, July 20, 2012 3:14 AM
To: Bodke, Kishore K
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] How to set environment variables inside a recipe?
On Thursday 19 July 2012 18:16:45 Bodke, Kishore K wrote:
The driver needs a bunch of environmental variables to be set ( specific to
driver only ) to build.
Right now to move forward I am doing like below in my recipe to build it.
export AAA = ${S}
export BBB = ${B}
export CCC = {S}/build-system
export DDD = {S}/env-files
Is this right way to do? Are there any other ways to set the environment
variables inside a recipe?
This is valid; I would recommend setting them within the function though
(e.g.
do_configure) rather than at the recipe level, assuming that works for your
case.
If I set outside the do_configure it builds fine.
But If I do inside
do_confiugre() {
export AAA = ${S}
export BBB = ${B}
export CCC = {S}/build-system
export DDD = {S}/env-files
}
run.do_configure.20832: line 78: export: `=': not a valid identifier
NOTE: task do_configure: Failed
pretty sure you can't have spaces around the =.
rday
--
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to set environment variables inside a recipe?
-Original Message-
From: Robert P. J. Day [mailto:rpj...@crashcourse.ca]
Sent: Friday, July 20, 2012 10:13 AM
To: Bodke, Kishore K
Cc: Paul Eggleton; yocto@yoctoproject.org
Subject: Re: [yocto] How to set environment variables inside a recipe?
On Fri, 20 Jul 2012, Bodke, Kishore K wrote:
-Original Message-
From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com]
Sent: Friday, July 20, 2012 3:14 AM
To: Bodke, Kishore K
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] How to set environment variables inside a recipe?
On Thursday 19 July 2012 18:16:45 Bodke, Kishore K wrote:
The driver needs a bunch of environmental variables to be set ( specific
to
driver only ) to build.
Right now to move forward I am doing like below in my recipe to build it.
export AAA = ${S}
export BBB = ${B}
export CCC = {S}/build-system
export DDD = {S}/env-files
Is this right way to do? Are there any other ways to set the environment
variables inside a recipe?
This is valid; I would recommend setting them within the function though
(e.g.
do_configure) rather than at the recipe level, assuming that works for your
case.
If I set outside the do_configure it builds fine.
But If I do inside
do_confiugre() {
export AAA = ${S}
export BBB = ${B}
export CCC = {S}/build-system
export DDD = {S}/env-files
}
run.do_configure.20832: line 78: export: `=': not a valid identifier
NOTE: task do_configure: Failed
pretty sure you can't have spaces around the =.
Yes, the spaces was an issue.
Works fine now.
Thanks
Kishore.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] beagleboard not booting yacto1.2.1
Hello, I have done a build on a Fedora17 and CentOS6. using yacto1.2.1 the default kernel is Linux-3.0.32-yocto-standard This was occurring in yacto1.2 also In yacto1.2 I tried the 3.4 kernel and it would boot further and I could ssh into the beagleboard. With yacto 1.2.1 I tried 3.2 kernel but it no get to where I could ssh into the beagleboard still not get the sato display in either ver. Console: switching to colour frame buffer device 80x25 regulator_init_complete: VDAC: incomplete constraints, leaving on twl_rtc twl_rtc: setting systemclock to 2000-01-01 00:00:00 UTC (946684800) Waitingfor root device /dev/mmcblk0p2... mmc0: new SDHC card at address b368 mmcblk0: mmc0:b368 SDU16 14.9 GiB (ro) mmcblk0: p1 p2 VFS: Cannot open root device mmcblk0p2 or unknown-block(179,2) Please append a correct root=boot option; here are the available partitions: b30015637504 mmcblk0 driver: mmcblk b301 66544 mmcblk0p1 ----0mmcblk0p1 b30215570944 mmcblk0p2 ----0mmcblk0p2 VFS: Unable to mount root fs onunknown-block(179,2) User configuration error - no valid root filesystem found Kernel panic - not syncing: Invalid configuration from end user prevents continu ing [c006381c] (unwind_backtrace+0x0/0xec) from [c044560c] (dump_stack+0x20/0x24 ) [c044560c] (dump_stack+0x20/0x24) from [c0445854] (panic+0x64/0x180) [c0445854] (panic+0x64/0x180) from [c0008ea4] (mount_block_root+0x1e8/0x234) [c0008ea4] (mount_block_root+0x1e8/0x234) from [c00090c8] (mount_root+0xf0/0 x110) [c00090c8] (mount_root+0xf0/0x110) from [c0009254] (prepare_namespace+0x16c/ 0x1cc) [c0009254] (prepare_namespace+0x16c/0x1cc) from [c0008a9c] (kernel_init+0x12 c/0x160) [c0008a9c] (kernel_init+0x12c/0x160) from [c005e428] (kernel_thread_exit+0x0 In the report for release 1.2.1 this stated that the beagleboard tested okay.' Is there any other information that I might provide about my builds? Thanks for any help. /0x8) ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] nothing building under denzil-7.0.1
There must be some basic thing I'm missing. Nothing that I used to build under denzil 7.0 will now build under denzil 7.0.1 or tracking the denzil branch. Are all the BSPs required to be updated to 7.0.1 before you can run? I'd thought I'd check before I post a bunch of log files. I just downloaded the poky 7.0.1 tarball and cd'ed to that untarred directory and untarred the 7.0 Intel BSPs. There must be a step I'm missing. otherwise this would not have gotten thru testing before deployment. Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] nothing building under denzil-7.0.1
On 07/20/2012 01:11 PM, Jim Abernathy wrote: There must be some basic thing I'm missing. Nothing that I used to build under denzil 7.0 will now build under denzil 7.0.1 or tracking the denzil branch. Are all the BSPs required to be updated to 7.0.1 before you can run? I'd thought I'd check before I post a bunch of log files. I just downloaded the poky 7.0.1 tarball and cd'ed to that untarred directory and untarred the 7.0 Intel BSPs. There must be a step I'm missing. otherwise this would not have gotten thru testing before deployment. Jim A Hi Jim, We need more specific information about the error(s) you're seeing. We've done extensive QA with 7.0.1 and meta-intel, so I imagine there must be a step you've forgotten. For example, you are using the denzil branch of meta-intel, right? Scott -- Scott Garman Embedded Linux Engineer - Yocto Project Intel Open Source Technology Center ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] nothing building under denzil-7.0.1
On 07/20/2012 04:29 PM, Scott Garman wrote: On 07/20/2012 01:11 PM, Jim Abernathy wrote: There must be some basic thing I'm missing. Nothing that I used to build under denzil 7.0 will now build under denzil 7.0.1 or tracking the denzil branch. Are all the BSPs required to be updated to 7.0.1 before you can run? I'd thought I'd check before I post a bunch of log files. I just downloaded the poky 7.0.1 tarball and cd'ed to that untarred directory and untarred the 7.0 Intel BSPs. There must be a step I'm missing. otherwise this would not have gotten thru testing before deployment. Jim A Hi Jim, We need more specific information about the error(s) you're seeing. We've done extensive QA with 7.0.1 and meta-intel, so I imagine there must be a step you've forgotten. For example, you are using the denzil branch of meta-intel, right? Scott I think it maybe that old problem with the n450 SRCREC being blank in the linux-yocto bbappend file. Obviously that BSP didn't get fixed before 7.0.1 was deployed. I'll put in the ones I used to patch in and see if it works. Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] nothing building under denzil-7.0.1
On Fri, 2012-07-20 at 16:35 -0400, Jim Abernathy wrote: On 07/20/2012 04:29 PM, Scott Garman wrote: On 07/20/2012 01:11 PM, Jim Abernathy wrote: There must be some basic thing I'm missing. Nothing that I used to build under denzil 7.0 will now build under denzil 7.0.1 or tracking the denzil branch. Are all the BSPs required to be updated to 7.0.1 before you can run? I'd thought I'd check before I post a bunch of log files. I just downloaded the poky 7.0.1 tarball and cd'ed to that untarred directory and untarred the 7.0 Intel BSPs. There must be a step I'm missing. otherwise this would not have gotten thru testing before deployment. Jim A Hi Jim, We need more specific information about the error(s) you're seeing. We've done extensive QA with 7.0.1 and meta-intel, so I imagine there must be a step you've forgotten. For example, you are using the denzil branch of meta-intel, right? Scott I think it maybe that old problem with the n450 SRCREC being blank in the linux-yocto bbappend file. Obviously that BSP didn't get fixed before 7.0.1 was deployed. I'll put in the ones I used to patch in and see if it works. I updated the n450 in both the denzil and master meta-intel branches, but the tarball still needs to be updated with that fix. Is this the problem you're seeing, or are there other problems you're seeing with this and/or the other meta-intel BSPs? Tom Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] nothing building under denzil-7.0.1
On 07/20/2012 04:39 PM, Tom Zanussi wrote: On Fri, 2012-07-20 at 16:35 -0400, Jim Abernathy wrote: On 07/20/2012 04:29 PM, Scott Garman wrote: On 07/20/2012 01:11 PM, Jim Abernathy wrote: There must be some basic thing I'm missing. Nothing that I used to build under denzil 7.0 will now build under denzil 7.0.1 or tracking the denzil branch. Are all the BSPs required to be updated to 7.0.1 before you can run? I'd thought I'd check before I post a bunch of log files. I just downloaded the poky 7.0.1 tarball and cd'ed to that untarred directory and untarred the 7.0 Intel BSPs. There must be a step I'm missing. otherwise this would not have gotten thru testing before deployment. Jim A Hi Jim, We need more specific information about the error(s) you're seeing. We've done extensive QA with 7.0.1 and meta-intel, so I imagine there must be a step you've forgotten. For example, you are using the denzil branch of meta-intel, right? Scott I think it maybe that old problem with the n450 SRCREC being blank in the linux-yocto bbappend file. Obviously that BSP didn't get fixed before 7.0.1 was deployed. I'll put in the ones I used to patch in and see if it works. I updated the n450 in both the denzil and master meta-intel branches, but the tarball still needs to be updated with that fix. Is this the problem you're seeing, or are there other problems you're seeing with this and/or the other meta-intel BSPs? Tom I should know shortly. I patched the n450 like I did before. I forgot that BSP didn't get updated when denzil 7.0.1 came out. Duh! If you have it fixed in Denzil and master branch, I'll test that as well. Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] nothing building under denzil-7.0.1
On Fri, 2012-07-20 at 16:42 -0400, Jim Abernathy wrote: On 07/20/2012 04:39 PM, Tom Zanussi wrote: On Fri, 2012-07-20 at 16:35 -0400, Jim Abernathy wrote: On 07/20/2012 04:29 PM, Scott Garman wrote: On 07/20/2012 01:11 PM, Jim Abernathy wrote: There must be some basic thing I'm missing. Nothing that I used to build under denzil 7.0 will now build under denzil 7.0.1 or tracking the denzil branch. Are all the BSPs required to be updated to 7.0.1 before you can run? I'd thought I'd check before I post a bunch of log files. I just downloaded the poky 7.0.1 tarball and cd'ed to that untarred directory and untarred the 7.0 Intel BSPs. There must be a step I'm missing. otherwise this would not have gotten thru testing before deployment. Jim A Hi Jim, We need more specific information about the error(s) you're seeing. We've done extensive QA with 7.0.1 and meta-intel, so I imagine there must be a step you've forgotten. For example, you are using the denzil branch of meta-intel, right? Scott I think it maybe that old problem with the n450 SRCREC being blank in the linux-yocto bbappend file. Obviously that BSP didn't get fixed before 7.0.1 was deployed. I'll put in the ones I used to patch in and see if it works. I updated the n450 in both the denzil and master meta-intel branches, but the tarball still needs to be updated with that fix. Is this the problem you're seeing, or are there other problems you're seeing with this and/or the other meta-intel BSPs? Tom I should know shortly. I patched the n450 like I did before. I forgot that BSP didn't get updated when denzil 7.0.1 came out. Duh! If you have it fixed in Denzil and master branch, I'll test that as well. Yes, you should be fine using the BSP branches from the git repo, but steer clear of the tarball until it gets updated... Tom Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] nothing building under denzil-7.0.1
On 07/20/2012 01:48 PM, Tom Zanussi wrote: On Fri, 2012-07-20 at 16:42 -0400, Jim Abernathy wrote: On 07/20/2012 04:39 PM, Tom Zanussi wrote: If you have it fixed in Denzil and master branch, I'll test that as well. Yes, you should be fine using the BSP branches from the git repo, but steer clear of the tarball until it gets updated... Sorry, I dropped the ball on this. Will look to get that updated. -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] nothing building under denzil-7.0.1
On Fri, 2012-07-20 at 15:39 -0500, Tom Zanussi wrote: On Fri, 2012-07-20 at 16:35 -0400, Jim Abernathy wrote: On 07/20/2012 04:29 PM, Scott Garman wrote: On 07/20/2012 01:11 PM, Jim Abernathy wrote: There must be some basic thing I'm missing. Nothing that I used to build under denzil 7.0 will now build under denzil 7.0.1 or tracking the denzil branch. Are all the BSPs required to be updated to 7.0.1 before you can run? I'd thought I'd check before I post a bunch of log files. I just downloaded the poky 7.0.1 tarball and cd'ed to that untarred directory and untarred the 7.0 Intel BSPs. There must be a step I'm missing. otherwise this would not have gotten thru testing before deployment. Jim A Hi Jim, We need more specific information about the error(s) you're seeing. We've done extensive QA with 7.0.1 and meta-intel, so I imagine there must be a step you've forgotten. For example, you are using the denzil branch of meta-intel, right? Scott I think it maybe that old problem with the n450 SRCREC being blank in the linux-yocto bbappend file. Obviously that BSP didn't get fixed before 7.0.1 was deployed. I'll put in the ones I used to patch in and see if it works. I updated the n450 in both the denzil and master meta-intel branches, but the tarball still needs to be updated with that fix. Is this the problem you're seeing, or are there other problems you're seeing with this and/or the other meta-intel BSPs? As a sanity check, I just now downloaded the denzil-7.0.1 tarball and the denzil sugarbay tarball and built successfully without any problems. Tom Tom Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] INSANE_SKIP
Is there a way to skip a QA check for more than one package or all packages?
I'd like to avoid having to add a INSANE_SKIP_${PN} += ldflags for
every package that fails due to ERROR: QA Issue: No GNU_HASH in the
elf binary.
There are gobs of python and perl packages failing with this error
when I try to build a distro.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] nothing building under denzil-7.0.1
On 07/20/2012 04:48 PM, Tom Zanussi wrote: On Fri, 2012-07-20 at 16:42 -0400, Jim Abernathy wrote: On 07/20/2012 04:39 PM, Tom Zanussi wrote: On Fri, 2012-07-20 at 16:35 -0400, Jim Abernathy wrote: On 07/20/2012 04:29 PM, Scott Garman wrote: On 07/20/2012 01:11 PM, Jim Abernathy wrote: There must be some basic thing I'm missing. Nothing that I used to build under denzil 7.0 will now build under denzil 7.0.1 or tracking the denzil branch. Are all the BSPs required to be updated to 7.0.1 before you can run? I'd thought I'd check before I post a bunch of log files. I just downloaded the poky 7.0.1 tarball and cd'ed to that untarred directory and untarred the 7.0 Intel BSPs. There must be a step I'm missing. otherwise this would not have gotten thru testing before deployment. Jim A Hi Jim, We need more specific information about the error(s) you're seeing. We've done extensive QA with 7.0.1 and meta-intel, so I imagine there must be a step you've forgotten. For example, you are using the denzil branch of meta-intel, right? Scott I think it maybe that old problem with the n450 SRCREC being blank in the linux-yocto bbappend file. Obviously that BSP didn't get fixed before 7.0.1 was deployed. I'll put in the ones I used to patch in and see if it works. I updated the n450 in both the denzil and master meta-intel branches, but the tarball still needs to be updated with that fix. Is this the problem you're seeing, or are there other problems you're seeing with this and/or the other meta-intel BSPs? Tom I should know shortly. I patched the n450 like I did before. I forgot that BSP didn't get updated when denzil 7.0.1 came out. Duh! If you have it fixed in Denzil and master branch, I'll test that as well. Yes, you should be fine using the BSP branches from the git repo, but steer clear of the tarball until it gets updated... Tom I don't have something right yet. on poky, I'm up to date on denzil branch. Also denzil branch on meta-intel. I'm getting a build failure on the yocto kernel. Log file below: DEBUG: Trying Upstream DEBUG: Running export HOME=/home/jim; export SSH_AGENT_PID=1456; export SSH_AUTH_SOCK=/tmp/keyring-aKbQKk/ssh; export GIT_CONFIG=/build/n450-denzil/tmp/sysroots/x86_64-linux/etc/gitconfig; export PATH=/build/n450-denzil/tmp/sysroots/x86_64-linux/usr/bin/core2-poky-linux:/build/n450-denzil/tmp/sysroots/n450/usr/bin/crossscripts:/build/n450-denzil/tmp/sysroots/x86_64-linux/usr/sbin:/build/n450-denzil/tmp/sysroots/x86_64-linux/usr/bin:/build/n450-denzil/tmp/sysroots/x86_64-linux/sbin:/build/n450-denzil/tmp/sysroots/x86_64-linux//bin:/home/jim/poky/scripts:/home/jim/poky/bitbake/bin/:/home/jim/poky/scripts:/home/jim/poky/bitbake/bin/:/home/jim/poky-denzil-7.0.1/scripts:/home/jim/poky-denzil-7.0.1/bitbake/bin/:/home/jim/poky-denzil-7.0.1/scripts:/home/jim/poky-denzil-7.0.1/bitbake/bin/:/home/jim/poky-denzil-7.0.1/scripts:/home/jim/poky-denzil-7.0.1/bitbake/bin/:/home/jim/poky/scripts:/home/jim/poky/bitbake/bin/:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/jim/poky/scripts; git log --pretty=oneline -n 1 8b8cfaaab2b8d79ac56e8c9a85bad9ae7bca399c -- 2 /dev/null | wc -l DEBUG: Running export HOME=/home/jim; export SSH_AGENT_PID=1456; export SSH_AUTH_SOCK=/tmp/keyring-aKbQKk/ssh; export GIT_CONFIG=/build/n450-denzil/tmp/sysroots/x86_64-linux/etc/gitconfig; export PATH=/build/n450-denzil/tmp/sysroots/x86_64-linux/usr/bin/core2-poky-linux:/build/n450-denzil/tmp/sysroots/n450/usr/bin/crossscripts:/build/n450-denzil/tmp/sysroots/x86_64-linux/usr/sbin:/build/n450-denzil/tmp/sysroots/x86_64-linux/usr/bin:/build/n450-denzil/tmp/sysroots/x86_64-linux/sbin:/build/n450-denzil/tmp/sysroots/x86_64-linux//bin:/home/jim/poky/scripts:/home/jim/poky/bitbake/bin/:/home/jim/poky/scripts:/home/jim/poky/bitbake/bin/:/home/jim/poky-denzil-7.0.1/scripts:/home/jim/poky-denzil-7.0.1/bitbake/bin/:/home/jim/poky-denzil-7.0.1/scripts:/home/jim/poky-denzil-7.0.1/bitbake/bin/:/home/jim/poky-denzil-7.0.1/scripts:/home/jim/poky-denzil-7.0.1/bitbake/bin/:/home/jim/poky/scripts:/home/jim/poky/bitbake/bin/:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/jim/poky/scripts; git log --pretty=oneline -n 1 49f931bc294d5b6be60502bbd448cff5aa766235 -- 2 /dev/null | wc -l DEBUG: Running export HOME=/home/jim; export SSH_AGENT_PID=1456; export SSH_AUTH_SOCK=/tmp/keyring-aKbQKk/ssh; export GIT_CONFIG=/build/n450-denzil/tmp/sysroots/x86_64-linux/etc/gitconfig; export
Re: [yocto] nothing building under denzil-7.0.1
On 07/20/2012 03:12 PM, Jim Abernathy wrote: git://git.yoctoproject.org/linux-yocto-3.2 could not be run: None ERROR: Function failed: Fetcher failure for URL: 'git://git.yoctoproject.org/linux-yocto-3.2;protocol=git;bareclone=1;branch=standard/default/common-pc/atom-pc,meta;name=machine,meta'. Unable to fetch URL from any source. Can you clone this from the shell? -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Cross referencing git commit SHA info in commit logs
Hello, I have seen some commit logs referring to poky commits but are applied to OE-Core and there might be vice versa case too. In general I don't see an issue when there is a commit SHA id in log message but please add the project info to it unless so someone can go and look for it in particular repo eg, poky/id OE-Core/id meta-oe/id oe.dev/id would make it a bit better Thanks -Khem ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] ERROR: Function failed: do_install_perf
Hi, I suddenly started to get the following error when running bitbake. I am using Denzil branches of poky, meta-intel and poky-extras. I installed libper-dev as suggested by the error message, but it made no difference. Any suggestions ? Thanks Rahul ERROR: Function failed: do_install_perf (see /home/rsaxena/YoctoWork3x/cedartraiv12p/tmp/work/cedartrail-poky-linux/linux-yocto-3.0.32+git1+46e8fc2bbbe73514e8d99101adaaa373f760ffa7_1+81fd8c307997aff37916828dc8b4ef72f5d35a94-r4/temp/log.do_install_perf.69672 for further information) NOTE: make -C /home/rsaxena/YoctoWork3x/cedartraiv12p/tmp/work/cedartrail-poky-linux/linux-yocto-3.0.32+git1+46e8fc2bbbe73514e8d99101adaaa373f760ffa7_1+81fd8c307997aff37916828dc8b4ef72f5d35a94-r4/linux/tools/perf CC=i586-poky-linux-gcc -m32-march=core2 -msse3 -mtune=generic -mfpmath=sse --sysroot=/home/rsaxena/YoctoWork3x/cedartraiv12p/tmp/sysroots/cedartrail LD=i586-poky-linux-ld --sysroot=/home/rsaxena/YoctoWork3x/cedartraiv12p/tmp/sysroots/cedartrail prefix=/usr DESTDIR=/home/rsaxena/YoctoWork3x/cedartraiv12p/tmp/work/cedartrail-poky-linux/linux-yocto-3.0.32+git1+46e8fc2bbbe73514e8d99101adaaa373f760ffa7_1+81fd8c307997aff37916828dc8b4ef72f5d35a94-r4/image install NO_NEWT=1 NO_DWARF=1 make: Entering directory `/home/rsaxena/YoctoWork3x/cedartraiv12p/tmp/work/cedartrail-poky-linux/linux-yocto-3.0.32+git1+46e8fc2bbbe73514e8d99101adaaa373f760ffa7_1+81fd8c307997aff37916828dc8b4ef72f5d35a94-r4/linux/tools/perf' Makefile:484: libperl not found, disables Perl scripting support. Please install libperl-dev or perl-devel * new build flags or prefix CC perf.o CC builtin-annotate.o CC builtin-bench.o CC bench/sched-messaging.o CC bench/sched-pipe.o CC bench/mem-memcpy.o CC builtin-diff.o CC builtin-evlist.o CC builtin-help.o CC builtin-sched.o CC builtin-buildid-list.o CC builtin-buildid-cache.o CC builtin-list.o CC builtin-record.o CC builtin-report.o CC builtin-stat.o CC builtin-timechart.o CC builtin-top.o CC builtin-script.o CC builtin-probe.o CC builtin-kmem.o CC builtin-lock.o CC builtin-kvm.o CC builtin-test.o CC builtin-inject.o CC util/abspath.o CC util/alias.o CC util/annotate.o CC util/build-id.o CC util/config.o CC util/ctype.o CC util/debugfs.o CC util/environment.o CC util/event.o CC util/evlist.o CC util/evsel.o CC util/exec_cmd.o CC util/help.o CC util/levenshtein.o CC util/parse-options.o CC util/parse-events.o CC util/path.o CC util/rbtree.o CC util/bitmap.o CC util/hweight.o CC util/run-command.o CC util/quote.o CC util/strbuf.o CC util/string.o CC util/strlist.o CC util/strfilter.o CC util/top.o CC util/usage.o CC util/wrapper.o CC util/sigchain.o CC util/symbol.o CC util/color.o CC util/pager.o CC util/header.o CC util/callchain.o CC util/values.o CC util/debug.o CC util/map.o CC util/pstack.o CC util/session.o CC util/thread.o CC util/thread_map.o CC util/trace-event-parse.o CC util/trace-event-read.o CC util/trace-event-info.o CC util/trace-event-scripting.o CC util/svghelper.o CC util/sort.o CC util/hist.o CC util/probe-event.o CC util/util.o CC util/xyarray.o CC util/cpumap.o CC util/cgroup.o CC util/scripting-engines/trace-event-python.o CC scripts/python/Perf-Trace-Util/Context.o AR libperf.a LINK perf GEN python/perf.so Traceback (most recent call last): File util/setup.py, line 6, in module from distutils.command.build_ext import build_ext as _build_ext File /home/rsaxena/YoctoWork3x/cedartraiv12p/tmp/sysroots/x86_64-linux/usr/lib/python2.7/distutils/command/build_ext.py, line 16, in module from distutils.sysconfig import customize_compiler, get_python_version File /home/rsaxena/YoctoWork3x/cedartraiv12p/tmp/sysroots/x86_64-linux/usr/lib/python2.7/distutils/sysconfig.py, line 22, in module PREFIX = os.path.normpath(sys.prefix).replace( os.getenv(BUILD_SYS), os.getenv(HOST_SYS) ) TypeError: expected a character buffer object cp: cannot stat `python_ext_build/lib/perf.so': No such file or directory make: *** [python/perf.so] Error 1 make: Leaving directory `/home/rsaxena/YoctoWork3x/cedartraiv12p/tmp/work/cedartrail-poky-linux/linux-yocto-3.0.32+git1+46e8fc2bbbe73514e8d99101adaaa373f760ffa7_1+81fd8c307997aff37916828dc8b4ef72f5d35a94-r4/linux/tools/perf' ERROR: oe_runmake failed ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] nothing building under denzil-7.0.1
On 07/20/2012 07:02 PM, Darren Hart wrote: On 07/20/2012 03:12 PM, Jim Abernathy wrote: git://git.yoctoproject.org/linux-yocto-3.2 could not be run: None ERROR: Function failed: Fetcher failure for URL: 'git://git.yoctoproject.org/linux-yocto-3.2;protocol=git;bareclone=1;branch=standard/default/common-pc/atom-pc,meta;name=machine,meta'. Unable to fetch URL from any source. Can you clone this from the shell? Okay, I blew away my poky and build directories, but keep my download central directory. Here are the steps. git clone git://git.yoctoproject.org/poky cd poky git clone git://git.yoctoproject.org/meta-intel.git git checkout -b denzil origin/denzil cd meta-intel git checkout -b denzil origin/denzil cd .. . oe-init-build-env /build/n450-new (edit local.conf for parallel options, machine= n450, and DL_DIR) (edit bblayer.conf for meta-intel and meta-intel/meta-n450 layer) bitbake core-image-sato Error console: NOTE: Running task 687 of 4920 (ID: 69, virtual:native:/home/jim/poky/meta/recipes-devtools/prelink/prelink_git.bb, do_unpack) WARNING: Failed to fetch URL git://git.yoctoproject.org/linux-yocto-3.2;protocol=git;bareclone=1;branch=standard/default/common-pc/atom-pc,meta;name=machine,meta ERROR: Fetcher failure: Fetch command export HOME=/home/jim; export SSH_AGENT_PID=1456; export SSH_AUTH_SOCK=/tmp/keyring-aKbQKk/ssh; export GIT_CONFIG=/build/n450-new/tmp/sysroots/x86_64-linux/etc/gitconfig; export PATH=/build/n450-new/tmp/sysroots/x86_64-linux/usr/bin/core2-poky-linux:/build/n450-new/tmp/sysroots/n450/usr/bin/crossscripts:/build/n450-new/tmp/sysroots/x86_64-linux/usr/sbin:/build/n450-new/tmp/sysroots/x86_64-linux/usr/bin:/build/n450-new/tmp/sysroots/x86_64-linux/sbin:/build/n450-new/tmp/sysroots/x86_64-linux//bin:/home/jim/poky/scripts:/home/jim/poky/bitbake/bin/:/home/jim/poky/scripts:/home/jim/poky/bitbake/bin/:/home/jim/poky/scripts:/home/jim/poky/bitbake/bin/:/home/jim/poky-denzil-7.0.1/scripts:/home/jim/poky-denzil-7.0.1/bitbake/bin/:/home/jim/poky-denzil-7.0.1/scripts:/home/jim/poky-denzil-7.0.1/bitbake/bin/:/home/jim/poky-denzil-7.0.1/scripts:/home/jim/poky-denzil-7.0.1/bitbake/bin/:/home/jim/poky/scripts:/home/jim/poky/bitbake/bin/:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/jim/poky/scripts; git remote add --mirror=fetch origin git://git.yoctoproject.org/linux-yocto-3.2 could not be run: None ERROR: Function failed: Fetcher failure for URL: 'git://git.yoctoproject.org/linux-yocto-3.2;protocol=git;bareclone=1;branch=standard/default/common-pc/atom-pc,meta;name=machine,meta'. Unable to fetch URL from any source. ERROR: Logfile of failure stored in: /build/n450-new/tmp/work/n450-poky-linux/linux-yocto-3.2.18+git1+49f931bc294d5b6be60502bbd448cff5aa766235_1+8b8cfaaab2b8d79ac56e8c9a85bad9ae7bca399c-r1/temp/log.do_fetch.12200 NOTE: package linux-yocto-3.2.18+git1+49f931bc294d5b6be60502bbd448cff5aa766235_1+8b8cfaaab2b8d79ac56e8c9a85bad9ae7bca399c-r1: task do_fetch: Failed ERROR: Task 705 (/home/jim/poky/meta/recipes-kernel/linux/linux-yocto_3.2.bb, do_fetch) failed with exit code '1' ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] ERROR: Function failed: do_install_perf
On Sat, 2012-07-21 at 00:02 +, Saxena, Rahul wrote: Hi, I suddenly started to get the following error when running bitbake. I am using Denzil branches of poky, meta-intel and poky-extras. I installed libper-dev as suggested by the error message, but it made no difference. Any suggestions ? I think the meta-kernel-dev with denzil is causing the problem i.e the AUTOREV is causing the tip of linux-yocto-3.0 to get picked up. So just removing poky-extras from your layers should fix the problem. Using the meta-kernel-dev AUTOREV with master should be fine though, and in fact I did update the cedartrail SRCREVs in master to catch the perf updates in linux-yocto-3.0, so advancing them won't hurt anything. I guess master is where you want to make new kernel changes anyway... Tom Thanks Rahul ERROR: Function failed: do_install_perf (see /home/rsaxena/YoctoWork3x/cedartraiv12p/tmp/work/cedartrail-poky-linux/linux-yocto-3.0.32+git1+46e8fc2bbbe73514e8d99101adaaa373f760ffa7_1+81fd8c307997aff37916828dc8b4ef72f5d35a94-r4/temp/log.do_install_perf.69672 for further information) NOTE: make -C /home/rsaxena/YoctoWork3x/cedartraiv12p/tmp/work/cedartrail-poky-linux/linux-yocto-3.0.32+git1+46e8fc2bbbe73514e8d99101adaaa373f760ffa7_1+81fd8c307997aff37916828dc8b4ef72f5d35a94-r4/linux/tools/perf CC=i586-poky-linux-gcc -m32-march=core2 -msse3 -mtune=generic -mfpmath=sse --sysroot=/home/rsaxena/YoctoWork3x/cedartraiv12p/tmp/sysroots/cedartrail LD=i586-poky-linux-ld --sysroot=/home/rsaxena/YoctoWork3x/cedartraiv12p/tmp/sysroots/cedartrail prefix=/usr DESTDIR=/home/rsaxena/YoctoWork3x/cedartraiv12p/tmp/work/cedartrail-poky-linux/linux-yocto-3.0.32+git1+46e8fc2bbbe73514e8d99101adaaa373f760ffa7_1+81fd8c307997aff37916828dc8b4ef72f5d35a94-r4/image install NO_NEWT=1 NO_DWARF=1 make: Entering directory `/home/rsaxena/YoctoWork3x/cedartraiv12p/tmp/work/cedartrail-poky-linux/linux-yocto-3.0.32+git1+46e8fc2bbbe73514e8d99101adaaa373f760ffa7_1+81fd8c307997aff37916828dc8b4ef72f5d35a94-r4/linux/tools/perf' Makefile:484: libperl not found, disables Perl scripting support. Please install libperl-dev or perl-devel * new build flags or prefix CC perf.o CC builtin-annotate.o CC builtin-bench.o CC bench/sched-messaging.o CC bench/sched-pipe.o CC bench/mem-memcpy.o CC builtin-diff.o CC builtin-evlist.o CC builtin-help.o CC builtin-sched.o CC builtin-buildid-list.o CC builtin-buildid-cache.o CC builtin-list.o CC builtin-record.o CC builtin-report.o CC builtin-stat.o CC builtin-timechart.o CC builtin-top.o CC builtin-script.o CC builtin-probe.o CC builtin-kmem.o CC builtin-lock.o CC builtin-kvm.o CC builtin-test.o CC builtin-inject.o CC util/abspath.o CC util/alias.o CC util/annotate.o CC util/build-id.o CC util/config.o CC util/ctype.o CC util/debugfs.o CC util/environment.o CC util/event.o CC util/evlist.o CC util/evsel.o CC util/exec_cmd.o CC util/help.o CC util/levenshtein.o CC util/parse-options.o CC util/parse-events.o CC util/path.o CC util/rbtree.o CC util/bitmap.o CC util/hweight.o CC util/run-command.o CC util/quote.o CC util/strbuf.o CC util/string.o CC util/strlist.o CC util/strfilter.o CC util/top.o CC util/usage.o CC util/wrapper.o CC util/sigchain.o CC util/symbol.o CC util/color.o CC util/pager.o CC util/header.o CC util/callchain.o CC util/values.o CC util/debug.o CC util/map.o CC util/pstack.o CC util/session.o CC util/thread.o CC util/thread_map.o CC util/trace-event-parse.o CC util/trace-event-read.o CC util/trace-event-info.o CC util/trace-event-scripting.o CC util/svghelper.o CC util/sort.o CC util/hist.o CC util/probe-event.o CC util/util.o CC util/xyarray.o CC util/cpumap.o CC util/cgroup.o CC util/scripting-engines/trace-event-python.o CC scripts/python/Perf-Trace-Util/Context.o AR libperf.a LINK perf GEN python/perf.so Traceback (most recent call last): File util/setup.py, line 6, in module from distutils.command.build_ext import build_ext as _build_ext File /home/rsaxena/YoctoWork3x/cedartraiv12p/tmp/sysroots/x86_64-linux/usr/lib/python2.7/distutils/command/build_ext.py, line 16, in module from distutils.sysconfig import customize_compiler, get_python_version File /home/rsaxena/YoctoWork3x/cedartraiv12p/tmp/sysroots/x86_64-linux/usr/lib/python2.7/distutils/sysconfig.py, line 22, in module PREFIX =
Re: [yocto] [PATCH 2/7] ia32-base.inc: also take -dev package of emgd
On Thu, 2012-07-19 at 10:28 -0500, Tom Zanussi wrote: On Wed, 2012-07-18 at 07:49 -0700, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com emgd-driver-bin recipe provides emgd-driver-bin, emgd-driver-bin-dev emgd-driver-bin-dbg packages. For emgd driver to work it also need library files from emgd-driver-bin-dev package. This change makes sure this -dev package is also added for emgd driver. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- conf/machine/include/ia32-base.inc |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/conf/machine/include/ia32-base.inc b/conf/machine/include/ia32-base.inc index 99ac352..7d9413a 100644 --- a/conf/machine/include/ia32-base.inc +++ b/conf/machine/include/ia32-base.inc @@ -57,6 +57,7 @@ XSERVER_IA32_I965 = xf86-video-intel \ XSERVER_IA32_EMGD = emgd-driver-bin \ + emgd-driver-bin-dev \ I think this is the same problem as 1.10 - you shouldn't have to pull in the -dev package to get those two .so files, which are in the emgd-bin-2443-1.10.i586.rpm and not the -dev rpm: /usr/lib/dri/emgd_dri.so /usr/lib/dri/emgd_drv_video.so /usr/lib/libEGL.so.1.5.15.3226 /usr/lib/libEMGD2d.so.1.5.15.3226 /usr/lib/libEMGDOGL.so.1.5.15.3226 /usr/lib/libEMGDScopeServices.so.1.5.15.3226 /usr/lib/libEMGDegl.so.1.5.15.3226 /usr/lib/libGLES_CM.so.1.5.15.3226 /usr/lib/libGLESv2.so.1.5.15.3226 /usr/lib/libOpenVG.so.1.5.15.3226 /usr/lib/libOpenVGU.so.1.5.15.3226 /usr/lib/libPVRScopeServices.so /usr/lib/libemgdPVR2D_DRIWSEGL.so.1.5.15.3226 /usr/lib/libemgdglslcompiler.so.1.5.15.3226 /usr/lib/libemgdsrv_init.so.1.5.15.3226 /usr/lib/libemgdsrv_um.so.1.5.15.3226 /usr/lib/xorg/modules/drivers/emgd_drv.so /usr/share/doc/emgd/emgd-cb.conf /usr/share/doc/emgd/emgd-rv.conf /usr/share/doc/emgd/license.txt /usr/share/doc/emgd/readme.txt /usr/share/man/man4/emgd.4.gz So those two .so files are now going into the -dev package when before they weren't. I think the package reordering changes are what broke the current recipe: commit f68cbf56d8f2a45ce44a59d0411cdda8ec7e2c36 Author: Saul Wold s...@linux.intel.com Date: Tue Jun 5 04:52:21 2012 -0700 bitbake.conf: reorder PACKAGES list This change re-orders the PACKAGES list to move PN to the end of the list this will ensure that base package gets the final bits since the packaging is greedy. We can then have -dev and other package get bits first. And probably some similar fix to the bunch of 'clean up FILE after PACKAGE reorder' commits would get things back to how they were. Should I file a bug for this? I pushed the fix for this to meta-intel/master, which you should be able to reuse for emgd 1.14. Tom Tom XSERVER_IA32_VESA = xf86-video-vesa ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] nothing building under denzil-7.0.1
On Fri, 2012-07-20 at 16:55 -0500, Tom Zanussi wrote: On Fri, 2012-07-20 at 15:39 -0500, Tom Zanussi wrote: On Fri, 2012-07-20 at 16:35 -0400, Jim Abernathy wrote: On 07/20/2012 04:29 PM, Scott Garman wrote: On 07/20/2012 01:11 PM, Jim Abernathy wrote: There must be some basic thing I'm missing. Nothing that I used to build under denzil 7.0 will now build under denzil 7.0.1 or tracking the denzil branch. Are all the BSPs required to be updated to 7.0.1 before you can run? I'd thought I'd check before I post a bunch of log files. I just downloaded the poky 7.0.1 tarball and cd'ed to that untarred directory and untarred the 7.0 Intel BSPs. There must be a step I'm missing. otherwise this would not have gotten thru testing before deployment. Jim A Hi Jim, We need more specific information about the error(s) you're seeing. We've done extensive QA with 7.0.1 and meta-intel, so I imagine there must be a step you've forgotten. For example, you are using the denzil branch of meta-intel, right? Scott I think it maybe that old problem with the n450 SRCREC being blank in the linux-yocto bbappend file. Obviously that BSP didn't get fixed before 7.0.1 was deployed. I'll put in the ones I used to patch in and see if it works. I updated the n450 in both the denzil and master meta-intel branches, but the tarball still needs to be updated with that fix. Is this the problem you're seeing, or are there other problems you're seeing with this and/or the other meta-intel BSPs? As a sanity check, I just now downloaded the denzil-7.0.1 tarball and the denzil sugarbay tarball and built successfully without any problems. Also did a fresh clone of meta-intel, checked out meta-intel/denzil and successfully built n450 with the denzil-7.0.1 tarball here with no problems. Tom Tom Tom Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
