I took a functioning 32-bit x86 system built with Morty and successfully
converted it to 64-bit. Builds and runs fine. Next, I tried applying the
x32 tune, as described in the Yocto manual. I created another BSP layer,
changed all the names accordingly, set CONFIG_64BIT=y and CONFIG_X86_X32=y
in
Hello All,
Here is the report for the 2.2.2 rc1 full point release test cycle.
Full Report :
https://wiki.yoctoproject.org/wiki/WW22_-_2017-06-05_-_Full_Point_Release_Test_Cycle_2.2.2_rc1
Summary
The QA cycle for release 2.2.2 rc1 is complete, there were 6 new
On 06/04/2017 12:30 AM, Gary Thomas wrote:
>> Which version of opkg are you using? do you have the libsolv backend
>> enabled? running opkg --version should tell you the opkg version and the
>> libsolv version, if the backend is enabled.
>
> # opkg --version
> opkg version 0.3.4 (libsolv
merged, with a minor fixup to -rt.
Bruce
On 2017-06-02 10:04 PM, Paul Gortmaker wrote:
Bruce, Yocto kernel folks:
Here is another 4.8.x stable update. Continuing on top of the
previously released v4.8.23 kernel, we now have the appropriate content
from 4.9.18 to 4.9.21 (inclusive) applied on
Tuesday, June 6, 2017 8:00 AM US Pacific Time
Agenda:
* Opens collection - 5 min (Stephen)
* Yocto Project status - 5 min (Stephen/team)
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.3_Status
https://wiki.yoctoproject.org/wiki/Yocto_2.3_Schedule
Khem,
Fully agree that Yocto has is good, 'cause it supports cross-build, has a wide
industry support and actually it has **the version** (meaning, all the packages
are taken with specific git commit id unlike debian/ubuntu binaries).
But then, I'm confused in the other respect...
I'm
Current Dev Position: Preparing for YP 2.4 M1
Next Deadline: YP 2.4 M1 Cut off is June 12, 2017
SWAT team rotation: Anibal -> Todor on June 2, 2017.
SWAT team rotation: Todor -> Alejandro on June 9, 2017.
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
Key Status/Updates:
