[yocto] [Recipe reporting system] Upgradable recipe name list

[recipe-report]

This mail was sent out by Recipe reporting system.

This message list those recipes which need to be upgraded. If maintainers
believe some of them needn't to upgrade at this time, they can fill
RECIPE_NO_UPDATE_REASON in respective recipe file to ignore this remainder
until newer upstream version was detected.

Example:
RECIPE_NO_UPDATE_REASON = "Version 2.0 is unstable"

You can check the detail information at:

http://recipes.yoctoproject.org/

Package   VersionUpstream version  Maintainer  
NoUpgradeReason
  -    --  
--
liberation-fonts  1.04   2.00.1Alexander Kanavin   
2.x depends on fontforge pa...
gobject-introspec...  1.48.0 1.50.0Alexander Kanavin
boost 1.61.0 1.62.0Alexander Kanavin
openssl   1.0.2j 1.1.0bAlexander Kanavin
bjam-native   1.61.0 1.62.0Alexander Kanavin
vala  0.32.1 0.34.2Alexander Kanavin
valgrind  3.11.0 3.12.0Alexander Kanavin
gnome-desktop33.20.2 3.22.1Alexander Kanavin
nspr  4.12   4.13.1Alexander Kanavin
nss   3.25   3.27.1Alexander Kanavin
webkitgtk 2.12.5 2.14.1Alexander Kanavin
lighttpd  1.4.41 1.4.42Alexander Kanavin
epiphany  3.20.3 3.22.1Alexander Kanavin
ffmpeg3.1.3  3.1.5 Alexander Kanavin
dtc   1.4.1+gitX 1.4.2+gitAUTOINC+...  Alexander Kanavin
kexec-tools   2.0.12 2.0.13Alexander Kanavin
btrfs-tools   4.7.1  4.8.1 Alexander Kanavin
gnutls3.5.3  3.5.5 Alexander Kanavin
cmake 3.6.1  3.6.2 Alexander Kanavin
sysprof   3.20.0+gitX3.22.1+gitAUTOINC...  Alexander Kanavin
cmake-native  3.6.1  3.6.2 Alexander Kanavin
mpg1231.23.6 1.23.8Alexander Kanavin
mkelfimage4.0+gitX   4.5+gitAUTOINC+0b...  Alexander Kanavin   
mkelfimage has been removed...
libksba   1.3.4  1.3.5 Alexander Kanavin
icu   57.1   58.1  Alexander Kanavin
perl  5.22.1 5.24.1Aníbal Limón
apt   1.2.12 1.3.1 Aníbal Limón
apt-native1.2.12 1.3.1 Aníbal Limón
dpkg  1.18.7 1.18.10   Aníbal Limón
perl-native   5.22.1 5.24.1Aníbal Limón
pinentry  0.9.2  0.9.7 Armin Kuster
nettle3.23.3   Armin Kuster
linux-yocto-rt4.8+gitX   4.8.3+gitAUTOINC+...  Bruce Ashfield
linux-yocto-tiny  4.8+gitX   4.8.3+gitAUTOINC+...  Bruce Ashfield
linux-libc-headers4.84.8.4 Bruce Ashfield
linux-yocto   4.8+gitX   4.8.3+gitAUTOINC+...  Bruce Ashfield
guilt-native  0.35+gitX  0.36+gitAUTOINC+2...  Bruce Ashfield
pciutils  3.5.1  3.5.2 Chen Qi
curl  7.50.1 7.50.3Chen Qi
busybox   1.25.0+gitX1.25.1+gitAUTOINC...  Chen Qi
dbus-glib 0.106  0.108 Chen Qi
dbus-test 1.10.101.10.12   Chen Qi
dbus  1.10.101.10.12   Chen Qi
cups  2.1.4  2.2.1 Chen Qi
gawk  4.1.3  4.1.4 Chen Qi
systemd   230+gitX   231+gitAUTOINC+38...  Chen Qi
systemd-boot  230+gitX   231+gitAUTOINC+38...  Chen Qi
util-linux2.28.1 2.28.2Chen Qi
sudo  1.8.17p1   1.8.18p1  Chen Qi
sysstat   11.4.0 11.5.1Chen Qi
systemd-bootchart 230+gitX   231+gitAUTOINC+9e...  Chen Qi
flex  2.6.0  2.6.1 Chen Qi
grep  2.25   2.26  Chen Qi
diffutils 3.43.5   Chen Qi
build-appliance-i...  15.0.0 15.0.1Cristian Iorga
docbook-sgml-dtd-...  3.13.1">3.1/

Re: [yocto] potentially confusing intro to what is in an SDK (SDK manual)

[Khem Raj]

On Sun, Oct 23, 2016 at 7:00 AM, Robert P. J. Day  wrote:
>
>   more of the pedantic nitpickery you've all come to expect from me,
> but in section 1.1 of SDK Manual (v. 2.2):
>
> "All SDKs consist of the following:
>
> Cross-Development Toolchain: This toolchain contains a compiler,
> debugger, and various miscellaneous tools.
>
> Libraries, Headers, and Symbols: The libraries, headers, and
> symbols are specific to the image (i.e. they match the image).
>
> Environment Setup Script: This *.sh file, once run, sets up the
> cross-development environment by defining variables and preparing
> for SDK use. "
>
> hang on ... that last reference to an ".sh" file is potentially
> misleading. the generated SDK itself is bundled into the installation
> script (say,
> poky-glibc-x86_64-core-image-minimal-ppce300c3-toolchain-2.2.sh), and
> when that's run, what is installed contains, at the top level, the
> setup script "environment-setup-ppce300c3-poky-linux" -- there is no
> .sh script installed in the SDK installation directory.

it should really be something like "This shell script file, once sourced  ..."
fell free to send a patch and cc Scott.

>
>   it might be common to create the symlink for convenience:
>
> environment-setup-ppce300c3-poky-linux -> env.sh
>
> or something like that, but AFAICT, there is no ".sh" setup script in
> the SDK installation directory.
>
>   is it possible the author was conflating the installation .sh file,
> and the environment setup file?
>
> rday
>
> --
>
> 
> Robert P. J. Day Ottawa, Ontario, CANADA
> http://crashcourse.ca
>
> Twitter:   http://twitter.com/rpjday
> LinkedIn:   http://ca.linkedin.com/in/rpjday
> 
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] potentially confusing intro to what is in an SDK (SDK manual)

[Robert P. J. Day]

  more of the pedantic nitpickery you've all come to expect from me,
but in section 1.1 of SDK Manual (v. 2.2):

"All SDKs consist of the following:

Cross-Development Toolchain: This toolchain contains a compiler,
debugger, and various miscellaneous tools.

Libraries, Headers, and Symbols: The libraries, headers, and
symbols are specific to the image (i.e. they match the image).

Environment Setup Script: This *.sh file, once run, sets up the
cross-development environment by defining variables and preparing
for SDK use. "

hang on ... that last reference to an ".sh" file is potentially
misleading. the generated SDK itself is bundled into the installation
script (say,
poky-glibc-x86_64-core-image-minimal-ppce300c3-toolchain-2.2.sh), and
when that's run, what is installed contains, at the top level, the
setup script "environment-setup-ppce300c3-poky-linux" -- there is no
.sh script installed in the SDK installation directory.

  it might be common to create the symlink for convenience:

environment-setup-ppce300c3-poky-linux -> env.sh

or something like that, but AFAICT, there is no ".sh" setup script in
the SDK installation directory.

  is it possible the author was conflating the installation .sh file,
and the environment setup file?

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday


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

[yocto] [meta-qt4][PATCH] packagegroup-core-qt4e.bb: mv tslib from rdepends to rrecommends

[Max Krummenacher]

Commit c4671873af5ab6c7d15ca397538f154c11c3486e made the build of tslib a
PACKAGECONFIG. By default tslib components are not built.

Thus a build for a machine with  "MACHINE_FEATURES" "touchscreen"
fails for missing tslib components.

Signed-off-by: Max Krummenacher 
---
Alternatively or additionally one could change the default PACKAGECONFIG
in qt4-embedded.inc conditionally on MACHINE_FEATURES. If that is prefered
I could create a patch.

Max

 recipes-qt4/packagegroups/packagegroup-core-qt4e.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-qt4/packagegroups/packagegroup-core-qt4e.bb 
b/recipes-qt4/packagegroups/packagegroup-core-qt4e.bb
index 588e99b..86646e9 100644
--- a/recipes-qt4/packagegroups/packagegroup-core-qt4e.bb
+++ b/recipes-qt4/packagegroups/packagegroup-core-qt4e.bb
@@ -37,7 +37,6 @@ RDEPENDS_${PN} = " \
qt4-embedded-plugin-imageformat-tiff \
qt4-embedded-plugin-script-dbus \
qt4-embedded-plugin-sqldriver-sqlite \
-   ${TOUCH} \
 qt4-embedded-demos \
 qt4-embedded-examples \
 qt-demo-init \
@@ -47,5 +46,6 @@ RDEPENDS_${PN} = " \
 RRECOMMENDS_${PN} = " \
libqt-embeddedxmlpatterns4 \
qt4-embedded-plugin-phonon-backend-gstreamer \
+   ${TOUCH} \
 "
 
-- 
2.5.5

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

Re: [yocto] [raspberrypi3][meta-qt5] Failed to build meta-toolchain-qt5

[Karim ATIKI]

Hi Paul,

I just tried with a clean configuration.

I"ve cloned the layers as shown in the config below:

Build Configuration:
BB_VERSION= "1.32.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "Debian-8.2"
TARGET_SYS= "arm-poky-linux-gnueabi"
MACHINE   = "raspberrypi3"
DISTRO= "poky"
DISTRO_VERSION= "2.2"
TUNE_FEATURES = "arm armv7ve vfp thumb neon vfpv4 callconvention-hard 
cortexa7"
TARGET_FPU= "hard"
meta
meta-poky
meta-yocto-bsp= "master:ef627ab364d52fe19994c94c1a78fbe21620a32c"
meta-raspberrypi  = "master:de016ceef63028f5578191785c50529695f76a1a"
meta-oe
meta-multimedia   = "master:8ba31c9ba214802b1305aabbc0be0353cba0bc3e"



Created a new build and just added:

MACHINE="raspberrypi3"
DISTRO_FEATURES_remove  = " x11 wayland".

Launched: bitbake -k gstreamer1.0-plugins-bad


It failed as usual during the do_compile() of gstreamer1.0-plugins-bad as 
reported yesterday.

./.libs/libgstgl-1.0.so: undefined reference to `graphics_get_display_size'


How did you get it work on your side ?


Karim




De : Paul Barker 
Envoyé : samedi 22 octobre 2016 23:27
À : Karim ATIKI
Cc : yocto
Objet : Re: [yocto] [raspberrypi3][meta-qt5] Failed to build meta-toolchain-qt5

On Sat, 22 Oct 2016 18:59:39 +
Karim ATIKI  wrote:

> Hi ,
>
>
> I just found out something interesting.
>
> I setup a build with poky-krogoth, I didn't include any of my custom
> recipes.
>
>
> I've jsut included meta-raspberrypi in the layers.
>
> Setup a machine "raspberrypi3"
>
>
> Launched: bitbake gstreamer1.0-plugins-bad
>
>
> It worked successfully.
>
> Then, I deleted the tmp and sstate directories.
>
>
> And I added in the local.conf:
>
> DISTRO_FEATURES_remove = " x11 wayland".
>
>
> Launched: bitbake gstreamer1.0-plugins-bad
>
>
>  It failed at the exact step (see below in the conversation)
>
>
> Is there a problem with this configuration ?
>
>
> Cheers,
>
>
> Karim
>

I can't reproduce this on master. gstreamer1.0-plugins-bad compiles
without error for raspberrypi3 without x11 or wayland in
DISTRO_FEATURES on my machine.

Are you using krogoth branches of all your layers? Could you retry this
on a clean checkout of master, using the minimal set of layers
(oe-core, meta-oe, meta-multimedia and meta-raspberrypi) and see if you
see the same problem?

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