Re: [yocto] Yocto procedure to write generated image to hdd

2018-03-01 Thread Iván Castell 
2018-03-02 0:41 GMT+01:00 Anuj Mittal :

> Hi,
>
> On 03/01/2018 07:20 PM, Iván Castell wrote:
> >
> > Is this the proper way to install the generated image in the hard disk?
> > Maybe I am doing something wrong?
>
> Does the image boot up if you select 'boot'?


I tested selecting 'boot' option and it happens exactly the same: a black
screen appears when booting with default options, and when adding "noapic",
the screen is flooded of "sleep: command not found" messages.



> Do you eventually get options to select storage media after all these 'not
> found' messages if you select 'install'?


After waiting more than 5 minutes, the "sleep: command not found" message
continues flooding the screen.



> Can you share the logs?
>

If I could, I would do it, but I have no way to get those logs out of the
box without a terminal available.



>
> Thanks,
> Anuj
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] error: possibly undefined macro: PKG_CONFIG_SYSROOT_DIR

2018-03-01 Thread Khem Raj 



On 3/1/18 2:21 AM, Abhishekh Awanti wrote:

Hi,

I am trying to build the package "/harfbuzz-1.3.0" , /but i am getting 
the following configure error


your build seems to be a bit mixed, the baseline seems to be daisy based 
( 1.6 ) but you are building harfbuzz which is introduced in morty ( 2.2 
) release. Doe the original version work ?




/Build Configuration:/
/BB_VERSION        = "1.22.0"/
/BUILD_SYS         = "x86_64-linux"/
/NATIVELSBSTRING   = "Ubuntu-14.04"/
/TARGET_SYS        = "arm-poky-linux-gnueabi"/
/MACHINE           = "iwg21m"/
/DISTRO            = "poky"/
/DISTRO_VERSION    = "1.6.1"/
/TUNE_FEATURES     = "armv7a vfp neon callconvention-hard cortexa15"/
/TARGET_FPU        = "vfp-neon"/
/meta /
/meta-yocto /
/meta-yocto-bsp    = "hmi_tmp:9febda430a88ba23b539394e5d54b59ae87405f6"/
/meta-renesas /
/meta-rzg1         = "master:2ea602f03b9c2378c1d7dc28675a675d18edb0e3"/
/meta-oe /
/meta-multimedia /
/meta-networking   = "hmi_tmp:dca466c074c9a35bc0133e7e0d65cca0731e2acf"/
/meta-linaro-toolchain = 
"hmi_build:8a0601723c06fdb75e62aa0f0cf15fc9d7d90167"/

/common /
/hmi-demo          = "master:2cdb73bb902ecd4462cd0a4a66d5d116d0f7c113"/
/meta-ndvr         = ":"/
/
/
/NOTE: Preparing runqueue/
/NOTE: Executing SetScene Tasks/
/NOTE: Executing RunQueue Tasks/
/ERROR: Function failed: do_configure (log file is located at 
/home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/temp/log.do_configure.451)/
/ERROR: Logfile of failure stored in: 
/home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/temp/log.do_configure.451/

/Log data follows:/
/| DEBUG: Executing python function sysroot_cleansstate/
/| DEBUG: Python function sysroot_cleansstate finished/
/| DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', 
'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common']/

/| DEBUG: Executing shell function autotools_preconfigure/
/| DEBUG: Shell function autotools_preconfigure finished/
/| DEBUG: Executing python function autotools_copy_aclocals/
/| DEBUG: Python function autotools_copy_aclocals finished/
/| DEBUG: Executing shell function do_configure/
/| automake (GNU automake) 1.14/
/| Copyright (C) 2013 Free Software Foundation, Inc./
/| License GPLv2+: GNU GPL version 2 or later 
>/

/| This is free software: you are free to change and redistribute it./
/| There is NO WARRANTY, to the extent permitted by law./
/| /
/| Written by Tom Tromey >/
/|        and Alexandre Duret-Lutz >./
/| AUTOV is 1/
/| NOTE: Executing ACLOCAL="aclocal 
--system-acdir=/home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/build/aclocal-copy/" 
autoreconf --verbose --install --force --exclude=autopoint -I 
/home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/harfbuzz-1.3.0/m4//

/| autoreconf: Entering directory `.'/
/| autoreconf:configure.ac : not using Gettext/
/| autoreconf: running: aclocal 
--system-acdir=/home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/build/aclocal-copy/ 
-I 
/home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/harfbuzz-1.3.0/m4/ 
-I 
/home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/harfbuzz-1.3.0/m4/ 
--force -I m4/

/| autoreconf:configure.ac : tracing/
/| autoreconf: running: libtoolize --copy --force/
/| libtoolize: putting auxiliary files in `.'./
/| libtoolize: copying file `./ltmain.sh'/
/| libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'./
/| libtoolize: copying file `m4/libtool.m4'/
/| libtoolize: copying file `m4/ltoptions.m4'/
/| libtoolize: copying file `m4/ltsugar.m4'/
/| libtoolize: copying file `m4/ltversion.m4'/
/| libtoolize: copying file `m4/lt~obsolete.m4'/
/| autoreconf: running: 
/home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/sysroots/x86_64-linux/usr/bin/autoconf 
--include=/home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/harfbuzz-1.3.0/m4/ 
--force/

/| configure:17934: error: possibly undefined macro:

Re: [yocto] [OE-core] Questions about udev rule and systemd-udev，relevant to mounting block device

2018-03-01 Thread Hongzhi, Song 

Hi all,

Does anyone have suggestion for me?

Thanks.

Hongzhi.Song


On 2018年03月01日 18:35, Hongzhi, Song wrote:


Defect:

    The exiting method of automount of udev in /oe-core/meta/ /is using

/automount.rules/ which call /mount.sh/ that using //bin/mount/ to 
mount device.


But systemd-udevd detaches /mount()/ operations done within the service

from the rest of the system with MountFlag=slave， this means host can

not access device. (e.g. Executing /mkfs.ext4 /dev/sda1// prompts

//dev/sda1 is apparently in use by the system; will not make a 
filesystem here!/)



Solution:

    Systemd upstream suggest that the best way is to use "systemd-mount"

in udev rules, which will request the mount operation to be executed 
by PID 1.


And I have tested it was effective.


Uncertain：

    The exiting method is designed for /SysV-init /which is not 
compatible to


systemd-udev, at least that's what I think. So I think that we should 
design


a new rule or organizational structure to be suitable for systemd-udev 
and


to mount deferent device. Dose anyone help do this? Or I can make some

improvements on the basis of the existing with "systemd-mount".





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

[yocto] [PATCH] hostname.sh: remove warning for bashism

2018-03-01 Thread Ulf Samuelsson 


The use of the environment variable HOSTNAME, triggers
the checkbashisms script, so change HOSTNAME to LOCALHOST

Signed-off-by: Ulf Samuelsson 
---
 meta/recipes-core/initscripts/initscripts-1.0/hostname.sh | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-core/initscripts/initscripts-1.0/hostname.sh 
b/meta/recipes-core/initscripts/initscripts-1.0/hostname.sh

index 95287cc..f4ba2b8 100755
--- a/meta/recipes-core/initscripts/initscripts-1.0/hostname.sh
+++ b/meta/recipes-core/initscripts/initscripts-1.0/hostname.sh
@@ -7,7 +7,7 @@
 # Default-Stop:
 # Short-Description: Set hostname based on /etc/hostname
 ### END INIT INFO
-HOSTNAME=$(/bin/hostname)
+LOCALHOST=$(/bin/hostname)

 hostname -b -F /etc/hostname 2> /dev/null
 if [ $? -eq 0 ]; then
@@ -17,6 +17,6 @@ fi
 # Busybox hostname doesn't support -b so we need implement it on our own
 if [ -f /etc/hostname ];then
 hostname `cat /etc/hostname`
-elif [ -z "$HOSTNAME" -o "$HOSTNAME" = "(none)" -o ! -z "`echo 
$HOSTNAME | sed -n '/^[0-9]*\.[0-9].*/p'`" ] ; then
+elif [ -z "$LOCALHOST" -o "$LOCALHOST" = "(none)" -o ! -z "`echo 
$LOCALHOST | sed -n '/^[0-9]*\.[0-9].*/p'`" ] ; then

 hostname localhost
 fi
--
1.9.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [linux-yocto] [yocto-4.12][PATCH 0/2] a kmemleak and build warning fix for yocto-4.12

2018-03-01 Thread Bruce Ashfield 

On 2018-03-01 9:17 PM, Liwei Song wrote:

Hi Bruce,

These are two upstream patches to fix kmemleak(patch1) and build
warning(patch2) for yocto-4.12 kernel.


Looks good. I've added this to my queue, but I'm working through
a kernel-devsrc change and libc-headers update, so it will be a
few days before I can get it merged.

Bruce




Thanks,
Liwei.


Mikulas Patocka (1):
   brd: remove unused brd_mutex

Shu Wang (1):
   audit: fix memleak in auditd_send_unicast_skb.

  drivers/block/brd.c | 1 -
  kernel/audit.c  | 1 +
  2 files changed, 1 insertion(+), 1 deletion(-)



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

Re: [linux-yocto] [PATCH] aufs: fix compile warning

2018-03-01 Thread Bruce Ashfield 

Looks good. I've added this to my queue, but I'm working through
a kernel-devsrc change and libc-headers update, so it will be a
few days before I can get it merged.

Bruce

On 2018-02-28 8:44 PM, Dengke Du wrote:

From: "Kexin(Casey) Chen" 

Forward port linux-yocto-4.8's patch to fix the build warning.

 
http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-4.8/commit/?h=standard/base=7e0dd2f2b0971f0e3191e1ddc088e09eb9855567

fs/aufs/debug.h:95:19: warning: comparison of constant '0'
with boolean expression is always false [-Wbool-compare]
if (unlikely((e) < 0)) \
 ^

fs/aufs/vdir.c:852:2: note: in expansion of macro 'AuTraceErr'
AuTraceErr(!valid);
^~

In expansion of AuTraceErr(!valid), comparison of (!valid)
and constant '0' always passes unlikely(x) false. function
'static int seek_vdir(struct file *file, struct dir_context *ctx)'
is to find whether there is a valid vd_deblk following ctx->pos.
return 1 means valid, 0 for not. Change to AuTraceErr(valid - 1)
makes more sense.

Signed-off-by: Kexin(Casey) Chen 
Signed-off-by: Dengke Du 
---
  fs/aufs/vdir.c | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/aufs/vdir.c b/fs/aufs/vdir.c
index b7583e9..15f0106 100644
--- a/fs/aufs/vdir.c
+++ b/fs/aufs/vdir.c
@@ -841,7 +841,7 @@ static int seek_vdir(struct file *file, struct dir_context 
*ctx)
  
  out:

/* smp_mb(); */
-   AuTraceErr(!valid);
+   AuTraceErr(valid - 1);
return valid;
  }
  



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

[linux-yocto] [yocto-4.12][PATCH 1/2] audit: fix memleak in auditd_send_unicast_skb.

2018-03-01 Thread Liwei Song 
From: Shu Wang 

commit b0659ae5e30074ede1dc08f2c6d64f0c11d64e0f upstream.

Found this issue by kmemleak report, auditd_send_unicast_skb
did not free skb if rcu_dereference(auditd_conn) returns null.

unreferenced object 0x88082568ce00 (size 256):
comm "auditd", pid 1119, jiffies 4294708499
backtrace:
[] kmemleak_alloc+0x4a/0xa0
[] kmem_cache_alloc_node+0xcc/0x210
[] __alloc_skb+0x5d/0x290
[] audit_make_reply+0x54/0xd0
[] audit_receive_msg+0x967/0xd70

(gdb) list *audit_receive_msg+0x967
0x8113dff7 is in audit_receive_msg (kernel/audit.c:1133).
1132skb = audit_make_reply(0, AUDIT_REPLACE, 0,
0, , sizeof(pvnr));
---
[] audit_receive+0x52/0xa0
[] netlink_unicast+0x181/0x240
[] netlink_sendmsg+0x2c2/0x3b0
[] sock_sendmsg+0x38/0x50
[] SYSC_sendto+0x102/0x190
[] SyS_sendto+0xe/0x10
[] entry_SYSCALL_64_fastpath+0x1a/0xa5
[] 0x

Signed-off-by: Shu Wang 
Signed-off-by: Paul Moore 

Signed-off-by: Liwei Song 
---
 kernel/audit.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/kernel/audit.c b/kernel/audit.c
index 4b7d49868ce1..7df61bee61ee 100644
--- a/kernel/audit.c
+++ b/kernel/audit.c
@@ -633,6 +633,7 @@ static int auditd_send_unicast_skb(struct sk_buff *skb)
ac = rcu_dereference(auditd_conn);
if (!ac) {
rcu_read_unlock();
+   kfree_skb(skb);
rc = -ECONNREFUSED;
goto err;
}
-- 
2.13.3

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

[linux-yocto] [yocto-4.12][PATCH 2/2] brd: remove unused brd_mutex

2018-03-01 Thread Liwei Song 
From: Mikulas Patocka 

commit 15f7b41f70ddcca3b555bd0fdc7c8da7466b517e upstream.

Remove unused mutex brd_mutex. It is unused since the commit ff26956875c2
("brd: remove support for BLKFLSBUF").

Signed-off-by: Mikulas Patocka 
Signed-off-by: Jens Axboe 
Signed-off-by: Liwei Song 
---
 drivers/block/brd.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/drivers/block/brd.c b/drivers/block/brd.c
index ef049e3c9709..d01d84314b16 100644
--- a/drivers/block/brd.c
+++ b/drivers/block/brd.c
@@ -58,7 +58,6 @@ struct brd_device {
 /*
  * Look up and return a brd's page for a given sector.
  */
-static DEFINE_MUTEX(brd_mutex);
 static struct page *brd_lookup_page(struct brd_device *brd, sector_t sector)
 {
pgoff_t idx;
-- 
2.13.3

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

[linux-yocto] [yocto-4.12][PATCH 0/2] a kmemleak and build warning fix for yocto-4.12

2018-03-01 Thread Liwei Song 
Hi Bruce,

These are two upstream patches to fix kmemleak(patch1) and build
warning(patch2) for yocto-4.12 kernel.

Thanks,
Liwei.


Mikulas Patocka (1):
  brd: remove unused brd_mutex

Shu Wang (1):
  audit: fix memleak in auditd_send_unicast_skb.

 drivers/block/brd.c | 1 -
 kernel/audit.c  | 1 +
 2 files changed, 1 insertion(+), 1 deletion(-)

-- 
2.13.3

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

Re: [yocto] Yocto procedure to write generated image to hdd

2018-03-01 Thread Anuj Mittal 
Hi,

On 03/01/2018 07:20 PM, Iván Castell wrote:
> Hello forum.
> 
> Working with 'rocko' yocto branch. Yocto generates .ext4, .hddimg and
> .wic images. I want to install the proper image to the HDD of my PC, in
> order to use it as my default Linux distro.
> 
> I have been using the .wic image to boot from the USB pendrive until
> now, writing it to the USB using 'dd'. This works fine, but because of
> some BIOS issues, I had to modify mkefidisk.wks script to add 'noapic'
> option (probably this is relevant).
> 
> To try to install the generated image in my hard disk, I write the
> .hddimg file to a USB-pendrive using dd and the plug the pendrive and
> boot the PC. A boot menu of GNU GRUB version 2.02 appears with two options:
> 
>     * install
>     * noot
> 
> Editing the install option I can see this:
> 
>     setparams 'install'
>     linux /vmlinuz LABEL=install-efi root=/dev/ram0 rootwait
> console=ttyS0,115200 console=tty0
>     initrd /initrd
> 
> And editing boot options I can see this:
> 
>     setparams 'boot'
>     linux /vmlinuz LABEL=boot root=/dev/ram0 rootwait
> console=ttyS0,115200 console=tty0
>     initrd /initrd
> 
> After choosing "install" option and pressing "Enter", a black screen
> appears and nothing else happens.
> 
> I have tried editing 'install' option, adding 'noapic' after
> console=tty0, and then I can see logs of kernel booting and after 0.5
> secods the screen is flooded of error lines:
> 
>     /init: line 65: sleep: command not found
>     /init: line 65: sleep: command not found
>     ...
>     /init: line 65: sleep: command not found
>                                                                        
>      
> Is this the proper way to install the generated image in the hard disk?
> Maybe I am doing something wrong?

Does the image boot up if you select 'boot'? Do you eventually get
options to select storage media after all these 'not found' messages if
you select 'install'? Can you share the logs?

Thanks,
Anuj

> 
> Thanks a lot in advance! :-)
> 
> Best regards,
>   -- Ivan
> 
> 
> 

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

Re: [yocto] Yocto procedure to write generated image to hdd

2018-03-01 Thread Iván Castell 
After writting the .hddimg file to a USB-pendrive I have mounted the
pendrive to analyze contents in my laptop. It contains the following files:

./EFI/BOOT/grub.cfg
./EFI/BOOT/bootx64.efi
./initrd
./ldlinux.sys
./libcom32.c32
./libutil.c32
./rootfs.img
./startup.nsh
./syslinux.cfg
./vesamenu.c32
./vmlinuz
./ldlinux.c32

This is the content of /EFI/BOOT/grub.cfg file:

$ cat EFI/BOOT/grub.cfg
# Automatically created by OE
serial --unit=0 --speed=115200 --word=8 --parity=no --stop=1
default=install
timeout=3

menuentry 'install'{
linux /vmlinuz LABEL=install-efi root=/dev/ram0
rootwait console=ttyS0,115200 console=tty0
initrd /initrd
}

menuentry 'boot'{
linux /vmlinuz LABEL=boot root=/dev/ram0  rootwait console=ttyS0,115200
console=tty0
initrd /initrd
}

I found this link with useful information:

https://www.yoctoproject.org/downloads/bsps/danny13/atom-pc

According to it, "it is likely the BIOS cannot understand the physical
layout of the disk".

This sounds strange to me, because USB-pendrive boots fine when the .wic
image is burned into the USB-pendrive. But anyway, I have checked BIOS
USB-related settings and this is my current setup:

Main information:

BIOS Vendor: American Megratrends
Core Version 5.009
Compilancy: UEFI 2.3; PI 1.2
BIOS ID: N29NL009 x64

USB-related information:

USB Module version: 8.11.02
Legacy USB Support [Enabled]
USB 2.0 Controller Mode [HiSpeed]
XHCI Hand-off [Enabled]
EHCI Hand-off [Disabled]
USB Mass Storage Driver Support is [Enabled]

General UDisk 5.00 [Auto]

I don't know what can I do to manage this issue. I'm really blocked on
this, any help to would be very helpful. Thanks in advance!!




2018-03-01 12:20 GMT+01:00 Iván Castell :

> Hello forum.
>
> Working with 'rocko' yocto branch. Yocto generates .ext4, .hddimg and .wic
> images. I want to install the proper image to the HDD of my PC, in order to
> use it as my default Linux distro.
>
> I have been using the .wic image to boot from the USB pendrive until now,
> writing it to the USB using 'dd'. This works fine, but because of some BIOS
> issues, I had to modify mkefidisk.wks script to add 'noapic' option
> (probably this is relevant).
>
> To try to install the generated image in my hard disk, I write the .hddimg
> file to a USB-pendrive using dd and the plug the pendrive and boot the PC.
> A boot menu of GNU GRUB version 2.02 appears with two options:
>
> * install
> * noot
>
> Editing the install option I can see this:
>
> setparams 'install'
> linux /vmlinuz LABEL=install-efi root=/dev/ram0 rootwait
> console=ttyS0,115200 console=tty0
> initrd /initrd
>
> And editing boot options I can see this:
>
> setparams 'boot'
> linux /vmlinuz LABEL=boot root=/dev/ram0 rootwait console=ttyS0,115200
> console=tty0
> initrd /initrd
>
> After choosing "install" option and pressing "Enter", a black screen
> appears and nothing else happens.
>
> I have tried editing 'install' option, adding 'noapic' after console=tty0,
> and then I can see logs of kernel booting and after 0.5 secods the screen
> is flooded of error lines:
>
> /init: line 65: sleep: command not found
> /init: line 65: sleep: command not found
> ...
> /init: line 65: sleep: command not found
>
>
> Is this the proper way to install the generated image in the hard disk?
> Maybe I am doing something wrong?
>
> Thanks a lot in advance! :-)
>
> Best regards,
>   -- Ivan
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi] linux kernel rt

2018-03-01 Thread Andrei Gherzan 
On Thu, Mar 1, 2018 at 1:59 PM, Andreas Müller 
wrote:

> On Fri, Jan 26, 2018 at 3:09 PM, Trevor Woerner 
> wrote:
> > On Fri, Jan 26, 2018 at 3:43 AM, Martin Hundebøll
> >  wrote:
> >>
> >>
> >>
> >> On 2018-01-26 04:51, Khem Raj wrote:
> >>>
> >>>
> >>> Secondly, I wonder how good is upstream mainline kernel for rpi now a
> >>> days, we could always have a mainline recipe as an option and use it
> as base
> >>> for things like rt.
> >>
> >>
> >> Apart from runtime device tree overlay support for RPi hats/extension
> >> boards, mainline linux fully supports each RPi revision.
> >>
> >> I guess linux-yocto-rt would be just fine...
> >>
> >
> > Does anyone know if the FIQ bug has been fixed upstream? The last time I
> > looked into PREEMPT_RT on the RPi, the only way to make it work/stable
> was
> > to patch the FIQ issue, or disable FIQ altogether (not ideal). This patch
> > was outside both the kernel and the PREEMPT_RT patch.
> >
> > --
> Seems RPi.org made some progress on this[1].
>
> If I only had some time left to give this a try...
>
> [1] https://github.com/raspberrypi/linux/issues/2244#
> issuecomment-369597357


Nice.

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

Re: [yocto] [meta-raspberrypi] linux kernel rt

2018-03-01 Thread Paul Barker 
On Thu, Mar 1, 2018 at 1:59 PM, Andreas Müller  wrote:
> Seems RPi.org made some progress on this[1].
>
> If I only had some time left to give this a try...
>
> [1] https://github.com/raspberrypi/linux/issues/2244#issuecomment-369597357
>

This looks great! I'd love to see a recipe for this added to
meta-raspberrypi. Let me know if you need any help and I'll see what I
can do.

-- 
Paul Barker
Togán Labs Ltd
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [auh][PATCH] Do not hardcode the location of tmp directory

2018-03-01 Thread Alexander Kanavin 
Get it from bitbake instead.

[YOCTO #12566]

Signed-off-by: Alexander Kanavin 
---
 upgradehelper.py | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/upgradehelper.py b/upgradehelper.py
index 169e9ce..d868cde 100755
--- a/upgradehelper.py
+++ b/upgradehelper.py
@@ -602,9 +602,9 @@ class UniverseUpdater(Updater):
 I(" Removing sstate directory ...")
 shutil.rmtree(os.path.join(get_build_dir(), "sstate-cache"))
 if settings.get("clean_tmp", "no") == "yes" and \
-os.path.exists(os.path.join(get_build_dir(), "tmp")):
+os.path.exists(self.base_env['TMPDIR']):
 I(" Removing tmp directory ...")
-shutil.rmtree(os.path.join(get_build_dir(), "tmp"))
+shutil.rmtree(self.base_env['TMPDIR'])
 
 def _check_upstream_versions(self):
 I(" Fetching upstream version(s) ...")
@@ -711,7 +711,7 @@ class UniverseUpdater(Updater):
 
 def _get_packages_to_upgrade(self, packages=None):
 self._check_upstream_versions()
-last_checkpkg_file = os.path.realpath(get_build_dir() + 
"/tmp/log/checkpkg.csv")
+last_checkpkg_file = os.path.realpath(self.base_env['TMPDIR'] + 
"/log/checkpkg.csv")
 
 pkgs_list = []
 for pkg in self._parse_checkpkg_file(last_checkpkg_file):
-- 
2.15.1

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

Re: [yocto] [meta-raspberrypi] linux kernel rt

2018-03-01 Thread Zoran Stojsavljevic 
*git://git.kernel.org/pub/scm/linux/kernel/git/bwh/linux-cip.git
*

True Real Time 4.4.112.

Zoran
___

On Thu, Dec 14, 2017 at 2:58 AM, Sherif Omran 
wrote:

> hey guys,
>
> any body tried the real time kernel? I get an error, it is snot in the
> compatibility list.
> can we skip it?
>
> thanks
>
> --
> ___
> 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] [meta-raspberrypi] linux kernel rt

2018-03-01 Thread Andreas Müller 
On Fri, Jan 26, 2018 at 3:09 PM, Trevor Woerner  wrote:
> On Fri, Jan 26, 2018 at 3:43 AM, Martin Hundebøll
>  wrote:
>>
>>
>>
>> On 2018-01-26 04:51, Khem Raj wrote:
>>>
>>>
>>> Secondly, I wonder how good is upstream mainline kernel for rpi now a
>>> days, we could always have a mainline recipe as an option and use it as base
>>> for things like rt.
>>
>>
>> Apart from runtime device tree overlay support for RPi hats/extension
>> boards, mainline linux fully supports each RPi revision.
>>
>> I guess linux-yocto-rt would be just fine...
>>
>
> Does anyone know if the FIQ bug has been fixed upstream? The last time I
> looked into PREEMPT_RT on the RPi, the only way to make it work/stable was
> to patch the FIQ issue, or disable FIQ altogether (not ideal). This patch
> was outside both the kernel and the PREEMPT_RT patch.
>
> --
Seems RPi.org made some progress on this[1].

If I only had some time left to give this a try...

[1] https://github.com/raspberrypi/linux/issues/2244#issuecomment-369597357

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

Re: [yocto] [Yocto][Meta-Raspberrypi] Yocto apt sources.list for Raspberry Pi

2018-03-01 Thread Laigui Qin 
Hi Alex,


Thanks for the explanation. It makes much more sense for the difference.


BR,
Mike



At 2018-03-01 00:02:36, "Alexander Kanavin"  
wrote:
>On 02/26/2018 04:14 PM, Laigui Qin wrote:
>> I would like to think there is a well maintained Yocto/Poky repository 
>> somewhere in the world like the debian/Raspbian deb source to leverage 
>> (build and maintain my own repo is not my purpose.) Looks like there is 
>> not such repo available...
>
>Please consider that Yocto is not a distribution. It's a toolkit for 
>creating distributions aimed at embedded use cases. While Poky is a 
>reference distro created using Yocto components, it has a fairly limited 
>set of supported hardware, which is mostly various QEMU emulator 
>machines. Almost anyone else will have a different machine, different 
>distribution features, and various other customizations. So any attempt 
>to provide an 'offical' package feed from Yocto itself will just cause 
>confusion and breakage, and will tie up the limited manpower we have 
>even more.
>
>
>Alex
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-java][PATCH] jdepend: give the downloaded file a reasonable name

2018-03-01 Thread Maxin B. John 
Hi,

On Thu, Mar 01, 2018 at 10:46:01AM +, André Draszik wrote:
> From: André Draszik 
> 
> 2.9.1.zip in the 'downloads' folder will easily be overwritten...
> 
> Signed-off-by: André Draszik 
> ---
>  recipes-core/jdepend/jdepend_2.9.1.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/recipes-core/jdepend/jdepend_2.9.1.bb 
> b/recipes-core/jdepend/jdepend_2.9.1.bb
> index be48325..5f09a8b 100644
> --- a/recipes-core/jdepend/jdepend_2.9.1.bb
> +++ b/recipes-core/jdepend/jdepend_2.9.1.bb
> @@ -6,7 +6,7 @@ LIC_FILES_CHKSUM = 
> "file://LICENSE;md5=f5777d32a7709d558c2877d4a6616230"
>  
>  HOMEPAGE = "https://github.com/clarkware/jdepend;
>  
> -SRC_URI = "https://github.com/clarkware/jdepend/archive/${PV}.zip;
> +SRC_URI = 
> "https://github.com/clarkware/jdepend/archive/${PV}.zip;downloadfilename=${BP}.zip;
>  
>  inherit java-library
>  

Thanks, Pushed to master.

Best Regards,
Maxin

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

Re: [yocto] error: possibly undefined macro: PKG_CONFIG_SYSROOT_DIR

2018-03-01 Thread Burton, Ross 
Assuming you don't delete sstate-cache then you won't need to rebuild
anything.

Ross

On 1 March 2018 at 11:36, Abhishekh Awanti  wrote:

> yeah the pkgconfig has been inherited.
> If i delete the tmp/ , again i have to recompile my whole build? Is tat
> you wanted to do me?
>
>
> Thanks and Regards,
> Abhishek Awanti
> Mob: +919620666017 <+91%2096206%2066017>
>
> On Thu, Mar 1, 2018 at 4:37 PM, Burton, Ross 
> wrote:
>
>> That usually means that the recipe doesn't inherit pkgconfig, but as this
>> is an oe-core recipe it should be doing this.  Can you verify this, and if
>> you can still reproduce it after deleting tmp/ then please attach the
>> entire log.do_configure.
>>
>> Ross
>>
>> On 1 March 2018 at 10:21, Abhishekh Awanti 
>> wrote:
>>
>>> Hi,
>>>
>>> I am trying to build the package "*harfbuzz-1.3.0" ,  *but i am getting
>>> the following configure error
>>>
>>> *Build Configuration:*
>>> *BB_VERSION= "1.22.0"*
>>> *BUILD_SYS = "x86_64-linux"*
>>> *NATIVELSBSTRING   = "Ubuntu-14.04"*
>>> *TARGET_SYS= "arm-poky-linux-gnueabi"*
>>> *MACHINE   = "iwg21m"*
>>> *DISTRO= "poky"*
>>> *DISTRO_VERSION= "1.6.1"*
>>> *TUNE_FEATURES = "armv7a vfp neon callconvention-hard cortexa15"*
>>> *TARGET_FPU= "vfp-neon"*
>>> *meta  *
>>> *meta-yocto*
>>> *meta-yocto-bsp= "hmi_tmp:9febda430a88ba23b539394e5d54b59ae87405f6"*
>>> *meta-renesas  *
>>> *meta-rzg1 = "master:2ea602f03b9c2378c1d7dc28675a675d18edb0e3"*
>>> *meta-oe   *
>>> *meta-multimedia   *
>>> *meta-networking   = "hmi_tmp:dca466c074c9a35bc0133e7e0d65cca0731e2acf"*
>>> *meta-linaro-toolchain =
>>> "hmi_build:8a0601723c06fdb75e62aa0f0cf15fc9d7d90167"*
>>> *common*
>>> *hmi-demo  = "master:2cdb73bb902ecd4462cd0a4a66d5d116d0f7c113"*
>>> *meta-ndvr = ":"*
>>>
>>> *NOTE: Preparing runqueue*
>>> *NOTE: Executing SetScene Tasks*
>>> *NOTE: Executing RunQueue Tasks*
>>> *ERROR: Function failed: do_configure (log file is located at
>>> /home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/temp/log.do_configure.451)*
>>> *ERROR: Logfile of failure stored in:
>>> /home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/temp/log.do_configure.451*
>>> *Log data follows:*
>>> *| DEBUG: Executing python function sysroot_cleansstate*
>>> *| DEBUG: Python function sysroot_cleansstate finished*
>>> *| DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common',
>>> 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common']*
>>> *| DEBUG: Executing shell function autotools_preconfigure*
>>> *| DEBUG: Shell function autotools_preconfigure finished*
>>> *| DEBUG: Executing python function autotools_copy_aclocals*
>>> *| DEBUG: Python function autotools_copy_aclocals finished*
>>> *| DEBUG: Executing shell function do_configure*
>>> *| automake (GNU automake) 1.14*
>>> *| Copyright (C) 2013 Free Software Foundation, Inc.*
>>> *| License GPLv2+: GNU GPL version 2 or later
>>> >> >*
>>> *| This is free software: you are free to change and redistribute it.*
>>> *| There is NO WARRANTY, to the extent permitted by law.*
>>> *| *
>>> *| Written by Tom Tromey >*
>>> *|and Alexandre Duret-Lutz >.*
>>> *| AUTOV is 1*
>>> *| NOTE: Executing ACLOCAL="aclocal
>>> --system-acdir=/home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/build/aclocal-copy/"
>>> autoreconf --verbose --install --force --exclude=autopoint -I
>>> /home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/harfbuzz-1.3.0/m4/*
>>> *| autoreconf: Entering directory `.'*
>>> *| autoreconf: configure.ac : not using Gettext*
>>> *| autoreconf: running: aclocal
>>> --system-acdir=/home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/build/aclocal-copy/
>>> -I
>>> /home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/harfbuzz-1.3.0/m4/
>>> -I
>>> /home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/harfbuzz-1.3.0/m4/
>>> --force -I m4*
>>> *| autoreconf: configure.ac

Re: [yocto] error: possibly undefined macro: PKG_CONFIG_SYSROOT_DIR

2018-03-01 Thread Abhishekh Awanti 
yeah the pkgconfig has been inherited.
If i delete the tmp/ , again i have to recompile my whole build? Is tat you
wanted to do me?


Thanks and Regards,
Abhishek Awanti
Mob: +919620666017

On Thu, Mar 1, 2018 at 4:37 PM, Burton, Ross  wrote:

> That usually means that the recipe doesn't inherit pkgconfig, but as this
> is an oe-core recipe it should be doing this.  Can you verify this, and if
> you can still reproduce it after deleting tmp/ then please attach the
> entire log.do_configure.
>
> Ross
>
> On 1 March 2018 at 10:21, Abhishekh Awanti 
> wrote:
>
>> Hi,
>>
>> I am trying to build the package "*harfbuzz-1.3.0" ,  *but i am getting
>> the following configure error
>>
>> *Build Configuration:*
>> *BB_VERSION= "1.22.0"*
>> *BUILD_SYS = "x86_64-linux"*
>> *NATIVELSBSTRING   = "Ubuntu-14.04"*
>> *TARGET_SYS= "arm-poky-linux-gnueabi"*
>> *MACHINE   = "iwg21m"*
>> *DISTRO= "poky"*
>> *DISTRO_VERSION= "1.6.1"*
>> *TUNE_FEATURES = "armv7a vfp neon callconvention-hard cortexa15"*
>> *TARGET_FPU= "vfp-neon"*
>> *meta  *
>> *meta-yocto*
>> *meta-yocto-bsp= "hmi_tmp:9febda430a88ba23b539394e5d54b59ae87405f6"*
>> *meta-renesas  *
>> *meta-rzg1 = "master:2ea602f03b9c2378c1d7dc28675a675d18edb0e3"*
>> *meta-oe   *
>> *meta-multimedia   *
>> *meta-networking   = "hmi_tmp:dca466c074c9a35bc0133e7e0d65cca0731e2acf"*
>> *meta-linaro-toolchain =
>> "hmi_build:8a0601723c06fdb75e62aa0f0cf15fc9d7d90167"*
>> *common*
>> *hmi-demo  = "master:2cdb73bb902ecd4462cd0a4a66d5d116d0f7c113"*
>> *meta-ndvr = ":"*
>>
>> *NOTE: Preparing runqueue*
>> *NOTE: Executing SetScene Tasks*
>> *NOTE: Executing RunQueue Tasks*
>> *ERROR: Function failed: do_configure (log file is located at
>> /home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/temp/log.do_configure.451)*
>> *ERROR: Logfile of failure stored in:
>> /home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/temp/log.do_configure.451*
>> *Log data follows:*
>> *| DEBUG: Executing python function sysroot_cleansstate*
>> *| DEBUG: Python function sysroot_cleansstate finished*
>> *| DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common',
>> 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common']*
>> *| DEBUG: Executing shell function autotools_preconfigure*
>> *| DEBUG: Shell function autotools_preconfigure finished*
>> *| DEBUG: Executing python function autotools_copy_aclocals*
>> *| DEBUG: Python function autotools_copy_aclocals finished*
>> *| DEBUG: Executing shell function do_configure*
>> *| automake (GNU automake) 1.14*
>> *| Copyright (C) 2013 Free Software Foundation, Inc.*
>> *| License GPLv2+: GNU GPL version 2 or later
>> > >*
>> *| This is free software: you are free to change and redistribute it.*
>> *| There is NO WARRANTY, to the extent permitted by law.*
>> *| *
>> *| Written by Tom Tromey >*
>> *|and Alexandre Duret-Lutz >.*
>> *| AUTOV is 1*
>> *| NOTE: Executing ACLOCAL="aclocal
>> --system-acdir=/home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/build/aclocal-copy/"
>> autoreconf --verbose --install --force --exclude=autopoint -I
>> /home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/harfbuzz-1.3.0/m4/*
>> *| autoreconf: Entering directory `.'*
>> *| autoreconf: configure.ac : not using Gettext*
>> *| autoreconf: running: aclocal
>> --system-acdir=/home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/build/aclocal-copy/
>> -I
>> /home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/harfbuzz-1.3.0/m4/
>> -I
>> /home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/harfbuzz-1.3.0/m4/
>> --force -I m4*
>> *| autoreconf: configure.ac : tracing*
>> *| autoreconf: running: libtoolize --copy --force*
>> *| libtoolize: putting auxiliary files in `.'.*
>> *| libtoolize: copying file `./ltmain.sh'*
>> *| libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.*
>> *| libtoolize: copying file `m4/libtool.m4'*
>> *|

[yocto] Yocto procedure to write generated image to hdd

2018-03-01 Thread Iván Castell 
Hello forum.

Working with 'rocko' yocto branch. Yocto generates .ext4, .hddimg and .wic
images. I want to install the proper image to the HDD of my PC, in order to
use it as my default Linux distro.

I have been using the .wic image to boot from the USB pendrive until now,
writing it to the USB using 'dd'. This works fine, but because of some BIOS
issues, I had to modify mkefidisk.wks script to add 'noapic' option
(probably this is relevant).

To try to install the generated image in my hard disk, I write the .hddimg
file to a USB-pendrive using dd and the plug the pendrive and boot the PC.
A boot menu of GNU GRUB version 2.02 appears with two options:

* install
* noot

Editing the install option I can see this:

setparams 'install'
linux /vmlinuz LABEL=install-efi root=/dev/ram0 rootwait
console=ttyS0,115200 console=tty0
initrd /initrd

And editing boot options I can see this:

setparams 'boot'
linux /vmlinuz LABEL=boot root=/dev/ram0 rootwait console=ttyS0,115200
console=tty0
initrd /initrd

After choosing "install" option and pressing "Enter", a black screen
appears and nothing else happens.

I have tried editing 'install' option, adding 'noapic' after console=tty0,
and then I can see logs of kernel booting and after 0.5 secods the screen
is flooded of error lines:

/init: line 65: sleep: command not found
/init: line 65: sleep: command not found
...
/init: line 65: sleep: command not found


Is this the proper way to install the generated image in the hard disk?
Maybe I am doing something wrong?

Thanks a lot in advance! :-)

Best regards,
  -- Ivan
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] error: possibly undefined macro: PKG_CONFIG_SYSROOT_DIR

2018-03-01 Thread Burton, Ross 
That usually means that the recipe doesn't inherit pkgconfig, but as this
is an oe-core recipe it should be doing this.  Can you verify this, and if
you can still reproduce it after deleting tmp/ then please attach the
entire log.do_configure.

Ross

On 1 March 2018 at 10:21, Abhishekh Awanti  wrote:

> Hi,
>
> I am trying to build the package "*harfbuzz-1.3.0" ,  *but i am getting
> the following configure error
>
> *Build Configuration:*
> *BB_VERSION= "1.22.0"*
> *BUILD_SYS = "x86_64-linux"*
> *NATIVELSBSTRING   = "Ubuntu-14.04"*
> *TARGET_SYS= "arm-poky-linux-gnueabi"*
> *MACHINE   = "iwg21m"*
> *DISTRO= "poky"*
> *DISTRO_VERSION= "1.6.1"*
> *TUNE_FEATURES = "armv7a vfp neon callconvention-hard cortexa15"*
> *TARGET_FPU= "vfp-neon"*
> *meta  *
> *meta-yocto*
> *meta-yocto-bsp= "hmi_tmp:9febda430a88ba23b539394e5d54b59ae87405f6"*
> *meta-renesas  *
> *meta-rzg1 = "master:2ea602f03b9c2378c1d7dc28675a675d18edb0e3"*
> *meta-oe   *
> *meta-multimedia   *
> *meta-networking   = "hmi_tmp:dca466c074c9a35bc0133e7e0d65cca0731e2acf"*
> *meta-linaro-toolchain =
> "hmi_build:8a0601723c06fdb75e62aa0f0cf15fc9d7d90167"*
> *common*
> *hmi-demo  = "master:2cdb73bb902ecd4462cd0a4a66d5d116d0f7c113"*
> *meta-ndvr = ":"*
>
> *NOTE: Preparing runqueue*
> *NOTE: Executing SetScene Tasks*
> *NOTE: Executing RunQueue Tasks*
> *ERROR: Function failed: do_configure (log file is located at
> /home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/temp/log.do_configure.451)*
> *ERROR: Logfile of failure stored in:
> /home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/temp/log.do_configure.451*
> *Log data follows:*
> *| DEBUG: Executing python function sysroot_cleansstate*
> *| DEBUG: Python function sysroot_cleansstate finished*
> *| DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common',
> 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common']*
> *| DEBUG: Executing shell function autotools_preconfigure*
> *| DEBUG: Shell function autotools_preconfigure finished*
> *| DEBUG: Executing python function autotools_copy_aclocals*
> *| DEBUG: Python function autotools_copy_aclocals finished*
> *| DEBUG: Executing shell function do_configure*
> *| automake (GNU automake) 1.14*
> *| Copyright (C) 2013 Free Software Foundation, Inc.*
> *| License GPLv2+: GNU GPL version 2 or later
>  >*
> *| This is free software: you are free to change and redistribute it.*
> *| There is NO WARRANTY, to the extent permitted by law.*
> *| *
> *| Written by Tom Tromey >*
> *|and Alexandre Duret-Lutz >.*
> *| AUTOV is 1*
> *| NOTE: Executing ACLOCAL="aclocal
> --system-acdir=/home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/build/aclocal-copy/"
> autoreconf --verbose --install --force --exclude=autopoint -I
> /home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/harfbuzz-1.3.0/m4/*
> *| autoreconf: Entering directory `.'*
> *| autoreconf: configure.ac : not using Gettext*
> *| autoreconf: running: aclocal
> --system-acdir=/home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/build/aclocal-copy/
> -I
> /home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/harfbuzz-1.3.0/m4/
> -I
> /home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/harfbuzz-1.3.0/m4/
> --force -I m4*
> *| autoreconf: configure.ac : tracing*
> *| autoreconf: running: libtoolize --copy --force*
> *| libtoolize: putting auxiliary files in `.'.*
> *| libtoolize: copying file `./ltmain.sh'*
> *| libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.*
> *| libtoolize: copying file `m4/libtool.m4'*
> *| libtoolize: copying file `m4/ltoptions.m4'*
> *| libtoolize: copying file `m4/ltsugar.m4'*
> *| libtoolize: copying file `m4/ltversion.m4'*
> *| libtoolize: copying file `m4/lt~obsolete.m4'*
> *| autoreconf: running:
> /home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/sysroots/x86_64-linux/usr/bin/autoconf
>

[yocto] [meta-java][PATCH] jdepend: give the downloaded file a reasonable name

2018-03-01 Thread André Draszik 
From: André Draszik 

2.9.1.zip in the 'downloads' folder will easily be overwritten...

Signed-off-by: André Draszik 
---
 recipes-core/jdepend/jdepend_2.9.1.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-core/jdepend/jdepend_2.9.1.bb 
b/recipes-core/jdepend/jdepend_2.9.1.bb
index be48325..5f09a8b 100644
--- a/recipes-core/jdepend/jdepend_2.9.1.bb
+++ b/recipes-core/jdepend/jdepend_2.9.1.bb
@@ -6,7 +6,7 @@ LIC_FILES_CHKSUM = 
"file://LICENSE;md5=f5777d32a7709d558c2877d4a6616230"
 
 HOMEPAGE = "https://github.com/clarkware/jdepend;
 
-SRC_URI = "https://github.com/clarkware/jdepend/archive/${PV}.zip;
+SRC_URI = 
"https://github.com/clarkware/jdepend/archive/${PV}.zip;downloadfilename=${BP}.zip;
 
 inherit java-library
 
-- 
2.16.2

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

[yocto] Questions about udev rule and systemd-udev，relevant to mounting block device

2018-03-01 Thread Hongzhi, Song 

Defect:

    The exiting method of automount of udev in /oe-core/meta/ /is using

/automount.rules/ which call /mount.sh/ that using //bin/mount/ to mount 
device.


But systemd-udevd detaches /mount()/ operations done within the service

from the rest of the system with MountFlag=slave， this means host can

not access device. (e.g. Executing /mkfs.ext4 /dev/sda1// prompts

//dev/sda1 is apparently in use by the system; will not make a 
filesystem here!/)



Solution:

    Systemd upstream suggest that the best way is to use "systemd-mount"

in udev rules, which will request the mount operation to be executed by 
PID 1.


And I have tested it was effective.


Uncertain：

    The exiting method is designed for /SysV-init /which is not 
compatible to


systemd-udev, at least that's what I think. So I think that we should design

a new rule or organizational structure to be suitable for systemd-udev and

to mount deferent device. Dose anyone help do this? Or I can make some

improvements on the basis of the existing with "systemd-mount".

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

[yocto] error: possibly undefined macro: PKG_CONFIG_SYSROOT_DIR

2018-03-01 Thread Abhishekh Awanti 
Hi,

I am trying to build the package "*harfbuzz-1.3.0" ,  *but i am getting the
following configure error

*Build Configuration:*
*BB_VERSION= "1.22.0"*
*BUILD_SYS = "x86_64-linux"*
*NATIVELSBSTRING   = "Ubuntu-14.04"*
*TARGET_SYS= "arm-poky-linux-gnueabi"*
*MACHINE   = "iwg21m"*
*DISTRO= "poky"*
*DISTRO_VERSION= "1.6.1"*
*TUNE_FEATURES = "armv7a vfp neon callconvention-hard cortexa15"*
*TARGET_FPU= "vfp-neon"*
*meta  *
*meta-yocto*
*meta-yocto-bsp= "hmi_tmp:9febda430a88ba23b539394e5d54b59ae87405f6"*
*meta-renesas  *
*meta-rzg1 = "master:2ea602f03b9c2378c1d7dc28675a675d18edb0e3"*
*meta-oe   *
*meta-multimedia   *
*meta-networking   = "hmi_tmp:dca466c074c9a35bc0133e7e0d65cca0731e2acf"*
*meta-linaro-toolchain =
"hmi_build:8a0601723c06fdb75e62aa0f0cf15fc9d7d90167"*
*common*
*hmi-demo  = "master:2cdb73bb902ecd4462cd0a4a66d5d116d0f7c113"*
*meta-ndvr = ":"*

*NOTE: Preparing runqueue*
*NOTE: Executing SetScene Tasks*
*NOTE: Executing RunQueue Tasks*
*ERROR: Function failed: do_configure (log file is located at
/home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/temp/log.do_configure.451)*
*ERROR: Logfile of failure stored in:
/home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/temp/log.do_configure.451*
*Log data follows:*
*| DEBUG: Executing python function sysroot_cleansstate*
*| DEBUG: Python function sysroot_cleansstate finished*
*| DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common',
'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common']*
*| DEBUG: Executing shell function autotools_preconfigure*
*| DEBUG: Shell function autotools_preconfigure finished*
*| DEBUG: Executing python function autotools_copy_aclocals*
*| DEBUG: Python function autotools_copy_aclocals finished*
*| DEBUG: Executing shell function do_configure*
*| automake (GNU automake) 1.14*
*| Copyright (C) 2013 Free Software Foundation, Inc.*
*| License GPLv2+: GNU GPL version 2 or later
>*
*| This is free software: you are free to change and redistribute it.*
*| There is NO WARRANTY, to the extent permitted by law.*
*| *
*| Written by Tom Tromey >*
*|and Alexandre Duret-Lutz >.*
*| AUTOV is 1*
*| NOTE: Executing ACLOCAL="aclocal
--system-acdir=/home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/build/aclocal-copy/"
autoreconf --verbose --install --force --exclude=autopoint -I
/home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/harfbuzz-1.3.0/m4/*
*| autoreconf: Entering directory `.'*
*| autoreconf: configure.ac : not using Gettext*
*| autoreconf: running: aclocal
--system-acdir=/home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/build/aclocal-copy/
-I
/home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/harfbuzz-1.3.0/m4/
-I
/home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/harfbuzz-1.3.0/m4/
--force -I m4*
*| autoreconf: configure.ac : tracing*
*| autoreconf: running: libtoolize --copy --force*
*| libtoolize: putting auxiliary files in `.'.*
*| libtoolize: copying file `./ltmain.sh'*
*| libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.*
*| libtoolize: copying file `m4/libtool.m4'*
*| libtoolize: copying file `m4/ltoptions.m4'*
*| libtoolize: copying file `m4/ltsugar.m4'*
*| libtoolize: copying file `m4/ltversion.m4'*
*| libtoolize: copying file `m4/lt~obsolete.m4'*
*| autoreconf: running:
/home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/sysroots/x86_64-linux/usr/bin/autoconf
--include=/home/bharath/Abhishek_WorkSpace/Projects/Renesas/RZG1H/iwave/build/Build_As_On_23_feb_2018/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/harfbuzz/1.3.0-r0/harfbuzz-1.3.0/m4/
--force*
*| configure:17934: error: possibly undefined macro: PKG_CONFIG_SYSROOT_DIR*
*|   If this token and others are legitimate, please use
m4_pattern_allow.*
*|   See the Autoconf documentation.*
*| autoreconf: