Re: [yocto] setcap using recipe

[Kumar, Shrawan]

Hello Ross,

Could  your update on my issues ?

Regards
Shrawan

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Kumar, Shrawan
Sent: Monday, June 27, 2016 12:04 PM
To: Burton, Ross
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] setcap using recipe

Hello Ross,

Against which version  this patch is applicable . I am using pseudo-1.7.4  and  
could not find capset.c  file  under  “ports/linux/guts/   directory .

Can you please help here  ?

Thanks and Regards
Shrawan


From: Burton, Ross [mailto:ross.bur...@intel.com]
Sent: Friday, June 24, 2016 6:40 PM
To: Kumar, Shrawan
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] setcap using recipe

Looks like using setcap directly is broken currently, there are two workarounds:

1) use a postinst to invoke setcap on the target instead
2) test the patch for pseudo that is on this list ([PATCH] Add capset pseudo 
function that always succeeds) and verify that it fixes the problem for you.

Ross

On 24 June 2016 at 13:31, Kumar, Shrawan 
> wrote:
I am using Yocto 2.0.2

Thanks and Regards
Shrawan

From: Burton, Ross [mailto:ross.bur...@intel.com]
Sent: Friday, June 24, 2016 5:56 PM

To: Kumar, Shrawan
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] setcap using recipe

What version of OE/Yocto are you using?  Old versions of pseudo didn't support 
xattrs at all.

Ross

On 24 June 2016 at 13:23, Kumar, Shrawan 
> wrote:
Thanks Ross for your quick turn around , I am getting below error

“Unable le to set CAP_SETFCAP effective capability: Operation not permitted.”

But when I use# sudo setcap cap_net_raw+ep  helloworldon command 
line I am able to set the cap.

To achieve the sudo realization  in recipe , I tried  as below , but no luck…… 
Can you suggest something here  ?

fakeroot do_install() {
install -d ${D}${bindir}
install -m 0755 helloworld ${D}${bindir}
install -d ${D}/lib/systemd/system
install -m 0755 hello.service ${D}/lib/systemd/system/
 setcap cap_net_raw+ep  ${D}${bindir}/helloworld

}

Thanks and Regards
Shrawan

From: Burton, Ross [mailto:ross.bur...@intel.com]
Sent: Friday, June 24, 2016 5:09 PM
To: Kumar, Shrawan
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] setcap using recipe

Hi,

On 24 June 2016 at 11:41, Kumar, Shrawan 
> wrote:

Is there a way to  add a capability to a binary (cap_net_raw+ep),into a recipe?


Example :

do_install() {

   install -d ${D}${bindir}

   install -m 0755 helloworld ${D}${bindir}

   install -d ${D}/lib/systemd/system

   install -m 0755 hello.service ${D}/lib/systemd/system/

   setcap cap_net_raw+ep  ${D}${bindir}/helloworld

}



If yes is this correct approach to achieve the same from  package recipe itself 
?

capabilities on files are just extended attributes, so assuming that you have a 
fairly recent Yocto and your host and target filesystems support extended 
attributes, yes this should work.

Ross


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [yocyo-autobuilder][PATCH v2] add mkefidisk image for easier debugging

[Bill Randle]

Originally-by: Ed Bartosh 
Signed-off-by: Bill Randle 
---
v2 fixes typo in image name

 buildset-config.controller/nightly-wic.conf | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/buildset-config.controller/nightly-wic.conf 
b/buildset-config.controller/nightly-wic.conf
index 680ac16..7d2ae88 100644
--- a/buildset-config.controller/nightly-wic.conf
+++ b/buildset-config.controller/nightly-wic.conf
@@ -18,7 +18,8 @@ steps: [{'SetDest':{}},
 {'BuildImages':{'images':'syslinux syslinux-native parted-native 
gptfdisk-native dosfstools-native mtools-native'}},
 {'BuildImages':{'images':'core-image-sato'}},
 {'CreateWicImages':{'wic_img_type':'directdisk', 
'target_img':'core-image-sato'}},
-{'CreateWicImages':{'wic_img_type':'directdisk-gpt', 
'target_img':'core-image-sato'}}]
+{'CreateWicImages':{'wic_img_type':'directdisk-gpt', 
'target_img':'core-image-sato'}},
+{'CreateWicImages':{'wic_img_type':'mkefidisk', 
'target_img':'core-image-sato'}}]
 
 
 
-- 
2.5.5

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [yocto-autobuilder][PATCH] add mkefdisk image for easier debugging

[Bill Randle]

Originally-by: Ed Bartosh 
Signed-off-by: Bill Randle 
---
 buildset-config.controller/nightly-wic.conf | 3 ++-
 1 file changed, 2 insertions(+), 1 deletions(-)

diff --git a/buildset-config.controller/nightly-wic.conf 
b/buildset-config.controller/nightly-wic.conf
index 680ac16..12f1c2e 100644
--- a/buildset-config.controller/nightly-wic.conf
+++ b/buildset-config.controller/nightly-wic.conf
@@ -18,7 +18,8 @@ steps: [{'SetDest':{}},
 {'BuildImages':{'images':'syslinux syslinux-native parted-native 
gptfdisk-native dosfstools-native mtools-native'}},
 {'BuildImages':{'images':'core-image-sato'}},
 {'CreateWicImages':{'wic_img_type':'directdisk', 
'target_img':'core-image-sato'}},
-{'CreateWicImages':{'wic_img_type':'directdisk-gpt', 
'target_img':'core-image-sato'}}]
+{'CreateWicImages':{'wic_img_type':'directdisk-gpt', 
'target_img':'core-image-sato'}},
+{'CreateWicImages':{'wic_img_type':'mkefdisk', 
'target_img':'core-image-sato'}}]
 
 
 
-- 
2.5.5

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [linux-yocto] [yocto-kernel-cache] [PATCH] Fix bitbake warnings on build

[Sullivan, California L]

Ack'd. It looks like we need this for 4.4 and master as well.

Thanks,
Cal

On 06/27/2016 12:14 AM, rebecca.swee.fun.ch...@intel.com wrote:
> From: Rebecca Chang Swee Fun 
>
> Hi Bruce,
>
> With a build test run on Intel Common BSP, some warning messages poped
> out about actual value set is not matched with requested value on
> CONFIG_GPIO_GENERIC.
>
> This can be resolved by setting CONFIG_GPIO_GENERIC_PLATFORM=y
> since CONFIG_GPIO_GENERIC is tristate selected by 
> CONFIG_GPIO_GENERIC_PLATFORM.
>
> This is only targetted to fix on yocto-4.1 branch.
>
> Please review and feedback if you have any. Thank you!
>
> Regards,
> Rebecca
>
> Rebecca Chang Swee Fun (1):
>   broxton: set CONFIG_GPIO_GENERIC_PLATFORM instead of
> CONFIG_GPIO_GENERIC
>
>  features/soc/broxton/broxton.cfg | 1 +
>  1 file changed, 1 insertion(+)
>

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

[yocto] some questions about PPC yocto reference board mpc8315e-rdb

[Robert P. J. Day]

  i'm currently working on a project involving some aging PPC boards
(including MPC8360), and i just happened across a MPC8315E-RDB
(apparently unused), which could be useful since it's the PPC yocto
reference board, which means i should be able to build fully working
images for it without a great deal of fuss.  but first ...

  i'm *reasonably* confident that this system is in the state it was
in as it came from the factory, so i'm curious as to what it should be
able to do without any tweaking. ergo, plugged it in, attached a
serial console, powered it up and ...

U-Boot 1.3.0-rc2 (Mar 21 2008 - 16:00:02) MPC83XX

Reset Status:

CPU:   e300c3, Rev: Unknown revision number:80b40011
Warning: Unsupported cpu revision!
Board: Freescale MPC8315ERDB Rev 1.0
I2C:   ready
DRAM:  128 MB
PCIE0: No link
PCIE1: No link
FLASH:  8 MB
NAND:  32 MiB
In:serial
Out:   serial
Err:   serial
Net:   eTSEC0, eTSEC1
Hit any key to stop autoboot:  0

  whew, that is some kind of old. and here are the current variables
(again, i have no idea if these were changed since the factory):

=> print
nfsboot=setenv bootargs root=/dev/nfs rw nfsroot=$serverip:$rootpath
  ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:off
  console=$consoledev,$baudrate $othbootargs;tftp $loadaddr
  $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr - $fdtaddr
bootdelay=6
baudrate=115200
loads_echo=1
ethaddr=04:00:00:00:00:0A
eth1addr=04:00:00:00:00:0B
loadaddr=20
netdev=eth0
consoledev=ttyS0
ramdiskaddr=100
ramdiskfile=ramfs.83xx
fdtaddr=40
fdtfile=mpc8315erdb.dtb
ethact=eTSEC0
mtdids=nor0=nor,nand0=nand
sataboot=set bootargs root=/dev/sda1 rw console=ttyS0,115200; bootm fe50 - 
fe70
bootcmd=run sataboot
smbboot=set bootargs root=/dev/ram rw console=ttyS0,115200 ramdisk_size=78800; 
tftp $ramdiskaddr $smbfs; bootm fe50 $ramdiskaddr fe70
ramboot=set bootargs root=/dev/ram rw console=ttyS0,115200; bootm fe50 
fe10 fe70
jffs2boot=set bootargs root=/dev/mtdblock1 rootfstype=jffs2 rw 
console=ttyS0,115200; bootm fe50 - fe70
ipaddr=10.196.31.57
serverip=10.196.31.38
bootargs=root=/dev/ram rw console=ttyS0,115200 ramdisk_size=50
stdin=serial
stdout=serial
stderr=serial

Environment size: 1117/8188 bytes
=>

  so let's see what happens if i just let it boot:


Hit any key to stop autoboot:  0
## Booting image at fe50 ...
   Image Name:   Linux-2.6.23
   Created:  2008-03-21   6:25:53 UTC
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:1722476 Bytes =  1.6 MB
   Load Address: 
   Entry Point:  
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
   Booting using the fdt at 0xfe70
   Loading Device Tree to 007fc000, end 007fefff ... OK
Using MPC8315 RDB machine description
Linux version 2.6.23 (yhh@rock) (gcc version 4.1.2) #1 Fri Mar 21 14:25:50 CST 
2008
console [udbg0] enabled
setup_arch: bootmem
mpc8315_rdb_setup_arch()
Freescale SerDes at e00e3000 initialized
Found MPC83xx PCI host bridge at 0x8500. Firmware bus number: 0->0
Found MPC83xx PCI host bridge at 0xe0009000. Firmware bus number: 0->0
Found MPC83xx PCI host bridge at 0xe000a000. Firmware bus number: 0->0
arch: exit
Zone PFN ranges:
  DMA 0 ->32768
  Normal  32768 ->32768
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0:0 ->32768
Built 1 zonelists in Zone order.  Total pages: 32512
Kernel command line: root=/dev/sda1 rw console=ttyS0,115200
IPIC (128 IRQ sources) at faef7700
PID hash table entries: 512 (order: 9, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 126064k/131072k available (3380k kernel code, 4864k reserved, 148k 
data, 100k bss, 164k init)
Mount-cache hash table entries: 512
NET: Registered protocol family 16
CI: Probing PCI hardware
Generic PHY: Registered new driver
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xe0004500 (irq = 22) is a 16550A
console handover: boot [udbg0] -> real [ttyS0]
serial8250.0: ttyS1 at MMIO 0xe0004600 (irq = 23) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 32768K size 1024 blocksize
loop: module loaded
Intel(R) PRO/1000 Network 

Re: [yocto] How to generate debug symbols but not copied to the image?

[Austin Kim]

Thank you for the help.

Now, it generate the debug image but there are two questions.

1. I have problem with Eclipse ADT plugin. I don't know how to set
debug-file-directory into my .dbginit. My project is created via eclipse
Yocto ADT plugin and it overwrites .dbginit whenever Eclipse starts
debugger.I'm pretty new to Yocto, Eclipse and Linux world. Could you give
me any idea how I can set debug-file-directory? I cannot update .dbginit
since the file is overwritten whenever debug starts.

2. When I build the image, it generates tar.gz compressed image and I have
to manually extract the image in some directory whenever build the image
and debug it. Is there any way to deploy the debug symbols under existing
sysroot during the build phase?

These are what I did -

IMAGE_GEN_DEBUGFS = "1"
PACKAGE_DEBUG_SPLIT_STYLE = "debug-file-directory"
IMAGE_FSTYPES_DEBUGFS = "tar.gz"


Thanks!


*- Austin*

On Tue, Jun 28, 2016 at 8:42 AM, Burton, Ross  wrote:

>
> On 28 June 2016 at 16:38, Austin Kim  wrote:
>
>> I'm wondering how to copy only stripped binary and leave debug symbols on
>> the host build machine. I'm running on the OS on a very tight HDD space so
>> I cannot put debug symbols into the image. So I tried
>>
>>
>> PACKAGE_DEBUG_SPLIT_STYLE = 'debug-without-src'
>>
>> EXTRA_IMAGE_FEATURES = "dbg-pkgs"
>>
>> But the output image is still bigger than the original image. Is there
>> anyway to keep the original size and keep debug symbols and source code in
>> the host so DBG may reference them during debugging?
>>
>
> Adding dbg-pkgs to IMAGE_FEATURES says that you want full debugging on the
> target.  Simply don't set that and you'll get stripped binaries on the
> target but full debugging is available on the host for remote gdb (see
> IMAGE_GEN_DEBUGFS).
>
> Ross
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] copying build configuration files to the rootfs

[Bjorn Sorensen]

Hello experts,
I built a Yocto image with ROS and a few of its packages, it all went down 
fine. I can run ROS and the packages that are built in the rootfs. Next I on 
the target machine I setup my environment (Catkin) in order to compile my 
additional ROS packages locally on the target later and at will.
Problem is that when invoking a catkin_make, I get CMake errors (related to the 
build dependencies) saying that:could not find a package configuration file 
provided by "Example_package" with any of the following 
names:"package_nameConfig.cmake""package_name-config.cmake"
I investigated further and "obviously" found out the all of these configuration 
files do exists in my host machine and under the /tmp/sysroots/... tree, in the 
correct path.
Since I want to be able to add and compile more ROS packages later and locally 
on the Target -- which may depend on the already installed packages -- Is there 
a way to instruct the build system to also included all of these configuration 
files in the rootfs image too? or is this contradict the purpose of the Yocto 
project.  -- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH][yocto-autobuilder] nightly-world-lsb.conf: Update buildstep name DownloadBitbakeErrorReports -> DownloadErrorReports

[Joshua G Lock]

Merged to master, thanks,

Joshua

On Tue, 2016-06-28 at 09:53 -0500, Aníbal Limón wrote:
> The reference of the buildsteps for download error reports was
> updated [1] but,
> i forget to update this one.
> 
> [1] http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder/commi
> t/?id=e1e7c3b86720786ae4f60da008f68d4cf5d58559
> 
> Signed-off-by: Aníbal Limón 
> ---
>  buildset-config.controller/nightly-world-lsb.conf | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/buildset-config.controller/nightly-world-lsb.conf
> b/buildset-config.controller/nightly-world-lsb.conf
> index ae3a621..afc7546 100644
> --- a/buildset-config.controller/nightly-world-lsb.conf
> +++ b/buildset-config.controller/nightly-world-lsb.conf
> @@ -21,5 +21,5 @@ steps: [{'SetDest':{}},
>  'distro': 'poky-lsb'}},
>  {'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
>  {'BuildImages': {'images': 'world'}},
> -{'DownloadBitbakeErrorReports': {}},
> +{'DownloadErrorReports': {}},
>  {'SendErrorReport': {}}]
> -- 
> 2.1.4
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] How to generate debug symbols but not copied to the image?

[Burton, Ross]

On 28 June 2016 at 16:38, Austin Kim  wrote:

> I'm wondering how to copy only stripped binary and leave debug symbols on
> the host build machine. I'm running on the OS on a very tight HDD space so
> I cannot put debug symbols into the image. So I tried
>
>
> PACKAGE_DEBUG_SPLIT_STYLE = 'debug-without-src'
>
> EXTRA_IMAGE_FEATURES = "dbg-pkgs"
>
> But the output image is still bigger than the original image. Is there
> anyway to keep the original size and keep debug symbols and source code in
> the host so DBG may reference them during debugging?
>

Adding dbg-pkgs to IMAGE_FEATURES says that you want full debugging on the
target.  Simply don't set that and you'll get stripped binaries on the
target but full debugging is available on the host for remote gdb (see
IMAGE_GEN_DEBUGFS).

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] How to generate debug symbols but not copied to the image?

[Austin Kim]

Hi,

I'm wondering how to copy only stripped binary and leave debug symbols on
the host build machine. I'm running on the OS on a very tight HDD space so
I cannot put debug symbols into the image. So I tried


PACKAGE_DEBUG_SPLIT_STYLE = 'debug-without-src'

EXTRA_IMAGE_FEATURES = "dbg-pkgs"

But the output image is still bigger than the original image. Is there
anyway to keep the original size and keep debug symbols and source code in
the host so DBG may reference them during debugging?

*- Austin*
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH][yocto-autobuilder] nightly-world-lsb.conf: Update buildstep name DownloadBitbakeErrorReports -> DownloadErrorReports

[Aníbal Limón]

The reference of the buildsteps for download error reports was updated [1] but,
i forget to update this one.

[1] 
http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder/commit/?id=e1e7c3b86720786ae4f60da008f68d4cf5d58559

Signed-off-by: Aníbal Limón 
---
 buildset-config.controller/nightly-world-lsb.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/buildset-config.controller/nightly-world-lsb.conf 
b/buildset-config.controller/nightly-world-lsb.conf
index ae3a621..afc7546 100644
--- a/buildset-config.controller/nightly-world-lsb.conf
+++ b/buildset-config.controller/nightly-world-lsb.conf
@@ -21,5 +21,5 @@ steps: [{'SetDest':{}},
 'distro': 'poky-lsb'}},
 {'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
 {'BuildImages': {'images': 'world'}},
-{'DownloadBitbakeErrorReports': {}},
+{'DownloadErrorReports': {}},
 {'SendErrorReport': {}}]
-- 
2.1.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] qemu-qoriq

[Khem Raj]

On Jun 28, 2016 7:22 AM, "Anicic Damir (PSI)"  wrote:
>
> Hi!
>
> For Yocto 2.1
> I have added meta-fsl-ppc repo,
> added layer to bblayers.conf,
> but how to instruct bitbake to use fsl's qemu-qoriq
> instead of poky's qemu (and qemu-native)
>

See if you can use PREFERRED_VERSION to do this

> Regards,
> Damir
>
>
>
>
> --
> ___
> 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] [[yocto-autobuilder][PATCHv2] 00/15] Add support for generate bitbake/oe-selftest error reports

[Aníbal Limón]

On 06/27/2016 07:28 AM, Beth 'pidge' Flanagan wrote:
> Pulled into master, thanks!

Thanks, when i was reviewing the integration i noticed that i miss to
update the buildstep reference (DownloadBitbakeErrorReports ->
DownloadErrorReports) into nightly-world-lsb.conf.

Sorry about that, i sent another patch for fix it,

https://lists.yoctoproject.org/pipermail/yocto/2016-June/030860.html

alimon

>
> 
> -b
> 
> On Tue, 2016-06-21 at 18:07 -0500, Aníbal Limón wrote:
>> This v2 adds support for generate also oe-selftest reports this is
>> almost
>> the previous version with changes requested in review [1], the next
>> patches
>> starts from patch,
>>
>>  autobuilder/lib/{ABtools,builsteps}.py: Create
>> save_error_report func
>>
>> Also the changes could be reviewed at [2].
>>
>> [1] https://lists.yoctoproject.org/pipermail/yocto/2016-June/030515.h
>> tml
>> [2] http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder/log/?
>> h=contrib/alimon/devel
>>
>> Aníbal Limón (15):
>>   lib/buildsteps.py: Add BitbakeShellCommand class
>>   lib/buildsteps.py: Add BitbakeLogLineObserver for
>> BitbakeShellCommands.
>>   lib/buildsteps: BitbakeShellCommand add support for create error
>> reports
>>   lib/ABTools: Add functions for get errordir path in controller and
>> worker
>>   buildbot: Add support for DirectoryDownload transfer step
>>   autobuilder/buildsteps: Add DownloadBitbakeErrorReports step
>>   buiidsets: Add DownloadBitbakeErrorReport step
>>   lib/buildsteps.py: BitbakeShellCommand add support for error_type
>>   autobuilder/lib/buildsteps.py: BitbakeShellCommand update error
>> report
>> types.
>>   autobuilder/lib/{ABtools,builsteps}.py: Create save_error_report
>> func
>>   autobuilder/lib/ABTools.py: Add get_lsb_distro function
>>   buildsteps/RunOeSelftest.py: Add support for create/save error
>> reports
>>   nightly-oe-selftest.conf: Add steps for Download and Send error
>> report.
>>   autobuilder/buildsteps: Rename DownloadBitbakeErrorReports to
>> DownloadErrorReports
>>   buildset-config: Update references from DownloadBitbakeErrorReports
>> to
>> DownloadErrorReports
>>
>>  buildset-config.controller/build-appliance.conf|   1 +
>>  buildset-config.controller/buildtools.conf |   1 +
>>  buildset-config.controller/nightly-arm-lsb.conf|   1 +
>>  buildset-config.controller/nightly-arm.conf|   1 +
>>  buildset-config.controller/nightly-arm64.conf  |   1 +
>>  .../nightly-deb-non-deb.conf   |   1 +
>>  buildset-config.controller/nightly-deb.conf|   1 +
>>  buildset-config.controller/nightly-ipk.conf|   1 +
>>  buildset-config.controller/nightly-mips-lsb.conf   |   1 +
>>  buildset-config.controller/nightly-mips.conf   |   1 +
>>  buildset-config.controller/nightly-mips64.conf |   1 +
>>  buildset-config.controller/nightly-multilib.conf   |   1 +
>>  buildset-config.controller/nightly-musl.conf   |   1 +
>>  buildset-config.controller/nightly-no-x11.conf |   1 +
>>  buildset-config.controller/nightly-non-gpl3.conf   |   1 +
>>  .../nightly-oe-selftest.conf   |   5 +-
>>  buildset-config.controller/nightly-oecore.conf |   1 +
>>  buildset-config.controller/nightly-ppc-lsb.conf|   1 +
>>  buildset-config.controller/nightly-ppc.conf|   1 +
>>  buildset-config.controller/nightly-qa-extras.conf  |   1 +
>>  .../nightly-qa-logrotate.conf  |   1 +
>>  buildset-config.controller/nightly-qa-pam.conf |   1 +
>>  .../nightly-qa-skeleton.conf   |   1 +
>>  buildset-config.controller/nightly-qa-systemd.conf |   1 +
>>  .../nightly-qa-targetbuilds.conf   |   1 +
>>  .../nightly-rpm-non-rpm.conf   |   1 +
>>  buildset-config.controller/nightly-rpm.conf|   1 +
>>  buildset-config.controller/nightly-uclibc.conf |   1 +
>>  buildset-config.controller/nightly-world-lsb.conf  |   1 +
>>  buildset-config.controller/nightly-world.conf  |   1 +
>>  buildset-config.controller/nightly-x32.conf|   1 +
>>  buildset-config.controller/nightly-x86-64-lsb.conf |   1 +
>>  buildset-config.controller/nightly-x86-64.conf |   1 +
>>  buildset-config.controller/nightly-x86-lsb.conf|   1 +
>>  buildset-config.controller/nightly-x86.conf|   1 +
>>  buildset-config.controller/nightly.conf|   1 +
>>  buildset-config.controller/poky-tiny.conf  |   1 +
>>  buildset-config.examples/awesomefirmware.conf  |   1 +
>>  buildset-config.freescale/nightly-fsl-arm-lsb.conf |   1 +
>>  buildset-config.freescale/nightly-fsl-arm.conf |   1 +
>>  buildset-config.freescale/nightly-fsl-ppc-lsb.conf |   1 +
>>  buildset-config.freescale/nightly-fsl-ppc.conf |   1 +
>>  buildset-config.iot-devkit/iot-devkit.conf |   1 +
>>  buildset-config.kernel/kernel-arm-lsb.conf |   1 +
>>  buildset-config.kernel/kernel-arm.conf |  

Re: [yocto] Failed to cross compile kernel with Yocto toolchain

[Khem Raj]

/usr/lib64/ccache is unusual why do you have it in path and if you really
need it add it after all other paths. Check your env first

On Jun 27, 2016 10:56 PM, "Zhenhua Luo"  wrote:

Hello Khem,

> -Original Message-
> From: Khem Raj [mailto:raj.k...@gmail.com]
> Sent: Tuesday, June 28, 2016 12:36 AM
> To: Zhenhua Luo 
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Failed to cross compile kernel with Yocto toolchain
>
> On Mon, Jun 27, 2016 at 1:16 AM, Zhenhua Luo 
> wrote:
> > Hello all,
> >
> >
> >
> > I generate the Yocto toolchain by “bitbake meta-toolchain”, and use
> > this toolchain to cross-compile kernel, I met the following error. Is
> > this a bug or I missed something? My host Linux is Fedora 22.
>
> its better to start using bitbake -cpopulate_sdk  to generate
> SDKs.
>
>
> >
> >
> >
> > $ source /opt/poky/2.1+snapshot/environment-setup-ppce500mc-poky-
> linux
> >
> > $ cd linux/
> >
> > $ make corenet32_smp_defconfig
> >
> >   HOSTCC  scripts/kconfig/conf.o
> >
> > ccache: error: Could not find compiler "gcc" in PATH
>
> did you see if gcc is in your path after sourcing SDK env script?
[Luo Zhenhua-B19537] gcc can't be found after sourcing the SDK env script.
but the /usr/bin is in the PATH env variable.
$ source /opt/poky/2.1+snapshot/environment-setup-ppce500mc-poky-linux
$ echo $PATH
/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin:/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/usr/sbin:/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/bin:/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/sbin:/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/../x86_64-pokysdk-linux/bin:/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/powerpc-poky-linux:/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/powerpc-poky-linux-uclibc:/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/powerpc-poky-linux-musl:/usr/lib64/qt-3.3/bin:/usr/lib64/ccache:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/bjsimics/.local/bin:/home/bjsimics/bin
$ echo $CCACHE_PATH
/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin:/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/../x86_64-pokysdk-linux/bin:/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/powerpc-poky-linux:/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/powerpc-poky-linux-uclibc:/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/powerpc-poky-linux-musl:
$ which gcc
/usr/lib64/ccache/gcc
$ gcc -v
ccache: error: Could not find compiler "gcc" in PATH


Best Regards,

Zhenhua

> > scripts/Makefile.host:108: recipe for target 'scripts/kconfig/conf.o'
> > failed
> >
> > make[1]: *** [scripts/kconfig/conf.o] Error 1
> >
> > Makefile:541: recipe for target 'corenet32_smp_defconfig' failed
> >
> > make: *** [corenet32_smp_defconfig] Error 2
> >
> >
> >
> >
> >
> > Best Regards,
> >
> >
> >
> > Zhenhua
> >
> >
> > --
> > ___
> > 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] [PATCH] nightly-world-lsb.conf: Update name buildstep DownloadBitbakeErrorReports -> DownloadErrorReports

[Aníbal Limón]

The reference of the buildsteps for download error reports was updated [1] but,
i forget to update this one.

[1] 
http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder/commit/?id=e1e7c3b86720786ae4f60da008f68d4cf5d58559

Signed-off-by: Aníbal Limón 
---
 buildset-config.controller/nightly-world-lsb.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/buildset-config.controller/nightly-world-lsb.conf 
b/buildset-config.controller/nightly-world-lsb.conf
index ae3a621..afc7546 100644
--- a/buildset-config.controller/nightly-world-lsb.conf
+++ b/buildset-config.controller/nightly-world-lsb.conf
@@ -21,5 +21,5 @@ steps: [{'SetDest':{}},
 'distro': 'poky-lsb'}},
 {'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
 {'BuildImages': {'images': 'world'}},
-{'DownloadBitbakeErrorReports': {}},
+{'DownloadErrorReports': {}},
 {'SendErrorReport': {}}]
-- 
2.1.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] qemu-qoriq

[Anicic Damir (PSI)]

Hi!

For Yocto 2.1
I have added meta-fsl-ppc repo,
added layer to bblayers.conf,
but how to instruct bitbake to use fsl's qemu-qoriq
instead of poky's qemu (and qemu-native)

Regards,
Damir



-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Failed to cross compile kernel with Yocto toolchain

[Daniel.]

I think you should set CROSS_COMPILE variable

usually I have a script at kernel root to setup variables for me: here
is what I'm using for Daisy
https://gist.github.com/gkos/28f7cf019b716eba8574b21e6f628aa7

2016-06-28 8:20 GMT-03:00 Zhenhua Luo :
> Hi,
>
>> From: Burton, Ross [mailto:ross.bur...@intel.com]
>> Sent: Tuesday, June 28, 2016 6:27 PM
>> To: Zhenhua Luo 
>> Cc: Khem Raj ; yocto@yoctoproject.org
>> Subject: Re: [yocto] Failed to cross compile kernel with Yocto toolchain
>>
>> On 28 June 2016 at 06:56, Zhenhua Luo  wrote:
>> Luo Zhenhua-B19537] gcc can't be found after sourcing the SDK env script. 
>> but the /usr/bin is in the PATH env variable.
>>
>> You *do* have a gcc in /usr/bin, right?
> [Zhenhua Liuo] Right.
>
>
> Best Regards,
>
> Zhenhua
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



-- 
"Do or do not. There is no try"
  Yoda Master
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] How to add recipes to images not RPMs.

[richard.zhang]

Fine ,its work.

Thanks


在 2016年06月28日 20:28, Daniel. 写道:

Ops, Yeah, you right Paul! IMAGE_INSTALL_append***

Thanks

2016-06-27 22:30 GMT-03:00 Paul Eggleton :

I think you mean IMAGE_INSTALL_append.

There is a section of the manual covering this:

   
http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#usingpoky-extend-customimage

Cheers,
Paul

On Mon, 27 Jun 2016 11:22:52 Daniel. wrote:

Adding this to your local.conf?

INSTALL_IMAGE_append = " your packages separeted by whitespaces"

2016-06-27 10:38 GMT-03:00 richard zhang :

Hi all

 I try to add some ricepes to meta layer.The do_fetch and do_compile

things are fine.

 But when I went to image,there is no packages just added.
 I find my packages in build/tmp/deploy/rpm .
 How to add these packages to image.

 I have do this when I use 'hob',but i don't know how to select them

without 'hob'.


best regard.
Richard Zhang

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

--

Paul Eggleton
Intel Open Source Technology Centre





--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] How to add recipes to images not RPMs.

[Daniel.]

Ops, Yeah, you right Paul! IMAGE_INSTALL_append***

Thanks

2016-06-27 22:30 GMT-03:00 Paul Eggleton :
> I think you mean IMAGE_INSTALL_append.
>
> There is a section of the manual covering this:
>
>   
> http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#usingpoky-extend-customimage
>
> Cheers,
> Paul
>
> On Mon, 27 Jun 2016 11:22:52 Daniel. wrote:
>> Adding this to your local.conf?
>>
>> INSTALL_IMAGE_append = " your packages separeted by whitespaces"
>>
>> 2016-06-27 10:38 GMT-03:00 richard zhang :
>> > Hi all
>> >
>> > I try to add some ricepes to meta layer.The do_fetch and do_compile
>> >
>> > things are fine.
>> >
>> > But when I went to image,there is no packages just added.
>> > I find my packages in build/tmp/deploy/rpm .
>> > How to add these packages to image.
>> >
>> > I have do this when I use 'hob',but i don't know how to select them
>> >
>> > without 'hob'.
>> >
>> >
>> > best regard.
>> > Richard Zhang
>> >
>> > --
>> > ___
>> > yocto mailing list
>> > yocto@yoctoproject.org
>> > https://lists.yoctoproject.org/listinfo/yocto
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre



-- 
"Do or do not. There is no try"
  Yoda Master
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Failed to cross compile kernel with Yocto toolchain

[Zhenhua Luo]

Hi, 

> From: Burton, Ross [mailto:ross.bur...@intel.com] 
> Sent: Tuesday, June 28, 2016 6:27 PM
> To: Zhenhua Luo 
> Cc: Khem Raj ; yocto@yoctoproject.org
> Subject: Re: [yocto] Failed to cross compile kernel with Yocto toolchain
>
> On 28 June 2016 at 06:56, Zhenhua Luo  wrote:
> Luo Zhenhua-B19537] gcc can't be found after sourcing the SDK env script. but 
> the /usr/bin is in the PATH env variable.
> 
> You *do* have a gcc in /usr/bin, right?
[Zhenhua Liuo] Right. 


Best Regards,

Zhenhua
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Failed to cross compile kernel with Yocto toolchain

[Burton, Ross]

On 28 June 2016 at 06:56, Zhenhua Luo  wrote:

> [Luo Zhenhua-B19537] gcc can't be found after sourcing the SDK env script.
> but the /usr/bin is in the PATH env variable.
>

You *do* have a gcc in /usr/bin, right?

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto