Re: [yocto] [oe] [OE-core] OEDAM, April 8 in San Diego after ELC

[Jeff Osier-Mixon]

Just a final transportation update for those attending OEDAM.

Transportation will be via carpool. Tom, Rudi, Armin, and myself have
volunteered to drive. Together we have room for 19 out of the 20
signed up. Let's plan to meet in front of the Hyatt at 8:30am on
Friday. If you are late or otherwise unable to be there at that time,
let me know and we'll arrange alternate transportation. If you are
planning to drive yourself, please let me know so we don't wait for
you.

Armin will be driving north after the meeting, so if you ride up there
with him I will either make two trips back or arrange for a cab.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 4/6] linux-firmware: Add brcmfmac43430 firmware

[Theodor Gherzan]

I will have a look.

Theodor Gherzan

On Tue, Mar 29, 2016 at 11:06 PM, Andrei Gherzan  wrote:
> On Fri, Mar 25, 2016 at 11:34:21AM +1100, Jonathan Liu wrote:
>> Hi Theodor,
>>
>> On 10 March 2016 at 01:15, Theodor Gherzan  wrote:
>> > From: Theodor Gherzan 
>> >
>> > Signed-off-by: Theodor Gherzan 
>> > ---
>> >  .../linux-firmware/LICENSE.broadcom_brcm80211  | 205 
>> > +
>> >  .../linux-firmware/brcmfmac43430-sdio.bin  | Bin 0 -> 368957 bytes
>> >  .../linux-firmware/brcmfmac43430-sdio.txt  |  66 +++
>> >  .../linux-firmware/linux-firmware_git.bbappend |  29 +++
>> >  4 files changed, 300 insertions(+)
>> >  create mode 100644 
>> > recipes-kernel/linux-firmware/linux-firmware/LICENSE.broadcom_brcm80211
>> >  create mode 100644 
>> > recipes-kernel/linux-firmware/linux-firmware/brcmfmac43430-sdio.bin
>> >  create mode 100644 
>> > recipes-kernel/linux-firmware/linux-firmware/brcmfmac43430-sdio.txt
>> >  create mode 100644 
>> > recipes-kernel/linux-firmware/linux-firmware_git.bbappend
>>
>> I get the following warning when building an image that installs
>> linux-firmware-ralink package (but not any of the other firmware
>> packages):
>> [log_check] WARNING: The license listed Firmware-broadcom_brcm80211
>> was not in the licenses collected for recipe linux-firmware
>>
>> It seems the license is not being packaged correctly.
>>
>> Could you please have a look?
>
> Theodor,
>
> Any chance you can take a look on this?
>
> Cheers!
>
> --
> Andrei Gherzan
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Python do_install fails on QEMUX86-64 and corei7-64 under Debian 8.0.3 isolated station

[Ronald Oakes]

I'm basing off of poky-jethro-14.0.1.tar.bz as downloaded from
yoctoproject.org.  I've also got meta-intel from the git of that name
to support the corei7, my eventual target.

Ron O

On Tue, Apr 5, 2016 at 3:29 PM, Burton, Ross  wrote:
>
> On 5 April 2016 at 19:55, Ronald Oakes  wrote:
>>
>> Illegal instruction
>
>
> It probably built a binary to run on your host using compiler flags for your
> target, which means that the binary contains instructions your processor
> can't execute.
>
> What release of OE/Poky/Yocto/whatever is this?
>
> Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Python do_install fails on QEMUX86-64 and corei7-64 under Debian 8.0.3 isolated station

[Burton, Ross]

On 5 April 2016 at 19:55, Ronald Oakes  wrote:

> Illegal instruction
>

It probably built a binary to run on your host using compiler flags for
your target, which means that the binary contains instructions your
processor can't execute.

What release of OE/Poky/Yocto/whatever is this?

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

Re: [yocto] Python do_install fails on QEMUX86-64 and corei7-64 under Debian 8.0.3 isolated station

[Ronald Oakes]

I'm hand-transcribing the error (which still exists after recopying
the source files into build/downloads):

--

if test $? -ne 0; then \
 echo "generate-posix-vars failed" ; \
 rm -f ./pybuilddir.txt ; \
 exit 1 ; \
fi
Illegal instruction
make: *** [sharedmods] Error 132
WARNING: exit code 1 from a shell command.
ERROR: oe_runmake failed
ERROR: Function failed: do_install (log file is located at
/home/ron/yocto/build/tmp/work/core2-64-poky-linux/python/2.7.9-r1/temp/log.do_install.10995)

--

The log above this shows no errors, but there are some warnings.

Ron Oakes

On Tue, Apr 5, 2016 at 10:50 AM, Rudolf J Streif
 wrote:
> Hi Ron,
>
> On Tuesday, April 05, 2016 10:37:07 AM Ronald Oakes wrote:
>> When I try to build either emulated or real 64 bit distributions on an
>> isolated system running Debian 8.0.3 (using BB_NO_NETWORK = "1"),
>> utilizing a downloads directory copied from a system running Centos
>> 7.2.1511, I get a failure in the do_install step for Python.
>>
>
> Could you please post the error message from the log file of the install task 
> for Python?
>
>> I plan on recopying Python.tar.xz onto my isolated station and trying
>> again.  But, if this doesn't resolve the problem are there any
>> suggestions?
>>
>
> Considering that according to your info above the failure occurs during the 
> install task, the source package is most likely not the culprit. However, the 
> source tarball should be named something like Python-2.7.11.tar.xz which 
> includes the version number.
>
>> For what it is worth, we're probably going to be moving to newer, but
>> still isolated, build stations shortly.  These new stations will be
>> running RedHat instead of Debian if that might make a difference.
>>
>
>> Thank You
>>   Ron Oakes
>>
>
>
> Best regards,
> Rudi
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Python do_install fails on QEMUX86-64 and corei7-64 under Debian 8.0.3 isolated station

[Rudolf J Streif]

Hi Ron,

On Tuesday, April 05, 2016 10:37:07 AM Ronald Oakes wrote:
> When I try to build either emulated or real 64 bit distributions on an
> isolated system running Debian 8.0.3 (using BB_NO_NETWORK = "1"),
> utilizing a downloads directory copied from a system running Centos
> 7.2.1511, I get a failure in the do_install step for Python.
> 

Could you please post the error message from the log file of the install task 
for Python?

> I plan on recopying Python.tar.xz onto my isolated station and trying
> again.  But, if this doesn't resolve the problem are there any
> suggestions?
> 

Considering that according to your info above the failure occurs during the 
install task, the source package is most likely not the culprit. However, the 
source tarball should be named something like Python-2.7.11.tar.xz which 
includes the version number.

> For what it is worth, we're probably going to be moving to newer, but
> still isolated, build stations shortly.  These new stations will be
> running RedHat instead of Debian if that might make a difference.
> 

> Thank You
>   Ron Oakes
> 


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

[yocto] Python do_install fails on QEMUX86-64 and corei7-64 under Debian 8.0.3 isolated station

[Ronald Oakes]

When I try to build either emulated or real 64 bit distributions on an
isolated system running Debian 8.0.3 (using BB_NO_NETWORK = "1"),
utilizing a downloads directory copied from a system running Centos
7.2.1511, I get a failure in the do_install step for Python.

I plan on recopying Python.tar.xz onto my isolated station and trying
again.  But, if this doesn't resolve the problem are there any
suggestions?

For what it is worth, we're probably going to be moving to newer, but
still isolated, build stations shortly.  These new stations will be
running RedHat instead of Debian if that might make a difference.

Thank You
  Ron Oakes
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Minutes: Yocto Project Technical Team Meeting - Tuesday, Mar. 8, 2016 8:00 AM US Pacific Time

[Jolley, Stephen K]

Attendees: Stephen, Ross, Saul, Armin, Richard,



Agenda:



* Opens collection - 5 min (Stephen)

* Yocto Project status - 5 min (Stephen/team)

https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.1_Status

https://wiki.yoctoproject.org/wiki/Yocto_2.1_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_2.1_Features

https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.2_Status

https://wiki.yoctoproject.org/wiki/Yocto_2.2_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_2.2_Features

YP 2.1 M3 rc2 - is almost out of QA. 
https://wiki.yoctoproject.org/wiki/2.1_QA_Status shows it is almost complete.

YP 2.1 M4 will be built as soon as we have most of the bugs found in M3 cleaned 
up.  Once we get clean QA reports on a M4 build we will release M4 as YP 2.1 
final.

YP 2.2 Planning - YP 2.2 is in active planning, but dates for the milestones 
haven't yet be fixed.  See the above links.

* Opens - 10 min

Armin - LTS - We discussed the need for support after a release goes to 
community support.  Discussion will continue.



* Team Sharing - 10 min




Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*   Work Telephone:  (503) 712-0534
*Cell:(208) 244-4460
* Email: stephen.k.jol...@intel.com

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

Re: [yocto] [PATCH][opkg-utils] opkg-build: Exit when fail to list files.

[Alejandro del Castillo]

On 04/01/2016 09:50 AM, Aníbal Limón wrote:

Hi,

Comments below,

alimon


On 03/31/2016 11:26 PM, Mike Looijmans wrote:

On 31-03-16 23:27, Aníbal Limón wrote:

We have an issue when ls segfaults in some cases [1] so it's
better to detect the failure at this level instead of continue
the build process.

[YOCTO #8926]

[1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=8926#c0

Signed-off-by: Aníbal Limón 
---
   opkg-build | 8 
   1 file changed, 8 insertions(+)

diff --git a/opkg-build b/opkg-build
index 98008b6..a9ccad2 100755
--- a/opkg-build
+++ b/opkg-build
@@ -53,6 +53,10 @@ pkg_appears_sane() {
   echo "*** Warning: The following files have names ending in
'~'.
   You probably want to remove them: " >&2
   ls -ld $tilde_files
+if [ $? -ne 0 ]; then


Instead of using $? you could just use the result of "ls" directly, i.e.:


Do you have any specific reason for not use $? variable?, for me is more
simple to test the exit status in this way.


Using $? works, but I agree with Mike: I think it's cleaner to directly test
the result of ls (and avoids and extra line).


if ! ls -ld $tilde_files; then



+echo "*** Error: Fail to list files have names ending in
'~'."
+exit 1
+fi
   echo >&2
   else
   echo "*** Removing the following files: $tilde_files"
@@ -66,6 +70,10 @@ You probably want to remove them: " >&2
   echo "*** Warning: The following files have a UID greater
than 99.
   You probably want to chown these to a system user: " >&2
   ls -ld $large_uid_files
+if [ $? -ne 0 ]; then
+echo "*** Error: Fail to list files have a UID greater
than 99."
+exit 1
+fi
   echo >&2
   fi




--
Cheers,

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

[yocto] [meta-raspberrypi][PATCH] Change serial console for Raspberry Pi 3

[Martin Bergek]

With the Raspberry Pi 3 the serial ports ttyS0 and ttyAMA0 have been switched 
around. This causes an issue with the serial console that has previously been 
set to ttyAMA0, causing the boot process to halt. I have a 100% failure rate 
when booting a Raspberry Pi 3 image built using the master branch of 
meta-raspberrypi. After a lot of testing it appears that the system fails to 
boot whenever the kernel command line specifies a console - regardless of 
whether it is ttyAMA0 or ttyS0.

This patch changes the serial console and kernel command line to use default 
values, allowing the raspberrypi3 machine configuration to assign different 
values and to remove the kernel console. Now I get the console output to the 
screen but at least it boots. Not sure if this is an acceptable way of doing it 
but it fixed my problem.

This patch has been verified on both the 4.1 and 4.4 kernel. It has also been 
tested with the raspberrypi2 machine configuration.

Signed-off-by: Martin Bergek 
---
conf/machine/include/rpi-base.inc  | 2 +-
conf/machine/raspberrypi3.conf | 4 
recipes-kernel/linux/linux-raspberrypi.inc | 2 +-
3 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/conf/machine/include/rpi-base.inc 
b/conf/machine/include/rpi-base.inc
index 792150e..5d6280b 100644
--- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc
@@ -7,7 +7,7 @@ include conf/machine/include/soc-family.inc

IMAGE_FSTYPES ?= "tar.bz2 ext3 rpi-sdimg"

-SERIAL_CONSOLE = "115200 ttyAMA0"
+SERIAL_CONSOLE ?= "115200 ttyAMA0"

XSERVER = " \
xserver-xorg \
diff --git a/conf/machine/raspberrypi3.conf b/conf/machine/raspberrypi3.conf
index 1b73f2f..2c76dc2 100644
--- a/conf/machine/raspberrypi3.conf
+++ b/conf/machine/raspberrypi3.conf
@@ -6,4 +6,8 @@ MACHINEOVERRIDES = "raspberrypi2:${MACHINE}"

MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-brcm43430"

+# Change serial console due to swapped ttyAMA0 and ttyS0 on the Raspberry Pi 3
+SERIAL_CONSOLE = "115200 ttyS0"
+CMDLINE = "dwc_otg.lpm_enable=0 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait"
+
include conf/machine/raspberrypi2.conf
diff --git a/recipes-kernel/linux/linux-raspberrypi.inc 
b/recipes-kernel/linux/linux-raspberrypi.inc
index 24e7fe2..a3fe61a 100644
--- a/recipes-kernel/linux/linux-raspberrypi.inc
+++ b/recipes-kernel/linux/linux-raspberrypi.inc
@@ -20,7 +20,7 @@ KERNEL_DEFCONFIG_raspberrypi ?= "bcmrpi_defconfig"
KERNEL_DEFCONFIG_raspberrypi2 ?= "bcm2709_defconfig"

# CMDLINE for raspberrypi
-CMDLINE = "dwc_otg.lpm_enable=0 console=ttyAMA0,115200 root=/dev/mmcblk0p2 
rootfstype=ext4 rootwait"
+CMDLINE ?= "dwc_otg.lpm_enable=0 console=ttyAMA0,115200 root=/dev/mmcblk0p2 
rootfstype=ext4 rootwait"

# Add the kernel debugger over console kernel command line option if enabled
CMDLINE_append = ' ${@base_conditional("ENABLE_KGDB", "1", 
"kgdboc=ttyAMA0,115200", "", d)}'
-- 
2.5.0



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