Skip to contentSkip to conversation

Community Chest

GIT PULL Saul Wold 4 participants 23 messages Jan 31, 2012

lore
Share & tools
lore

Saul Wold

author
#0 lore raw

Richard,

Kernel Update from Bruce, they need a meta-yocto change set also. I pulled the first part of Steve's GNUGP changes, but not the enabling part since that is getting tweaked still.

Generally the other changes seems ok, autobuilder is still chugging away on the MUT branch.

Sau!

The following changes since commit d7b13cd42ab8d5f44f97e119b73ec2e363677d26:

useradd.bbclass: Fix missing quote (2012-01-27 23:57:33 +0000)

are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib sgw/stage
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=sgw/stage

Andrea Adami (2):
image_types.bbclass: refactor cpio images generation.
tzdata_2011n: provide pkg_postinst and timezone defaults

Bruce Ashfield (3):
kern-tools: import config audit and branch manipulation updates
linux-yocto: add kernel 3.2.2 support
linux-yocto: update to v3.0.18 + features

Eric Bénard (1):
qt4-tools-nativesdk-4.8.0: fix build

Khem Raj (4):
gdb-common: Drop elfutils from DEPENDS
arm/tune: Correct the logic which added thumb-interwork to OVERRIDES tunearch/arm: Differentiate between thumb code generation and thumb
capability
tune-thumb.inc: Delete

Koen Kooi (3):
alsa-state: fix RDEPENDS assignment
alsa-utils: make alsa-utils-alsactl recommend alsa-states
classes: replace 'Poky' with 'OE-core'

Martin Jansa (1):
rootfs_ipk: remove runtime_script_required usage

Saul Wold (3):
default-providers: add kbd as PREFERRED_PROVIDER for console-tools
gcc-runtime: fix override from poky-lsb to linuxstdbase
genext2fs: fix inode computation

Steve Sakoman (2):
libksba: add recipe for 1.2.0
gnupg: add recipe for 2.0.18

 meta/classes/image_types.bbclass                   |   21 +++++-
 meta/classes/package.bbclass                       |    2 +-
 meta/classes/package_rpm.bbclass                   |   10 ++--
 meta/classes/rootfs_ipk.bbclass                    |    2 +-
 meta/classes/sanity.bbclass                        |    2 +-
 meta/classes/staging.bbclass                       |    2 +-
 meta/classes/toolchain-scripts.bbclass             |    2 +-
 meta/conf/distro/include/default-providers.inc     |    2 +-
 .../conf/machine/include/arm/feature-arm-thumb.inc |   20 +++++--
 meta/conf/machine/include/tune-strongarm1100.inc   |    4 +-
 meta/conf/machine/include/tune-thumb.inc           |   32 ----------
 meta/recipes-bsp/alsa-state/alsa-state.bb          |    5 +-
 meta/recipes-devtools/gcc/gcc-runtime_4.6.bb       |    2 +-
 meta/recipes-devtools/gdb/gdb-common.inc           |    6 +-
 .../genext2fs-1.4.1/fix-nbblocks-cast.patch        |   35 +++++++++++
 meta/recipes-devtools/genext2fs/genext2fs_1.4.1.bb |    4 +-
 meta/recipes-extended/tzdata/tzdata_2011n.bb       |   62 ++++++++++++++++++-
 .../kern-tools/kern-tools-native_git.bb            |    2 +-
 meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb    |    8 +-
 meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb    |   37 ++++++++++++
 meta/recipes-kernel/linux/linux-yocto_3.0.bb       |   19 +++---
 meta/recipes-kernel/linux/linux-yocto_3.2.bb       |   41 +++++++++++++
 .../recipes-multimedia/alsa/alsa-utils_1.0.24.2.bb |    4 +-
 .../qt4/{files => qt-4.7.4}/configure-lflags.patch |    0
 .../recipes-qt/qt4/qt-4.8.0/configure-lflags.patch |   18 ++++++
 meta/recipes-qt/qt4/qt4-tools-nativesdk.inc        |   10 ++-
 meta/recipes-qt/qt4/qt4-tools-nativesdk_4.7.4.bb   |    3 +-
 meta/recipes-support/gnupg/gnupg_2.0.18.bb         |   25 ++++++++
 meta/recipes-support/libksba/libksba_1.2.0.bb      |   12 ++++
 29 files changed, 305 insertions(+), 87 deletions(-)
 delete mode 100644 meta/conf/machine/include/tune-thumb.inc
 create mode 100644 meta/recipes-devtools/genext2fs/genext2fs-1.4.1/fix-nbblocks-cast.patch
 create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
 create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.2.bb
 rename meta/recipes-qt/qt4/{files => qt-4.7.4}/configure-lflags.patch (100%)
 create mode 100644 meta/recipes-qt/qt4/qt-4.8.0/configure-lflags.patch
 create mode 100644 meta/recipes-support/gnupg/gnupg_2.0.18.bb
 create mode 100644 meta/recipes-support/libksba/libksba_1.2.0.bb
Signature · 1 line
1.7.6.5
author
#1 lore raw

[CONSOLIDATED PULL 01/19] default-providers: add kbd as PREFERRED_PROVIDER for console-tools

kbd is used a primary provider for console-tools

---
 meta/conf/distro/include/default-providers.inc |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
meta/conf/distro/include/default-providers.inc +1 -1
index efa8117..667f3ba 100644
@@ -32,4 +32,4 @@ PREFERRED_PROVIDER_matchbox-panel ?= "matchbox-panel-2"
 PREFERRED_PROVIDER_opkg ?= "opkg"
 PREFERRED_PROVIDER_opkg-native ?= "opkg-native"
 PREFERRED_PROVIDER_opkg-nativesdk ?= "opkg-nativesdk"
-
+PREFERRED_PROVIDER_console-tools ?= "kbd"
Signature · 1 line
1.7.6.5
author
#2 lore raw

[CONSOLIDATED PULL 02/19] gcc-runtime: fix override from poky-lsb to linuxstdbase

In reply to Saul Wold
---
 meta/recipes-devtools/gcc/gcc-runtime_4.6.bb |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
meta/recipes-devtools/gcc/gcc-runtime_4.6.bb +1 -1
index 97468db..a2fb200 100644
@@ -5,4 +5,4 @@ require gcc-package-runtime.inc
 ARCH_FLAGS_FOR_TARGET += "-isystem${STAGING_INCDIR}"
 
 EXTRA_OECONF += "--disable-libunwind-exceptions"
-EXTRA_OECONF_append_poky-lsb = " --enable-clocale=gnu"
+EXTRA_OECONF_append_linuxstdbase = " --enable-clocale=gnu"
Signature · 1 line
1.7.6.5
author
#3 lore raw

[CONSOLIDATED PULL 03/19] rootfs_ipk: remove runtime_script_required usage

In reply to Saul Wold

From: Martin Jansa <[email protected]>

* it was introduced in 87780fc09b066525e47d0f50ee5497db54d304cd
* then partially removed in 2feba313c991170747381c7cf821a45c2cd04632
* so remove this use too as runtime_script_required is not initialized anymore and results in run.do_rootfs.6328: line 235: [: -eq: unary operator expected

---
 meta/classes/rootfs_ipk.bbclass |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
meta/classes/rootfs_ipk.bbclass +1 -1
index 48fb2fb..5342035 100644
@@ -90,7 +90,7 @@ fakeroot rootfs_ipk_do_rootfs () {
 	rm -f ${IMAGE_ROOTFS}${opkglibdir}/lists/*
 
 	if ${@base_contains("IMAGE_FEATURES", "package-management", "false", "true", d)}; then
-		if [ $runtime_script_required -eq 0 ]; then
+		if ! grep Status:.install.ok.unpacked ${IMAGE_ROOTFS}${opkglibdir}status; then
 			# All packages were successfully configured.
 			# update-rc.d, base-passwd are no further use, remove them now
 			opkg-cl ${IPKG_ARGS} --force-depends remove update-rc.d base-passwd || true
Signature · 1 line
1.7.6.5
author
#4 lore raw

[CONSOLIDATED PULL 04/19] image_types.bbclass: refactor cpio images generation.

In reply to Saul Wold

From: Andrea Adami <[email protected]>

* Add common check for the presence of an /init
* symlink, being 'touch' would fail with it
* and 'touch -h' is not yet generally supported
* (depends on distro on build host).

---
 meta/classes/image_types.bbclass |   21 +++++++++++++++++----
 1 files changed, 17 insertions(+), 4 deletions(-)
meta/classes/image_types.bbclass +17 -4
index 4908ed9..eef554d 100644
@@ -115,16 +115,29 @@ IMAGE_CMD_tar = "cd ${IMAGE_ROOTFS} && tar -cvf ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME
 IMAGE_CMD_tar.gz = "cd ${IMAGE_ROOTFS} && tar -zcvf ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.tar.gz ."
 IMAGE_CMD_tar.bz2 = "cd ${IMAGE_ROOTFS} && tar -jcvf ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.tar.bz2 ."
 IMAGE_CMD_tar.xz = "cd ${IMAGE_ROOTFS} && tar --xz -cvf ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.tar.xz ."
-IMAGE_CMD_cpio () {
+
+CPIO_TOUCH_INIT () {
+	if [ ! -L ${IMAGE_ROOTFS}/init ]
+	then
 	touch ${IMAGE_ROOTFS}/init
+	fi
+}
+IMAGE_CMD_cpio () {
+	${CPIO_TOUCH_INIT}
 	cd ${IMAGE_ROOTFS} && (find . | cpio -o -H newc >${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.cpio)
 }
 IMAGE_CMD_cpio.gz () {
-	touch ${IMAGE_ROOTFS}/init
+	${CPIO_TOUCH_INIT}
 	cd ${IMAGE_ROOTFS} && (find . | cpio -o -H newc | gzip -c -9 >${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.cpio.gz)
 }
-IMAGE_CMD_cpio.xz = "type cpio >/dev/null; cd ${IMAGE_ROOTFS} && (find . | cpio -o -H newc | xz -c ${XZ_COMPRESSION_LEVEL} --check=${XZ_INTEGRITY_CHECK} > ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.cpio.xz) ${EXTRA_IMAGECMD}"
-IMAGE_CMD_cpio.lzma = "type cpio >/dev/null; cd ${IMAGE_ROOTFS} && (find . | cpio -o -H newc | xz --format=lzma -c ${XZ_COMPRESSION_LEVEL} --check=${XZ_INTEGRITY_CHECK} >${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.cpio.lzma) ${EXTRA_IMAGECMD}"
+IMAGE_CMD_cpio.xz () {
+	${CPIO_TOUCH_INIT}
+	cd ${IMAGE_ROOTFS} && (find . | cpio -o -H newc | xz -c ${XZ_COMPRESSION_LEVEL} --check=${XZ_INTEGRITY_CHECK} > ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.cpio.xz) ${EXTRA_IMAGECMD}
+}
+IMAGE_CMD_cpio.lzma () {
+	${CPIO_TOUCH_INIT}
+	cd ${IMAGE_ROOTFS} && (find . | cpio -o -H newc | xz --format=lzma -c ${XZ_COMPRESSION_LEVEL} --check=${XZ_INTEGRITY_CHECK} >${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.cpio.lzma) ${EXTRA_IMAGECMD}
+}
 
 UBI_VOLNAME ?= "${MACHINE}-rootfs"
 
Signature · 1 line
1.7.6.5
author
#5 lore raw

[CONSOLIDATED PULL 05/19] genext2fs: fix inode computation

In reply to Saul Wold

This patch fixes a problem with the computation of inodes based on the bytes_per_inode options, for a larger FS (> 2G) the inode count would go negative and a smaller default count would be used, this would cause the FS to run out of inodes.

---
 .../genext2fs-1.4.1/fix-nbblocks-cast.patch        |   35 ++++++++++++++++++++
 meta/recipes-devtools/genext2fs/genext2fs_1.4.1.bb |    4 ++-
 2 files changed, 38 insertions(+), 1 deletions(-)
 create mode 100644 meta/recipes-devtools/genext2fs/genext2fs-1.4.1/fix-nbblocks-cast.patch
meta/recipes-devtools/genext2fs/genext2fs-1.4.1/fix-nbblocks-cast.patch new file +35 -0
new file mode 100644
index 0000000..3fd15e0
@@ -0,0 +1,35 @@
+
+This patch fixes up the computation of nbinodes which would go
+negative due to an int overflow issue when nbblocks > 2Meg for
+a 2Gig or greater filesystem.
+
+The computation is now done as a float equation, since both nbblocks
+and bytes_per_inode are no floats, and then cast to int by assignment.
+
+int tmp_nbinodes = nbblocks * BLOCKSIZE / bytes_per_inode;
+
+Upstream-Status: Submitted
+Signed-off-by: Saul Wold <[email protected]>
+
+Index: genext2fs-1.4.1/genext2fs.c
+===================================================================
+--- genext2fs-1.4.1.orig/genext2fs.c
++++ genext2fs-1.4.1/genext2fs.c
+@@ -2447,7 +2447,7 @@ extern int optind, opterr, optopt;
+ int
+ main(int argc, char **argv)
+ {
+-	int nbblocks = -1;
++	float nbblocks = -1;
+ 	int nbinodes = -1;
+ 	int nbresrvd = -1;
+ 	float bytes_per_inode = -1;
+@@ -2609,7 +2609,7 @@ main(int argc, char **argv)
+ 		}
+ 		if(fs_timestamp == -1)
+ 			fs_timestamp = time(NULL);
+-		fs = init_fs(nbblocks, nbinodes, nbresrvd, holes, fs_timestamp);
++		fs = init_fs((int)nbblocks, nbinodes, nbresrvd, holes, fs_timestamp);
+ 	}
+ 	
+ 	populate_fs(fs, dopt, didx, squash_uids, squash_perms, fs_timestamp, NULL);
meta/recipes-devtools/genext2fs/genext2fs_1.4.1.bb +3 -1
index 9364bb8..012ec6c 100644
@@ -1,6 +1,8 @@
 require genext2fs.inc
 
-PR = "r0"
+PR = "r1"
+
+SRC_URI += "file://fix-nbblocks-cast.patch"
 
 SRC_URI[md5sum] = "b7b6361bcce2cedff1ae437fadafe53b"
 SRC_URI[sha256sum] = "404dbbfa7a86a6c3de8225c8da254d026b17fd288e05cec4df2cc7e1f4feecfc"
Signature · 1 line
1.7.6.5
author
#6 lore raw

[CONSOLIDATED PULL 06/19] qt4-tools-nativesdk-4.8.0: fix build

In reply to Saul Wold

From: Eric Bénard <[email protected]>

the build is actually failing because host g++ and ld are used to compile and link

---
 .../qt4/{files => qt-4.7.4}/configure-lflags.patch |    0
 .../recipes-qt/qt4/qt-4.8.0/configure-lflags.patch |   18 ++++++++++++++++++
 meta/recipes-qt/qt4/qt4-tools-nativesdk.inc        |   10 +++++++---
 meta/recipes-qt/qt4/qt4-tools-nativesdk_4.7.4.bb   |    3 ++-
 4 files changed, 27 insertions(+), 4 deletions(-)
 rename meta/recipes-qt/qt4/{files => qt-4.7.4}/configure-lflags.patch (100%)
 create mode 100644 meta/recipes-qt/qt4/qt-4.8.0/configure-lflags.patch
meta/recipes-qt/qt4/qt-4.7.4/configure-lflags.patch renamed from meta/recipes-qt/qt4/files/configure-lflags.patch +0 -0
similarity index 100%
rename from meta/recipes-qt/qt4/files/configure-lflags.patch
rename to meta/recipes-qt/qt4/qt-4.7.4/configure-lflags.patch
meta/recipes-qt/qt4/qt-4.8.0/configure-lflags.patch new file +18 -0
new file mode 100644
index 0000000..d74f7fd
@@ -0,0 +1,18 @@
+qt4-tools-native: set LFLAGS to pick up zlib from staging
+
+Original Author: Jeremy Lainé <[email protected]>
+Upstream-Status: Pending
+
+Index: qt-everywhere-opensource-src-4.8.0/configure
+===================================================================
+--- qt-everywhere-opensource-src-4.8.0.orig/configure
++++ qt-everywhere-opensource-src-4.8.0/configure
+@@ -611,7 +611,7 @@ fi
+ # initalize variables
+ #-------------------------------------------------------------------------------
+ 
+-SYSTEM_VARIABLES="RANLIB STRIP OBJDUMP LD CC CXX CFLAGS CXXFLAGS LDFLAGS"
++SYSTEM_VARIABLES="RANLIB STRIP OBJDUMP LD CC CXX CFLAGS CXXFLAGS LDFLAGS LFLAGS"
+ for varname in $SYSTEM_VARIABLES; do
+     qmakevarname="${varname}"
+     # use LDFLAGS for autoconf compat, but qmake uses QMAKE_LFLAGS
meta/recipes-qt/qt4/qt4-tools-nativesdk.inc +7 -3
index 275fdcc..4b097cf 100644
@@ -4,7 +4,7 @@ SECTION = "libs"
 HOMEPAGE = "http://qt.nokia.com"
 LICENSE = "LGPLv2.1 | GPLv3"
 
-INC_PR = "r7"
+INC_PR = "r8"
 
 FILESEXTRAPATHS =. "${FILE_DIRNAME}/qt-${PV}:"
 
@@ -12,7 +12,6 @@ inherit nativesdk qmake2
 
 SRC_URI = "http://get.qt.nokia.com/qt/source/qt-everywhere-opensource-src-${PV}.tar.gz \
            file://configure-lflags.patch \
-           file://compile.test-lflags.patch \
            file://qt-config.patch \
            file://qmake-exists-check.patch \
            file://configure-paths.patch \
@@ -51,12 +50,18 @@ EXTRA_OECONF = "-prefix ${prefix} \
 EXTRA_OEMAKE = " "
 
 do_configure() {
+    # Avoid problems with Qt 4.8.0 configure setting QMAKE_LINK from LD (since we want the linker to be g++)
+    unset LD
+
     if [ ! -e mkspecs/${TARGET_OS}-oe-g++ ]; then
         ln -sf linux-g++ mkspecs/${TARGET_OS}-oe-g++
     fi
 
     cp ../g++.conf mkspecs/common
     cp ../linux.conf mkspecs/common
+    # don't use host g++ even during configure
+    sed -i -e "s#g++#${CXX}#" mkspecs/common/g++-base.conf
+    sed -i -e "s#gcc#${CC}#" mkspecs/common/g++-base.conf
 
     # first launch configure to get qmake compiled for the nativesdk
     (echo o; echo yes) | CC="${CC}" CXX="${CXX}" ./configure ${EXTRA_OECONF} || true
@@ -66,7 +71,6 @@ do_configure() {
     if [ ! -e bin/qmake ]; then
         ln -sf ${STAGING_BINDIR_NATIVE}/qmake2 bin/qmake
     fi
-
     (echo o; echo yes) | CC="${CC}" CXX="${CXX}" ./configure ${EXTRA_OECONF} || die "Configuring qt failed. EXTRA_OECONF was ${EXTRA_OECONF}"
 }
 
meta/recipes-qt/qt4/qt4-tools-nativesdk_4.7.4.bb +2 -1
index 4c90d57..ea5e13d 100644
@@ -3,7 +3,8 @@ require qt4-tools-nativesdk.inc
 PR = "${INC_PR}.0"
 
 SRC_URI += "file://blacklist-diginotar-certs.diff \
-            file://fix-qtbug-20925.patch"
+            file://fix-qtbug-20925.patch \
+            file://compile.test-lflags.patch "
 
 SRC_URI[md5sum] = "9831cf1dfa8d0689a06c2c54c5c65aaf"
 SRC_URI[sha256sum] = "97195ebce8a46f9929fb971d9ae58326d011c4d54425389e6e936514f540221e"
Signature · 1 line
1.7.6.5
author
#7 lore raw

[CONSOLIDATED PULL 07/19] alsa-state: fix RDEPENDS assignment

In reply to Saul Wold

From: Koen Kooi <[email protected]>

---
 meta/recipes-bsp/alsa-state/alsa-state.bb |    5 ++---
 1 files changed, 2 insertions(+), 3 deletions(-)
meta/recipes-bsp/alsa-state/alsa-state.bb +2 -3
index bc17b25..83c9faa 100644
@@ -10,7 +10,7 @@ sound state at system boot and save it at system shut down."
 LICENSE = "MIT"
 LIC_FILES_CHKSUM = "file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
 PV = "0.2.0"
-PR = "r0"
+PR = "r2"
 
 SRC_URI = "\
   file://asound.conf \
@@ -18,8 +18,6 @@ SRC_URI = "\
   file://alsa-state \
 "
 
-RDEPENDS = "alsa-utils-alsactl"
-
 inherit update-rc.d
 
 INITSCRIPT_NAME = "alsa-state"
@@ -39,6 +37,7 @@ PACKAGES += "alsa-states"
 
 RRECOMMENDS_alsa-state = "alsa-states"
 
+RDEPENDS_${PN} = "alsa-utils-alsactl"
 FILES_${PN} = "${sysconfdir}/init.d ${sysconfdir}/asound.conf"
 CONFFILES_${PN} = "${sysconfdir}/asound.conf"
 
Signature · 1 line
1.7.6.5
author
#8 lore raw

[CONSOLIDATED PULL 08/19] alsa-utils: make alsa-utils-alsactl recommend alsa-states

In reply to Saul Wold

From: Koen Kooi <[email protected]>

This will drag in the asound.state from the BSP that alsactl uses.

---
 .../recipes-multimedia/alsa/alsa-utils_1.0.24.2.bb |    4 +++-
 1 files changed, 3 insertions(+), 1 deletions(-)
meta/recipes-multimedia/alsa/alsa-utils_1.0.24.2.bb +3 -1
index 196128e..e62a0f3 100644
@@ -6,7 +6,7 @@ LICENSE = "GPLv2+"
 LIC_FILES_CHKSUM = "file://COPYING;md5=393a5ca445f6965873eca0259a17f833 \
                     file://alsactl/utils.c;beginline=1;endline=20;md5=fe9526b055e246b5558809a5ae25c0b9"
 DEPENDS = "alsa-lib ncurses libsamplerate0"
-PR = "r4"
+PR = "r5"
 
 SRC_URI = "ftp://ftp.alsa-project.org/pub/utils/alsa-utils-${PV}.tar.bz2 \
            file://ncursesfix.patch \
@@ -79,4 +79,6 @@ DESCRIPTION_alsa-utils-alsactl      = "saves/restores ALSA-settings in /etc/asou
 DESCRIPTION_alsa-utils-alsaconf     = "a bash script that creates ALSA configuration files"
 DESCRIPTION_alsa-utils-alsaucm      = "ALSA Use Case Manager"
 
+RRECOMMENDS_alsa-utils-alsactl = "alsa-states"
+
 ALLOW_EMPTY_alsa-utils = "1"
Signature · 1 line
1.7.6.5
author
#9 lore raw

[CONSOLIDATED PULL 09/19] classes: replace 'Poky' with 'OE-core'

In reply to Saul Wold

From: Koen Kooi <[email protected]>

---
 meta/classes/package.bbclass           |    2 +-
 meta/classes/package_rpm.bbclass       |   10 +++++-----
 meta/classes/sanity.bbclass            |    2 +-
 meta/classes/staging.bbclass           |    2 +-
 meta/classes/toolchain-scripts.bbclass |    2 +-
 5 files changed, 9 insertions(+), 9 deletions(-)
meta/classes/package.bbclass +1 -1
index 45447e3..68a2539 100644
@@ -690,7 +690,7 @@ python split_and_strip_files () {
 		debuglibdir = "/usr/lib/debug"
 		debugsrcdir = "/usr/src/debug"
 	else:
-		# Original Poky, a.k.a. ".debug", style debug info
+		# Original OE-core, a.k.a. ".debug", style debug info
 		debugappend = ""
 		debugdir = "/.debug"
 		debuglibdir = ""
meta/classes/package_rpm.bbclass +5 -5
index bac9de5..a813c8b 100644
@@ -359,7 +359,7 @@ package_install_internal_rpm () {
 		done
 	fi
 
-	#### Note: 'Recommends' is an arbitrary tag that means _SUGGESTS_ in Poky..
+	#### Note: 'Recommends' is an arbitrary tag that means _SUGGESTS_ in OE-core..
 	# Add any recommended packages to the image
 	# RPM does not solve for recommended packages because they are optional...
 	# So we query them and tree them like the ATTEMPTONLY packages above...
@@ -720,7 +720,7 @@ python write_specfile () {
 					splitrobsoletes = dep
 
 		print_deps(splitrdepends,	"Requires", spec_preamble_bottom, d)
-		# Suggests in RPM are like recommends in Poky!
+		# Suggests in RPM are like recommends in OE-core!
 		print_deps(splitrrecommends,	"Suggests", spec_preamble_bottom, d)
 		# While there is no analog for suggests... (So call them recommends for now)
 		print_deps(splitrsuggests, 	"Recommends", spec_preamble_bottom, d)
@@ -811,7 +811,7 @@ python write_specfile () {
 
 	print_deps(srcdepends,		"BuildRequires", spec_preamble_top, d)
 	print_deps(srcrdepends,		"Requires", spec_preamble_top, d)
-	# Suggests in RPM are like recommends in Poky!
+	# Suggests in RPM are like recommends in OE-core!
 	print_deps(srcrrecommends,	"Suggests", spec_preamble_top, d)
 	# While there is no analog for suggests... (So call them recommends for now)
 	print_deps(srcrsuggests, 	"Recommends", spec_preamble_top, d)
@@ -960,7 +960,7 @@ python do_package_rpm () {
 		outfile.write("\tprintf \"%s\\n\" ${line}\n")
 		outfile.write("done\n")
 
-	# Poky dependencies a.k.a. RPM requires
+	# OE-core dependencies a.k.a. RPM requires
 	outdepends = workdir + "/" + srcname + ".requires"
 
 	try:
@@ -974,7 +974,7 @@ python do_package_rpm () {
 	dependsfile.close()
 	os.chmod(outdepends, 0755)
 
-	# Poky / RPM Provides
+	# OE-core / RPM Provides
 	outprovides = workdir + "/" + srcname + ".provides"
 
 	try:
meta/classes/sanity.bbclass +1 -1
index 53584ee..a029428 100644
@@ -5,7 +5,7 @@
 SANITY_REQUIRED_UTILITIES ?= "patch diffstat texi2html makeinfo svn bzip2 tar gzip gawk chrpath wget cpio"
 
 def raise_sanity_error(msg):
-    bb.fatal(""" Poky's config sanity checker detected a potential misconfiguration.
+    bb.fatal(""" OE-core's config sanity checker detected a potential misconfiguration.
     Either fix the cause of this error or at your own risk disable the checker (see sanity.conf).
     Following is the list of potential problems / advisories:
     
meta/classes/staging.bbclass +1 -1
index 9c9df6a..66314a7 100644
@@ -115,7 +115,7 @@ addtask do_populate_sysroot_setscene
 
 python () {
     if d.getVar('do_stage', True) is not None:
-        bb.fatal("Legacy staging found for %s as it has a do_stage function. This will need conversion to a do_install or often simply removal to work with Poky" % d.getVar("FILE", True))
+        bb.fatal("Legacy staging found for %s as it has a do_stage function. This will need conversion to a do_install or often simply removal to work with OE-core" % d.getVar("FILE", True))
 }
 
 
meta/classes/toolchain-scripts.bbclass +1 -1
index 5cba403..6fc9c13 100644
@@ -34,7 +34,7 @@ toolchain_create_sdk_env_script () {
 }
 
 # This function creates an environment-setup-script in the TMPDIR which enables
-# a Poky IDE to integrate with the build tree
+# a OE-core IDE to integrate with the build tree
 toolchain_create_tree_env_script () {
 	script=${TMPDIR}/environment-setup-${MULTIMACH_TARGET_SYS}
 	rm -f $script
Signature · 1 line
1.7.6.5
author
#10 lore raw

[CONSOLIDATED PULL 10/19] tzdata_2011n: provide pkg_postinst and timezone defaults

In reply to Saul Wold

From: Andrea Adami <[email protected]>

* Introduce DEFAULT_TIMEZONE variable ('Universal', present in base package)
* and add /etc/timezone during do_install.
* While there, fix hardcoded references to $exec_prefix (/usr).
* Add the pkg_postinst script (adapted from Gentoo).
* Create /etc/localtime during postinst.
* Bump PR

---
 meta/recipes-extended/tzdata/tzdata_2011n.bb |   62 ++++++++++++++++++++++++--
 1 files changed, 58 insertions(+), 4 deletions(-)
meta/recipes-extended/tzdata/tzdata_2011n.bb +58 -4
index de9281a..9a41131 100644
@@ -5,7 +5,7 @@ LICENSE = "PD"
 LIC_FILES_CHKSUM = "file://asia;beginline=2;endline=3;md5=06468c0e84ef4d4c97045a4a29b08234"
 DEPENDS = "tzcode-native"
 
-PR = "r0"
+PR = "r1"
 
 RCONFLICTS= "timezones timezone-africa timezone-america timezone-antarctica \
              timezone-arctic timezone-asia timezone-atlantic \
@@ -19,6 +19,8 @@ SRC_URI[tzdata.sha256sum] = "a343e542486b2b8ebdeca474eed79f1c04f69420ca943c2b9bd
 
 S = "${WORKDIR}"
 
+DEFAULT_TIMEZONE ?= "Universal"
+
 TZONES= "africa antarctica asia australasia europe northamerica southamerica  \
          factory solar87 solar88 solar89 etcetera backward systemv \
         "
@@ -36,12 +38,64 @@ do_compile () {
 }
 
 do_install () {
-        install -d ${D}/usr ${D}${datadir}/zoneinfo
-        cp -pPR ${S}/usr ${D}/
+        install -d ${D}/$exec_prefix ${D}${datadir}/zoneinfo
+        cp -pPR ${S}/$exec_prefix ${D}/
         # libc is removing zoneinfo files from package
         cp -pP "${S}/zone.tab" ${D}${datadir}/zoneinfo
         cp -pP "${S}/iso3166.tab" ${D}${datadir}/zoneinfo
-	chown -R root:root ${D}
+
+        # Install default timezone
+        install -d ${D}${sysconfdir}
+        echo ${DEFAULT_TIMEZONE} > ${D}${sysconfdir}/timezone
+
+        chown -R root:root ${D}
+}
+
+pkg_postinst_${PN} () {
+
+# code taken from Gentoo's tzdata ebuild
+
+	etc_lt="$D${sysconfdir}/localtime"
+	src="$D${sysconfdir}/timezone"
+
+	if [ -e ${src} ] ; then
+		tz=$(sed -e 's:#.*::' -e 's:[[:space:]]*::g' -e '/^$/d' "${src}")
+	else
+		tz="FUBAR"
+	fi
+	
+	if [ -z ${tz} ] ; then
+		return 0
+	fi
+	
+	if [ ${tz} = "FUBAR" ] ; then
+		echo "You do not have TIMEZONE set in ${src}."
+
+		if [ ! -e ${etc_lt} ] ; then
+			# if /etc/localtime is a symlink somewhere, assume they
+			# know what they're doing and they're managing it themselves
+			if [ ! -L ${etc_lt} ] ; then
+				cp -f "$D${datadir}/zoneinfo/Universal" "${etc_lt}"
+				echo "Setting ${etc_lt} to Universal."
+			else
+				echo "Assuming your ${etc_lt} symlink is what you want; skipping update."
+			fi
+		else
+			echo "Skipping auto-update of ${etc_lt}."
+		fi
+		return 0
+	fi
+
+	if [ ! -e "$D${datadir}/zoneinfo/${tz}" ] ; then
+		echo "You have an invalid TIMEZONE setting in ${src}"
+		echo "Your ${etc_lt} has been reset to Universal; enjoy!"
+		tz="Universal"
+	fi
+	echo "Updating ${etc_lt} with $D${datadir}/zoneinfo/${tz}"
+	if [ -L ${etc_lt} ] ; then
+		rm -f "${etc_lt}"
+	fi
+	cp -f "$D${datadir}/zoneinfo/${tz}" "${etc_lt}"
 }
 
 # Packages primarily organized by directory with a major city
Signature · 1 line
1.7.6.5
author
#11 lore raw

[CONSOLIDATED PULL 11/19] kern-tools: import config audit and branch manipulation updates

In reply to Saul Wold

From: Bruce Ashfield <[email protected]>

Updating the kern-tools SRCREV to import the following changes:

a7a9930 kgit-meta/scc: allow multi-line defines
e3442c6 kern-tools: add required and optional kernel configuration processing b56b67b configme: extract redefinition and mismatch information 6118eaf kern-tools: remove branchname assumptions

These are required to support the kernel configuration policy changes implemented in the yocto 3.2 kernel repository.

---
 .../kern-tools/kern-tools-native_git.bb            |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
meta/recipes-kernel/kern-tools/kern-tools-native_git.bb +1 -1
index 2711465..1eced23 100644
@@ -4,7 +4,7 @@ LIC_FILES_CHKSUM = "file://git/tools/kgit;beginline=5;endline=9;md5=e2bf4415f3d8
 
 DEPENDS = "git-native guilt-native"
 
-SRCREV = "52d929b5435d32097bce22b3f3662440f73a33b5"
+SRCREV = "a7a9930d2b1f1954fbd817810b706e2e3c42e8de"
 PR = r12
 PV = "0.1+git${SRCPV}"
 
Signature · 1 line
1.7.6.5
author
#12 lore raw

[CONSOLIDATED PULL 12/19] linux-yocto: add kernel 3.2.2 support

In reply to Saul Wold

From: Bruce Ashfield <[email protected]>

Adding initial support for the linux 3.2 kernel.

Although the branching and naming has changed slightly, the same BSPs and features exist in this tree as have existed in previous linux-yocto versions.

Notable features of this update are:

- streamlined branch naming
- configuration and functionality split in the standard kernel
- creation of the 'tiny' kernel type branch
- audited kernel configurations with optional features documented in the meta branch
- feature and BSP refreshes
- 3.2-rt support refresh
- qemu ppc graphics support

Build and boot testing has been performed on all emulated targets (sato and core).

---
 meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb |   37 ++++++++++++++++++++
 meta/recipes-kernel/linux/linux-yocto_3.2.bb    |   41 +++++++++++++++++++++++
 2 files changed, 78 insertions(+), 0 deletions(-)
 create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
 create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.2.bb
meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb new file +37 -0
new file mode 100644
index 0000000..9b0c1bf
@@ -0,0 +1,37 @@
+inherit kernel
+require recipes-kernel/linux/linux-yocto.inc
+
+KMACHINE = "common-pc"
+KMACHINE_qemux86  = "common-pc"
+KMACHINE_qemux86-64  = "common-pc-64"
+KMACHINE_qemuarm  = "arm-versatile-926ejs"
+KMACHINE_qemuppc  = "qemu-ppc32"
+KMACHINE_qemumips = "mti-malta32-be"
+
+KBRANCH = "standard/preempt-rt/base"
+KBRANCH_qemuppc = "standard/preempt-rt/qemu-ppc32"
+
+LINUX_VERSION ?= "3.2.2"
+LINUX_KERNEL_TYPE = "preempt-rt"
+
+SRCREV_machine ?= "415af017cf163c63d7b1e6e929e4a9c9baf5ba6d"
+SRCREV_machine_qemuppc ?= "38345c1e41b15c49308a9adbdde95167eeaa05fa"
+SRCREV_meta ?= "138bf5b502607fe40315c0d76822318d77d97e01"
+
+PR = "r0"
+PV = "${LINUX_VERSION}+git${SRCPV}"
+
+SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.2.git;protocol=git;nocheckout=1;branch=${KBRANCH},meta;name=machine,meta"
+
+# Omit broken machines from COMPATIBLE_MACHINE
+#   qemuppc hangs at boot
+#   qemumips panics at boot
+COMPATIBLE_MACHINE = "(qemux86|qemux86-64|qemuarm)"
+
+# Functionality flags
+KERNEL_FEATURES=features/netfilter
+KERNEL_FEATURES_append=" features/taskstats"
+KERNEL_FEATURES_append_qemux86=" cfg/sound"
+KERNEL_FEATURES_append_qemux86-64=" cfg/sound"
+
+require recipes-kernel/linux/linux-tools.inc
meta/recipes-kernel/linux/linux-yocto_3.2.bb new file +41 -0

41 lines not on this page · raw message

Signature · 1 line
1.7.6.5
author
#13 lore raw

[CONSOLIDATED PULL 13/19] linux-yocto: update to v3.0.18 + features

In reply to Saul Wold

From: Bruce Ashfield <[email protected]>

The -stable team released v3.0.18, so it becomes the new base for the linux-yocto_3.0 recipe.

Along with the 3.0.18 update this kernel refresh brings in the following changes:

59314a3 meta/beagleboard: Using CONFIG_PANEL_GENERIC_DPI=y b168325 crownbay: use emgd-1.10
281b80f kver: bumping to v3.0.18
0d5d0dd common-pc*: add SMP and virtio

---
 meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb |    8 ++++----
 meta/recipes-kernel/linux/linux-yocto_3.0.bb    |   19 +++++++++----------
 2 files changed, 13 insertions(+), 14 deletions(-)
meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb +4 -4
index 9a543ab..5402f17 100644
@@ -11,12 +11,12 @@ KMACHINE_qemumips = "mti-malta32-be"
 KBRANCH = "yocto/standard/preempt-rt/base"
 KBRANCH_qemuppc = "yocto/standard/preempt-rt/qemu-ppc32"
 
-LINUX_VERSION ?= "3.0.14"
+LINUX_VERSION ?= "3.0.18"
 LINUX_KERNEL_TYPE = "preempt-rt"
 
-SRCREV_machine ?= "f1cc220f4ddf434bf254707c83a45794a63f117f"
-SRCREV_machine_qemuppc ?= "8bd5b80cb3243dadc9d6c5c09482c49994dff1a8"
-SRCREV_meta ?= "665fea1c249b4f335cb1c9a46a9f2c138d611f1a"
+SRCREV_machine ?= "2f9d925f5681eaae7f341cc1270c739e8b329c03"
+SRCREV_machine_qemuppc ?= "c66f7ef2315010756c8c97af6b13d52f9f18c03b"
+SRCREV_meta ?= "59314a3523e360796419d76d78c6f7d8c5ef2593"
 
 PR = "r1"
 PV = "${LINUX_VERSION}+git${SRCPV}"
meta/recipes-kernel/linux/linux-yocto_3.0.bb +9 -10
index 9d51bd0..6ff6027 100644
@@ -10,16 +10,15 @@ KMACHINE_qemuarm  = "yocto/standard/arm-versatile-926ejs"
 
 KBRANCH = ${KMACHINE}
 
-LINUX_VERSION ?= "3.0.14"
-
-
-SRCREV_machine_qemuarm ?= "c0386e4195c685b0ff94b7e21581ec47008ab13b"
-SRCREV_machine_qemumips ?= "56e4361a1bfc10042d83a7d8a5f96932056e3f35"
-SRCREV_machine_qemuppc ?= "53e71af30e30162e17e32b2f57e4481f5bc0573e"
-SRCREV_machine_qemux86 ?= "9e73573b6b227ab2c62e66e63470866d136f8d76"
-SRCREV_machine_qemux86-64 ?= "3551fd0412965b1f6b0b2f6ba35f7fecdaddb58a"
-SRCREV_machine ?= "6f5b11830deba4a6262c8c4abf67e608924f649e"
-SRCREV_meta ?= "665fea1c249b4f335cb1c9a46a9f2c138d611f1a"
+LINUX_VERSION ?= "3.0.18"
+
+SRCREV_machine_qemuarm ?= "48e68bd72da497a14200801140b3b87dae6d60e9"
+SRCREV_machine_qemumips ?= "9d86aeb43e5bbb0851cc4f105b64caab13bc71f3"
+SRCREV_machine_qemuppc ?= "15fd748017f0849138ff4b47d73f6866fa26cfe8"
+SRCREV_machine_qemux86 ?= "8f74a4339b3dc029fafff0ba7d88d6dc950d4b31"
+SRCREV_machine_qemux86-64 ?= "610c5a62daeda033755b0b7bfcb3e2cad5c76f3f"
+SRCREV_machine ?= "5df0b4c2538399aed543133b3855f809adf08ab8"
+SRCREV_meta ?= "59314a3523e360796419d76d78c6f7d8c5ef2593"
 
 PR = "r3"
 PV = "${LINUX_VERSION}+git${SRCPV}"
Signature · 1 line
1.7.6.5
author
#14 lore raw

[CONSOLIDATED PULL 14/19] gdb-common: Drop elfutils from DEPENDS

In reply to Saul Wold

From: Khem Raj <[email protected]>

---
 meta/recipes-devtools/gdb/gdb-common.inc |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)
meta/recipes-devtools/gdb/gdb-common.inc +3 -3
index d728139..930a71b 100644
@@ -2,7 +2,7 @@ DESCRIPTION = "gdb - GNU debugger"
 HOMEPAGE = "http://www.gnu.org/software/gdb/"
 LICENSE="GPLv3+"
 SECTION = "devel"
-DEPENDS = "ncurses readline elfutils ${LTTNGUST}"
+DEPENDS = "ncurses readline ${LTTNGUST}"
 
 LTTNGUST = "lttng-ust"
 LTTNGUST_libc-uclibc = ""
@@ -11,7 +11,7 @@ LTTNGUST_mipsel = ""
 LTTNGUST_mips64 = ""
 LTTNGUST_mips64el = ""
 
-INC_PR = "r4"
+INC_PR = "r5"
 
 LIC_FILES_CHKSUM = "file://COPYING;md5=59530bdf33659b29e73d4adb9f9f6552 \
 		file://COPYING.LIB;md5=9f604d8a4f8e74f4f5140845a21b6674 \
@@ -40,7 +40,7 @@ EXPAT = "--without-expat"
 
 EXTRA_OECONF = "--disable-gdbtk --disable-tui --disable-x \
                 --with-curses --disable-multilib --with-system-readline --disable-sim \
-                ${GDBPROPREFIX} --with-libelf=${STAGING_DIR_TARGET} ${EXPAT} \
+                ${GDBPROPREFIX} ${EXPAT} \
                 ${@base_contains('DISTRO_FEATURES', 'multiarch', '--enable-64-bit-bfd', '', d)} \
                "
 
Signature · 1 line
1.7.6.5
author
#15 lore raw

[CONSOLIDATED PULL 15/19] arm/tune: Correct the logic which added thumb-interwork to OVERRIDES

In reply to Saul Wold

From: Khem Raj <[email protected]>

Add no-thumb-interwork to TUNE_FEATURES for angstrom

---
 .../conf/machine/include/arm/feature-arm-thumb.inc |    2 +-
 meta/conf/machine/include/tune-strongarm1100.inc   |    4 +---
 2 files changed, 2 insertions(+), 4 deletions(-)
meta/conf/machine/include/arm/feature-arm-thumb.inc +1 -1
index b7d6061..da29102 100644
@@ -21,6 +21,6 @@ ARMPKGSFX_THUMB .= "${@bb.utils.contains("TUNE_FEATURES", [ "armv7", "thumb" ],
 # turn this off - the actual cost is very small.
 TUNEVALID[no-thumb-interwork] = "Disable mixing of thumb and ARM functions"
 TUNE_CCARGS += "${@bb.utils.contains("TUNE_FEATURES", "no-thumb-interwork", "-mno-thumb-interwork", "-mthumb-interwork", d)}"
-OVERRIDES .= "${@bb.utils.contains("TUNE_FEATURES", "no-thumb-interwork", ":thumb-interwork", "", d)}"
+OVERRIDES .= "${@bb.utils.contains("TUNE_FEATURES", "no-thumb-interwork", "", ":thumb-interwork", d)}"
 
 TARGET_CC_KERNEL_ARCH += "-mno-thumb-interwork -marm"
meta/conf/machine/include/tune-strongarm1100.inc +1 -3
index 66bab8e..8bd5be7 100644
@@ -6,7 +6,5 @@ TUNEVALID[strongarm] = "Enable Strongarm 1100 series processor optimizations"
 TUNE_CCARGS += "${@bb.utils.contains("TUNE_FEATURES", "strongarm", "-mtune=strongarm1100", "", d)}"
 
 AVAILTUNES += "strongarm"
-TUNE_FEATURES_tune-strongarm = "${TUNE_FEATURES_tune-armv4} strongarm"
+TUNE_FEATURES_tune-strongarm = "${TUNE_FEATURES_tune-armv4} strongarm no-thumb-interwork"
 PACKAGE_EXTRA_ARCHS_tune-strongarm = "${PACKAGE_EXTRA_ARCHS_tune-armv4}"
-
-
Signature · 1 line
1.7.6.5
author
#16 lore raw

[CONSOLIDATED PULL 16/19] tunearch/arm: Differentiate between thumb code generation and thumb capability

In reply to Saul Wold

From: Khem Raj <[email protected]>

We have diverged a bit from oe.dev where thumb in OVERRIDES meant the code was being compiled in thumb mode. With tunearch this got a different meaning where it meant that if a core is capable of generating thumb code them we will have this in overrides. With this patch I am trying to address the problem where 'thumbmode' in TUNE_FEATURES means that code will be compiled in thumb mode by default and 'thumb' is to denote that core is capable of thumb instruction set.

---
 .../conf/machine/include/arm/feature-arm-thumb.inc |   18 ++++++++++++++----
 1 files changed, 14 insertions(+), 4 deletions(-)
meta/conf/machine/include/arm/feature-arm-thumb.inc +14 -4
index da29102..cb6f4e7 100644
@@ -4,10 +4,20 @@
 # encoded RISC sub-set. Thumb code is smaller (maybe 70% of the ARM size)
 # but requires more instructions (140% for 70% smaller code) so may be
 # slower.
-TUNEVALID[thumb] = "Use thumb instructions instead of ARM"
-ARM_THUMB_M_OPT = "${@['-marm', '-mthumb'][d.getVar('ARM_INSTRUCTION_SET', 1) == 'thumb']}"
-TUNE_CCARGS += "${@bb.utils.contains("TUNE_FEATURES", "thumb", "${ARM_THUMB_M_OPT}", "", d)}"
-OVERRIDES .= "${@bb.utils.contains("TUNE_FEATURES", "thumb", ":thumb", "", d)}"
+
+# 'thumbmode' in TUNE_FEATURES means default ISA for code generation is thumb
+# 'thumb' in TUNE_FEATURES means the core supports thumb ISA but code
+# generation can happen in arm or thumb
+# having 'thumbmode' would imply 'thumb' naturally
+
+TUNEVALID[thumbmode] = "Use THUMB instruction set instead of ARM"
+ARM_INSTRUCTION_SET ?= "arm"
+AVAILTUNES += "${@bb.utils.contains("ARM_INSTRUCTION_SET", "thumb", "thumbmode", "", d)}"
+TUNE_FEATURES_tune-thumbmode += "${@bb.utils.contains("ARM_INSTRUCTION_SET", "thumb", "thumbmode", "", d)}"
+TUNE_CCARGS += "${@bb.utils.contains("ARM_INSTRUCTION_SET", "thumb", "-mthumb", "-marm", d)}"
+OVERRIDES .= "${@bb.utils.contains("ARM_INSTRUCTION_SET", "thumb", ":thumb", "", d)}"
+
+TUNEVALID[thumb] = "THUMB instruction set capable ARM core"
 
 # Note armv7 will hit on armv7a as well
 ARMPKGSFX_THUMB .= "${@bb.utils.contains("TUNE_FEATURES", [ "armv4", "thumb" ], "t", "", d)}"
Signature · 1 line
1.7.6.5
#17 lore raw

Re: [CONSOLIDATED PULL 16/19] tunearch/arm: Differentiate between thumb code generation and thumb capability

Quoted 7 lines · Saul Wold

We have diverged a bit from oe.dev where thumb in OVERRIDES meant the code was being compiled in thumb mode. With tunearch this got a different meaning where it meant that if a core is capable of generating thumb code them we will have this in overrides. With this patch I am trying to address the problem where 'thumbmode' in TUNE_FEATURES means that code will be compiled in thumb mode by default and 'thumb' is to denote that core is capable of thumb instruction set.

So this patch is changing the meaning of the "thumb" override in oe-core, right? Is that really a good idea?

Also, I'm not quite sure I understand what the "thumb" tuning would be useful for when this patch is applied. You seem to have removed most of the code which checks for "thumb" in TUNE_FEATURES which seems to leave it not doing anything very much.

Can you clarify what exactly is the problem that this patch is solving, what the old and new semantics of the overrides and tune flags are, and why it's an improvement?

p.

#18 lore raw

Re: [CONSOLIDATED PULL 16/19] tunearch/arm: Differentiate between thumb code generation and thumb capability

Quoted 9 lines · Phil Blundell
Quoted 7 lines · Saul Wold

We have diverged a bit from oe.dev where thumb in OVERRIDES meant the code was being compiled in thumb mode. With tunearch this got a different meaning where it meant that if a core is capable of generating thumb code them we will have this in overrides. With this patch I am trying to address the problem where 'thumbmode' in TUNE_FEATURES means that code will be compiled in thumb mode by default and 'thumb' is to denote that core is capable of thumb instruction set.

Quoted 3 lines

So this patch is changing the meaning of the "thumb" override in oe-core, right?  Is that really a good idea?

yes see below it bridges the gap that was created with tune overhaul

Quoted 4 lines

Also, I'm not quite sure I understand what the "thumb" tuning would be useful for when this patch is applied.  You seem to have removed most of the code which checks for "thumb" in TUNE_FEATURES which seems to leave it not doing anything very much.

it adds 't' or 't2' to package arch but it wont mean the package is compiled in thumb
mode.

Quoted 4 lines

Can you clarify what exactly is the problem that this patch is solving, what the old and new semantics of the overrides and tune flags are, and why it's an improvement?

recipes has used thumb override when they were being compiled in thumbmode and not thumb enabled. Currently override gets added regardless of mode which is not right. This is what it fixes there are few recipes in oe-core which use this
override and plus helps in porting recipes from oe.dev which uses the override as explained.

Quoted 9 lines

p.

_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

author
#19 lore raw

[CONSOLIDATED PULL 17/19] tune-thumb.inc: Delete

In reply to Saul Wold

From: Khem Raj <[email protected]>

The same functionality is provided by
machine/include/arm/feature-arm-thumb.inc
Setting ARM_INSTRUCTION_SET = "thumb"
in distro configs should be enough

---
 meta/conf/machine/include/tune-thumb.inc |   32 ------------------------------
 1 files changed, 0 insertions(+), 32 deletions(-)
 delete mode 100644 meta/conf/machine/include/tune-thumb.inc
meta/conf/machine/include/tune-thumb.inc deleted +0 -32
deleted file mode 100644
index 214e3b6..0000000
@@ -1,32 +0,0 @@
-#tune file for thumb instructions
-
-ARM_INSTRUCTION_SET ?= "arm"
-# "arm" "thumb"
-#    The instruction set the compiler should use when generating application
-#    code.  The kernel is always compiled with arm code at present.  arm code
-#    is the original 32 bit ARM instruction set, thumb code is the 16 bit
-#    encoded RISC sub-set.  Thumb code is smaller (maybe 70% of the ARM size)
-#    but requires more instructions (140% for 70% smaller code) so may be
-#    slower.
-
-THUMB_INTERWORK ?= "yes"
-# "yes" "no"
-#    Whether to compile with code to allow interworking between the two
-#    instruction sets.  This allows thumb code to be executed on a primarily
-#    arm system and vice versa.  It is strongly recommended that DISTROs not
-#    turn this off - the actual cost is very small.
-
-OVERRIDE_THUMB = "${@['', ':thumb'][d.getVar('ARM_INSTRUCTION_SET', 1) == 'thumb']}"
-OVERRIDE_INTERWORK = "${@['', ':thumb-interwork'][d.getVar('THUMB_INTERWORK', 1) == 'yes']}"
-OVERRIDES .= "${OVERRIDE_THUMB}${OVERRIDE_INTERWORK}"
-
-#    Compiler and linker options for application code and kernel code.  These
-#    options ensure that the compiler has the correct settings for the selected
-#    instruction set and interworking.
-ARM_INTERWORK_M_OPT = "${@['-mno-thumb-interwork', '-mthumb-interwork'][d.getVar('THUMB_INTERWORK', 1) == 'yes']}"
-ARM_THUMB_M_OPT = "${@['-marm', '-mthumb'][d.getVar('ARM_INSTRUCTION_SET', 1) == 'thumb']}"
-
-#
-TUNE_CCARGS +=  "${ARM_INTERWORK_M_OPT} ${ARM_THUMB_M_OPT}"
-TARGET_CC_KERNEL_ARCH  += "-mno-thumb-interwork -marm"
-
Signature · 1 line
1.7.6.5
author
#20 lore raw

[CONSOLIDATED PULL 18/19] libksba: add recipe for 1.2.0

In reply to Saul Wold

From: Steve Sakoman <[email protected]>

Libksba provides an easy API to create and parse X.509 and CMS related objects and is required for gnupg

---
 meta/recipes-support/libksba/libksba_1.2.0.bb |   12 ++++++++++++
 1 files changed, 12 insertions(+), 0 deletions(-)
 create mode 100644 meta/recipes-support/libksba/libksba_1.2.0.bb
meta/recipes-support/libksba/libksba_1.2.0.bb new file +12 -0
new file mode 100644
index 0000000..1fadd48
@@ -0,0 +1,12 @@
+DESCRIPTION = "Libksba provides an easy API to create and parse X.509 and CMS related objects"
+LICENSE = "GPLv3"
+LIC_FILES_CHKSUM = "file://COPYING;md5=f27defe1e96c2e1ecd4e0c9be8967949"
+
+DEPENDS = "libgpg-error"
+
+inherit autotools binconfig
+
+SRC_URI = "ftp://ftp.gnupg.org/gcrypt/${PN}/${PN}-${PV}.tar.bz2"
+
+SRC_URI[md5sum] = "e797f370b69b4dc776499d6a071ae137"
+SRC_URI[sha256sum] = "09afce65b03d027cbec10d21464f4f651cdfd269e38b404f83e48d3e2a3c934b"
Signature · 1 line
1.7.6.5
author
#21 lore raw

[CONSOLIDATED PULL 19/19] gnupg: add recipe for 2.0.18

In reply to Saul Wold

From: Steve Sakoman <[email protected]>

GnuPG 2.0 is the new modularized version of GnuPG supporting OpenPGP and S/MIME

---
 meta/recipes-support/gnupg/gnupg_2.0.18.bb |   25 +++++++++++++++++++++++++
 1 files changed, 25 insertions(+), 0 deletions(-)
 create mode 100644 meta/recipes-support/gnupg/gnupg_2.0.18.bb
meta/recipes-support/gnupg/gnupg_2.0.18.bb new file +25 -0
new file mode 100644
index 0000000..bdf6e3e
@@ -0,0 +1,25 @@
+DESCRIPTION = "gnupg - GNU privacy guard"
+LICENSE = "GPLv3 & LGPLv3"
+LIC_FILES_CHKSUM = "file://COPYING;md5=f27defe1e96c2e1ecd4e0c9be8967949 \
+                    file://COPYING.LIB;md5=6a6a8e020838b23406c81b19c1d46df6"
+
+DEPENDS = "pth libassuan libksba zlib bzip2 readline"
+
+inherit autotools gettext
+
+SRC_URI = "ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-${PV}.tar.bz2"
+
+SRC_URI[md5sum] = "2f37e0722666a0fedbe4d9f9227ac4d7"
+SRC_URI[sha256sum] = "48aedd762ca443fb952a9e859efe3c66706d7c2c9c77c32dbdbac4fe962dae5b"
+
+S = "${WORKDIR}/gnupg-${PV}"
+
+EXTRA_OECONF = "--disable-ldap \
+		--with-zlib=${STAGING_LIBDIR}/.. \
+		--with-bzip2=${STAGING_LIBDIR}/.. \
+                --with-readline=${STAGING_LIBDIR}/.. \
+               "
+
+do_install_append() {
+	ln -sf gpg2 ${D}${bindir}/gpg
+}
Signature · 1 line
1.7.6.5
#22 lore raw
In reply to Saul Wold
Quoted 5 lines · Saul Wold

Kernel Update from Bruce, they need a meta-yocto change set also. I pulled the first part of Steve's GNUGP changes, but not the enabling part since that is getting tweaked still.

GNUPG I guess ;-)

Signature · 3 lines
Otavio Salvador                             O.S. Systems
E-mail: [email protected]  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br