[yocto] Dependency walk for busybox recipe
Hi, How can I do a dependency walk for the busybox recipe? I've added gcc-4.5 recipe support and eglibc-2.13 support against the latest poky master branch. The core-image-minimal image works for my powerpc440 soft-float target, from an older commit id, prior to the gcc toolchain rework, and it worked correctly with gcc-4.5 and eglibc-2.13. So, as a next step after getting the image to boot correctly, I updated the recipes to work against the latest poky master. The resulting image crashed with a kernel init, when I passed init=/bin/sh. The size of the /bin/busybox or /bin/sh (soft-link) executable was 600.1kb for the older commit id, with busybox-1.19.4. The size of the busybox-1.20.2 executable a bit larger(around 608kb) but that did't work with gcc-4.5 and eglibc-2.13, and caused a kernel panic. So I added busybox-1.19.4 recipe back into my poky master branch, and the resulting size of the busybox-1.19.4 /bin/busybox or /bin/sh executable is 604.2 kb. Same gcc-4.5, eglibc-2.13 and busybox-1.19.4 recipes and srcrevs, but different executable sizes. How can I find out which packages might be contributing the extra 3.2kb to the /bin/busybox executable? I'm hoping that if I can progressively replace each recipe in the dependency chain, till I get to the original size, I might be able to atleast narrow it down to the recipe that i causing the kernel panics for the powerpc440 target. Once I do that, then I can try with a newer gcc and eglibc version. Best regards, Elvis Dowson ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 2/4] meta-intel: restore emgd 1.10
From: Tom Zanussi tom.zanu...@intel.com
The upgrade to emgd 1.14 inadvertantly removed 1.10, which is still
used by some BSPs, so restore it for them.
Signed-off-by: Tom Zanussi tom.zanu...@intel.com
---
.../xorg-driver/emgd-driver-bin_1.10.bb| 91 ++
1 file changed, 91 insertions(+)
create mode 100644 common/recipes-graphics/xorg-driver/emgd-driver-bin_1.10.bb
diff --git a/common/recipes-graphics/xorg-driver/emgd-driver-bin_1.10.bb
b/common/recipes-graphics/xorg-driver/emgd-driver-bin_1.10.bb
new file mode 100644
index 000..5779e5d
--- /dev/null
+++ b/common/recipes-graphics/xorg-driver/emgd-driver-bin_1.10.bb
@@ -0,0 +1,91 @@
+SUMMARY = EMGD 1.10 xserver binaries
+DESCRIPTION = EMGD 1.10 includes some userspace binaries that use non-free \
+licensing, which are now available via a non-click-through downloadable \
+tarball, and is what this recipe now uses. Since it is a non-free license, \
+this recipe is marked as 'License_emgd-driver-bin_1.10' and you need to add \
+to LICENSE_FLAGS_WHITELIST += \License_emgd-driver-bin_1.10\ to your \
+local.conf in order to enable it in a build.
+LICENSE = Intel-binary-only
+LICENSE_FLAGS = license_${PN}_${PV}
+PR = r1
+
+EMGD_LIC_DIR = IEMGD_HEAD_Linux/License
+EMGD_RPM_DIR = IEMGD_HEAD_Linux/MeeGo1.2
+EMGD_VIDEO_PLUGIN_DIR = ../common/video_plugin
+
+LIC_FILES_CHKSUM =
file://${WORKDIR}/${EMGD_LIC_DIR}/License.txt;md5=b54f01caaf8483b3cb60c0c40f2bf22d
+
+DEPENDS = rpm-native xz-native
+
+SRC_URI =
https://edc.intel.com/App_Shared/Downloads/LIN_EMGD_1_10_RC_2209.tgz;
+
+SRC_URI[md5sum] = e4a38d9efa0b086ae21b68145c4db4e9
+SRC_URI[sha256sum] =
acea5f0f93a31553553428623c007d7ed0c604cf715fd87dfe075751da4be548
+
+# These are closed binaries generated elsewhere so don't check ldflags
+INSANE_SKIP_${PN} = ldflags
+
+FILES_${PN} += ${libdir}/dri ${libdir}/gstreamer-0.10
${libdir}/xorg/modules/drivers
+FILES_${PN}-dbg += ${libdir}/xorg/modules/drivers/.debug ${libdir}/dri/.debug
+
+S = ${WORKDIR}/${EMGD_RPM_DIR}
+
+do_install () {
+# A gstreamer VA buffer library
+rpm2cpio ${S}/${EMGD_VIDEO_PLUGIN_DIR}/gst-vabuffer*.rpm | cpio -id
+
+# MIX Common contains common classes, datatype, header files used by other
MIX components
+rpm2cpio ${S}/${EMGD_VIDEO_PLUGIN_DIR}/mixcommon*.rpm | cpio -id
+
+# MIX Video Bitstream Parser is an user library interface for various
video format bitstream parsing
+rpm2cpio ${S}/${EMGD_VIDEO_PLUGIN_DIR}/mixvbp*.rpm | cpio -id
+
+# MIX Video is an user library interface for various video codecs
available on the platform.
+rpm2cpio ${S}/${EMGD_VIDEO_PLUGIN_DIR}/mixvideo*.rpm | cpio -id
+
+install -d -m 0755
${D}${libdir}/gstreamer-0.10
+install -m 0755 ${S}/usr/lib/*${D}${libdir}/
+
+# A gstreamer plugin that uses MIX Video for hardware accelerated video
decoding and rendering.
+rpm2cpio ${S}/${EMGD_VIDEO_PLUGIN_DIR}/gst-plugins-mixvideo*.rpm | cpio -id
+
+# A collection of gstreamer plugins that uses VA libraries for hardware
accelerated video rendering and text overlay.
+rpm2cpio ${S}/${EMGD_VIDEO_PLUGIN_DIR}/gst-plugins-va*.rpm | cpio -id
+
+install -m 0755 ${S}/usr/lib/gstreamer-0.10/*
${D}${libdir}/gstreamer-0.10/
+
+# EMGD runtime graphics libraries
+rpm2cpio ${S}/emgd-bin*.rpm | xz -d | cpio -id
+
+install -d -m 0755${D}${libdir}/dri
+install -d -m 0755
${D}${libdir}/xorg/modules/drivers
+install -d -m 0755${D}${sysconfdir}
+install -d -m 0755${D}${mandir}/man4
+install -m 0755 ${S}/usr/lib/*.so.* ${D}${libdir}/
+install -m 0755 ${S}/usr/lib/dri/*${D}${libdir}/dri/
+install -m 0755 ${S}/usr/lib/xorg/modules/drivers/*
${D}${libdir}/xorg/modules/drivers/
+install -m 0755 ${S}/etc/*${D}${sysconfdir}/
+install -m 0755 ${S}/usr/share/man/man4/* ${D}${mandir}/man4/
+
+# Khronos development headers needed for EGL, OpenGL-ES, and OpenVG
development
+rpm2cpio ${S}/emgd-devel*.rpm | xz -d | cpio -id
+
+install -d -m 0755${D}${includedir}/EGL
+install -m 0755 ${S}/usr/include/EGL/*.h
${D}${includedir}/EGL/
+install -d -m 0755
${D}${includedir}/GLES
+install -m 0755 ${S}/usr/include/GLES/*.h
${D}${includedir}/GLES/
+install -d -m 0755
${D}${includedir}/GLES2
+install -m 0755 ${S}/usr/include/GLES2/*.h
${D}${includedir}/GLES2/
+install -d -m 0755${D}${includedir}/KHR
+install -m 0755 ${S}/usr/include/KHR/*.h
${D}${includedir}/KHR/
+install -d -m 0755
[yocto] [PATCH 0/4] meta-intel: BSP updates for gst-ffmpeg LICENSE_FLAGS change, v2
From: Tom Zanussi tom.zanu...@intel.com
This patchset updates the BSPs that enable video acceleration to
make them able to handle the new LICENSE_FLAGS change to gst-ffmpeg.
There's no change to functionality if you add commercial to
LICENSE_FLAGS_WHITELIST when building; if that's not done you'll
simply get an image without video acceleration.
v2: while testing this change, I noticed that emgd-1.10 was missing
and that some BSPs still use it, and also took the opportunity to
fix a longstanding mistake in where the emgd recipes were located.
Finally, my attempts to make things build with the LICENSE_FLAGS
change by using RRECOMMENDS as suggested all met with failure, so
am keeping the method that works for now.
The following changes since commit 164e0c7418229a38d7c97cd6bb3117a89869f6a4:
meta-cedartrail: Update PVR graphics driver to version 1.0.3 (2012-09-15
14:56:30 -0500)
are available in the git repository at:
git://git.yoctoproject.org/meta-intel-contrib.git
tzanussi/va-license-flags-commercial
http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-contrib/log/?h=tzanussi/va-license-flags-commercial
Tom Zanussi (4):
meta-intel: make video acceleration choice dependent on LICENSE_FLAGS
meta-intel: restore emgd 1.10
meta-intel: have fri2 and sys940x prefer emgd-1.10
meta-intel: move emgd-driver-bin_1.14 to xorg-driver/
.../xorg-driver/emgd-driver-bin_1.10.bb| 91 ++
.../emgd-driver-bin_1.14.bb| 0
meta-cedartrail/README | 15
meta-cedartrail/conf/machine/cedartrail.conf | 3 +-
meta-chiefriver/README | 15
meta-chiefriver/conf/machine/chiefriver.conf | 3 +-
meta-crownbay/README | 15
meta-crownbay/conf/machine/crownbay.conf | 3 +-
meta-fri2/README | 15
meta-fri2/conf/machine/fri2.conf | 4 +-
meta-sugarbay/README | 15
meta-sugarbay/conf/machine/sugarbay.conf | 3 +-
meta-sys940x/README| 15
meta-sys940x/conf/machine/sys940x.conf | 4 +-
14 files changed, 195 insertions(+), 6 deletions(-)
create mode 100644 common/recipes-graphics/xorg-driver/emgd-driver-bin_1.10.bb
rename common/recipes-graphics/{xorg-xserver =
xorg-driver}/emgd-driver-bin_1.14.bb (100%)
--
1.7.11.4
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 1/4] meta-intel: make video acceleration choice dependent on LICENSE_FLAGS
From: Tom Zanussi tom.zanu...@intel.com
The gst-ffmpeg recipe in oe-core had LICENSE_FLAGS added to make it
commercial, so to avoid build errors the BSPs that use it (via the
gst-va-intel VA_FEATURE) should only include it if the user has added
commercial to LICENSE_FLAGS_WHITELIST when building.
This adds a conditional to detect that, along with a NOTE in the
README to explain the need for the flag.
Signed-off-by: Tom Zanussi tom.zanu...@intel.com
---
meta-cedartrail/README | 15 +++
meta-cedartrail/conf/machine/cedartrail.conf | 3 ++-
meta-chiefriver/README | 15 +++
meta-chiefriver/conf/machine/chiefriver.conf | 3 ++-
meta-crownbay/README | 15 +++
meta-crownbay/conf/machine/crownbay.conf | 3 ++-
meta-fri2/README | 15 +++
meta-fri2/conf/machine/fri2.conf | 3 ++-
meta-sugarbay/README | 15 +++
meta-sugarbay/conf/machine/sugarbay.conf | 3 ++-
meta-sys940x/README | 15 +++
meta-sys940x/conf/machine/sys940x.conf | 3 ++-
12 files changed, 102 insertions(+), 6 deletions(-)
diff --git a/meta-cedartrail/README b/meta-cedartrail/README
index e47151e..81a1260 100755
--- a/meta-cedartrail/README
+++ b/meta-cedartrail/README
@@ -88,6 +88,21 @@ At the end of a successful build, you should have a live
image that
you can boot from a USB flash drive (see instructions on how to do
that below, in the section 'Booting the images from /binary').
+NOTE: The 'cedartrail' machine will include support for hardware video
+acceleration via gstreamer if and only if the commercial string is
+added to the the LICENSE_FLAGS_WHITELIST variable in your local.conf.
+
+For example:
+
+ LICENSE_FLAGS_WHITELIST = license_cdv-pvr-driver_1.0.3 commercial
+
+The reason this is needed is to prevent the image from including
+anything that might violate the license terms of the packages used to
+implement the the video acceleration feature, such as gst-ffmpeg and
+ffmpeg. As always, please consult the licenses included in the
+specific packages for details if you use packages that require
+particular LICENSE_FLAGS.
+
As an alternative to downloading the BSP tarball, you can also work
directly from the meta-intel git repository. For each BSP in the
'meta-intel' repository, there are multiple branches, one
diff --git a/meta-cedartrail/conf/machine/cedartrail.conf
b/meta-cedartrail/conf/machine/cedartrail.conf
index cd9acd7..33af012 100644
--- a/meta-cedartrail/conf/machine/cedartrail.conf
+++ b/meta-cedartrail/conf/machine/cedartrail.conf
@@ -22,6 +22,7 @@ SYSLINUX_OPTS = serial 0 115200
SERIAL_CONSOLE = 115200 ttyS0
APPEND += console=ttyS0,115200 console=tty0
-VA_FEATURES ?= gst-va-intel va-intel
+VA_FEATURES = ${@bb.utils.contains(LICENSE_FLAGS_WHITELIST, \
+ commercial, gst-va-intel va-intel, , d)}
MACHINE_EXTRA_RRECOMMENDS += ${VA_FEATURES}
diff --git a/meta-chiefriver/README b/meta-chiefriver/README
index 49e4461..438c293 100644
--- a/meta-chiefriver/README
+++ b/meta-chiefriver/README
@@ -60,6 +60,21 @@ At the end of a successful build, you should have a live
image that
you can boot from a USB flash drive (see instructions on how to do
that below, in the section 'Booting the images from /binary').
+NOTE: The 'chiefriver' machine will include support for hardware video
+acceleration via gstreamer if and only if the commercial string is
+added to the the LICENSE_FLAGS_WHITELIST variable in your local.conf.
+
+For example:
+
+ LICENSE_FLAGS_WHITELIST = commercial
+
+The reason this is needed is to prevent the image from including
+anything that might violate the license terms of the packages used to
+implement the the video acceleration feature, such as gst-ffmpeg and
+ffmpeg. As always, please consult the licenses included in the
+specific packages for details if you use packages that require
+particular LICENSE_FLAGS.
+
As an alternative to downloading the BSP tarball, you can also work
directly from the meta-intel git repository. For each BSP in the
'meta-intel' repository, there are multiple branches, one
diff --git a/meta-chiefriver/conf/machine/chiefriver.conf
b/meta-chiefriver/conf/machine/chiefriver.conf
index 6d8d3a5..a9c8e5a 100644
--- a/meta-chiefriver/conf/machine/chiefriver.conf
+++ b/meta-chiefriver/conf/machine/chiefriver.conf
@@ -15,6 +15,7 @@ XSERVER ?= ${XSERVER_IA32_BASE} \
${XSERVER_IA32_I965} \
-VA_FEATURES ?= gst-va-intel va-intel
+VA_FEATURES = ${@bb.utils.contains(LICENSE_FLAGS_WHITELIST, \
+ commercial, gst-va-intel va-intel, , d)}
MACHINE_EXTRA_RRECOMMENDS += ${VA_FEATURES} lms
diff --git a/meta-crownbay/README b/meta-crownbay/README
index 2521432..f7aeffa 100644
--- a/meta-crownbay/README
+++ b/meta-crownbay/README
@@ -92,6 +92,21 @@ At the end of a successful build, you should
[yocto] [PATCH 4/4] meta-intel: move emgd-driver-bin_1.14 to xorg-driver/
From: Tom Zanussi tom.zanu...@intel.com
emgd-driver-bin should be in common/recipes-graphics/xorg-driver
rather than common/recipes-graphics/xorg-xserver so move it there.
Signed-off-by: Tom Zanussi tom.zanu...@intel.com
---
.../{xorg-xserver = xorg-driver}/emgd-driver-bin_1.14.bb | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename common/recipes-graphics/{xorg-xserver =
xorg-driver}/emgd-driver-bin_1.14.bb (100%)
diff --git a/common/recipes-graphics/xorg-xserver/emgd-driver-bin_1.14.bb
b/common/recipes-graphics/xorg-driver/emgd-driver-bin_1.14.bb
similarity index 100%
rename from common/recipes-graphics/xorg-xserver/emgd-driver-bin_1.14.bb
rename to common/recipes-graphics/xorg-driver/emgd-driver-bin_1.14.bb
--
1.7.11.4
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 3/4] meta-intel: have fri2 and sys940x prefer emgd-1.10
From: Tom Zanussi tom.zanu...@intel.com
fri2 and sys940x need to use emgd-1.10 instead of the newer 1.14.
Signed-off-by: Tom Zanussi tom.zanu...@intel.com
---
meta-fri2/conf/machine/fri2.conf | 1 +
meta-sys940x/conf/machine/sys940x.conf | 1 +
2 files changed, 2 insertions(+)
diff --git a/meta-fri2/conf/machine/fri2.conf b/meta-fri2/conf/machine/fri2.conf
index bf7754f..39fb698 100644
--- a/meta-fri2/conf/machine/fri2.conf
+++ b/meta-fri2/conf/machine/fri2.conf
@@ -25,6 +25,7 @@ XSERVER ?= ${XSERVER_IA32_BASE} \
PREFERRED_VERSION_xserver-xorg ?= 1.9.3
PREFERRED_VERSION_mesa-dri ?= 7.11
PREFERRED_VERSION_xf86-input-evdev ?= 2.6.0
+PREFERRED_VERSION_emgd-driver-bin ?= 1.10
# Syslinux does not know about the 64MHz uart clock and it does not detect the
# serial device by number. Use the IO port directly and divide the baud down to
diff --git a/meta-sys940x/conf/machine/sys940x.conf
b/meta-sys940x/conf/machine/sys940x.conf
index f71bb3a..46c4315 100644
--- a/meta-sys940x/conf/machine/sys940x.conf
+++ b/meta-sys940x/conf/machine/sys940x.conf
@@ -21,6 +21,7 @@ XSERVER ?= ${XSERVER_IA32_BASE} \
PREFERRED_VERSION_xserver-xorg ?= 1.9.3
PREFERRED_VERSION_mesa-dri ?= 7.11
PREFERRED_VERSION_xf86-input-evdev ?= 2.6.0
+PREFERRED_VERSION_emgd-driver-bin ?= 1.10
SERIAL_CONSOLE = 115200 ttyS0
APPEND += console=ttyS0,115200 console=tty0
--
1.7.11.4
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Forcing link order for autotools recipe
I've got a recipe that uses autotools. It builds ok under Poky, but if I try to build it on my host (e.g. when developing) then it fails to build with lots of 'symbol not found' link errors related to libs that are on the system and which are in the gcc lib search path. I've finally tracked this down to link order. The final command is of the form: g++ -lGL -lcurl -o binary a.o b.o If I change this to: g++ -o binary a.o b.o -lGL -lcurl then it builds ok. Stranger still is the original form works fine on another system (older Ubuntu). The ld versions are different (2.21.53 on the one that fails, 2.20.1 on the one that works). Can I get autotools to always link the libraries last? Chris Tapp opensou...@keylevel.com www.keylevel.com ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [Package Report System]Upgrade recipes name list
This mail was sent out by Package Report System. This message list those recipes which need to be upgraded. If maintainers believe some of them needn't to upgrade this time, they can fill in RECIPE_NO_UPDATE_REASON_pn-xxx in upstream_tracking files to ignore this recipe remainder until newer upstream version was detected. Example: RECIPE_NO_UPDATE_REASON_pn-xxx = Not upgrade to 2.0 because the new version is unstable You can check the detail information at http://packages.yoctoproject.org/upgradepkgname PackageName Version UpVersion MaintainerNoUpgradeReason ccache3.1.7 3.1.8 Wenzong Fan wenzong@windriver.com xdg-utils 1.0.2 1.1.0 Valentin Popa valentin.p...@intel.com only release candidates avail... libxslt 1.1.261.1.27 Valentin Popa valentin.p...@intel.com evolution-data-server 2.30+git1+3ca578d968d097 6.0 Valentin Popa valentin.p...@intel.com puzzles r9594 9660 Valentin Popa valentin.p...@intel.com matchbox-panel-2 0.0+git1+cdf7a22716b8746 2.0 Valentin Popa valentin.p...@intel.com lttng-viewer 0.12.38 0.12.38.21032011 Valentin Popa valentin.p...@intel.com sysprof 1.1.8+git1+4692f85f625f4 1.2.0 Tom Zanussi tom.zanu...@intel.com shadow4.1.4.3 4.1.5.1 Scott Garman scott.a.gar...@intel.com sudo 1.8.5p2 1.8.6 Scott Garman scott.a.gar...@intel.com blktool 4-6 4 Scott Garman scott.a.gar...@intel.com apmd 3.2.2-14 3.2.2 Scott Garman scott.a.gar...@intel.com openssh 6.0p1 6.1p1 Scott Garman scott.a.gar...@intel.com mc4.8.4 4.8.6 Saul Wold s...@linux.intel.com createrepo0.4.110.9.9 Saul Wold s...@linux.intel.com Versions after 0.9.* use YUM,... libnl 2.0 3.2.13 Saul Wold s...@linux.intel.com libnl-3.2.2 is incompatible w... apt 0.7.140.9.7.5 Saul Wold s...@linux.intel.com pkgconfig 0.25 0.27.1 Saul Wold s...@linux.intel.com removes glib-conf, adds circu... build-appliance-image 1.0 3.2.1 Saul Wold s...@linux.intel.com util-linux2.21.22.22 Saul Wold s...@linux.intel.com libxml2 2.8.0 2.9.0 Saul Wold s...@linux.intel.com resolvconf1.67 1.68 Saul Wold s...@linux.intel.com dhcp 4.2.4-P1 4.2.4 Saul Wold s...@linux.intel.com logrotate 3.8.1 3.8.2 Robert Yang liezhi.y...@windriver.com unzip 6.0 552 Radu Moisan radu.moi...@intel.com liburcu 0.6.7 0.7.4 Radu Moisan radu.moi...@intel.com curl 7.26.07.27.0 Radu Moisan radu.moi...@intel.com js1.7.0+1.8.0rc11.60 Radu Moisan radu.moi...@intel.com u-boot-mkimage2011.06 2012.07 Radu Moisan radu.moi...@intel.com valgrind 3.7.0 3.8.0 Radu Moisan
[yocto] [Package Report System]Manual check recipes name list
This mail was sent out by Package Report System. It will list all the recipes which can't check upstream version by script, and will show how long it is since their last mannual version check. You can check the detail information at http://packages.yoctoproject.org/manuallychkinfo PackageName Version LastChkVersion LastChkTime Maintainer NoUpgradeReason lsb 4.1 1.4 41166 d Yi Zhao yi.z...@windriver.co...1.4 is fixed version of LSB Te... freetype 2.4.10 2.4.10 18 days Valentin Popa valentin.popa@...No data menu-cache 0.3.3 0.3.3 16 days Valentin Popa valentin.popa@...No data libfm0.1.17 1.3017 days Valentin Popa valentin.popa@...No data pcmanfm 0.9.10 0.9.10 16 days Valentin Popa valentin.popa@...No data gtkhtml2 2.11.0+svnr11...2.11.1 18 days Valentin Popa valentin.popa@...No data e2fsprogs1.42.1 1.42.5 19 days Scott Garman scott.a.garman@...No data chrpath 0.140.1420 days Scott Garman scott.a.garman@...No data opensp 1.5.2 1.5.2 16 days Scott Garman scott.a.garman@...No data expat2.1.0 2.0.1 19 days Scott Garman scott.a.garman@...No data nfs-utils1.2.3 1.2.6 16 days Scott Garman scott.a.garman@...No data libpng 1.2.49 1.5.11 73 days Scott Garman scott.a.garman@...1.4.3 and later changes the AP... psmisc 22.19 22.19 16 days Saul Wold s...@linux.intel.co...No data cracklib 2.8.19 2.8.19 19 days Saul Wold s...@linux.intel.co...No data sysstat 10.1.1 10.1.1 13 days Saul Wold s...@linux.intel.co...No data less 444 444 18 days Saul Wold s...@linux.intel.co...No data glew 1.9.0 1.9.0 18 days Saul Wold s...@linux.intel.co...No data libexif 0.6.21 0.6.21 17 days Saul Wold s...@linux.intel.co...No data sqlite3 3.7.13 3.7.13 13 days Saul Wold s...@linux.intel.co...No data boost1.51.0 1.51.0 20 days Saul Wold s...@linux.intel.co...No data libcheck 0.9.8 0.9.8 17 days Saul Wold s...@linux.intel.co...No data sysfsutils 2.1.0 2.1.0 13 days Saul Wold s...@linux.intel.co...No data console-tools0.3.2 0.3.2 19 days Saul Wold s...@linux.intel.co...No data libmad 0.15.1b 0.15.2b 17 days Saul Wold s...@linux.intel.co...No data tzdata 2012d 2012c 10 days Radu Moisan radu.moisan@inte...No data watchdog 5.125.1213 days Radu Moisan radu.moisan@inte...No data hdparm 9.399.3918 days Radu Moisan radu.moisan@inte...No data tslib1.0 1.0 13 days Radu Moisan radu.moisan@inte...No data beecrypt
Re: [yocto] Dependency walk for busybox recipe
On Sat, Sep 15, 2012 at 10:59 AM, Elvis Dowson elvis.dow...@gmail.com wrote: So I added busybox-1.19.4 recipe back into my poky master branch, and the resulting size of the busybox-1.19.4 /bin/busybox or /bin/sh executable is 604.2 kb. make sure that .config of busybox has not changed even if you have same version backported ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
