[oe] Error while bitbake meta-toolchain-qt5
Hi, I am getting error while Building Qt5 using yocto on Wandboard refering to the link http://wiki.wandboard.org/index.php/Building_Qt5_using_yocto_on_Wandboard At the time of $ bitbake meta-toolchain-qt5 I am getting error, i have posted that error in wandboard forum - http://forums.wandboard.org/viewtopic.php?f=10t=573p=2520sid=45ce5e714aa2ae65ffc52cb7bedf31b3#p2520 Can you please look at this post? I think it is problem with 'git:// qt.gitorious.org/qt/qtwayland.git Thanking you in advance. - Switesh. -- “The contents of this e-mail message and any attachments are confidential and are intended solely for addressee. The information may also be legally privileged. This transmission is sent in trust, for the sole purpose of delivery to the intended recipient. If you have received this transmission in error, any use, reproduction or dissemination of this transmission is strictly prohibited. If you are not the intended recipient, please immediately notify the sender by reply e-mail or phone and delete this message and its attachments, if any.” -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-networking][PATCH 1/6] ipsec-tools: Fix build with glibc 2.20
Signed-off-by: Khem Raj raj.k...@gmail.com
---
.../ipsec-tools/ipsec-tools/glibc-2.20.patch | 23 ++
.../ipsec-tools/ipsec-tools_0.8.2.bb | 1 +
2 files changed, 24 insertions(+)
create mode 100644
meta-networking/recipes-support/ipsec-tools/ipsec-tools/glibc-2.20.patch
diff --git
a/meta-networking/recipes-support/ipsec-tools/ipsec-tools/glibc-2.20.patch
b/meta-networking/recipes-support/ipsec-tools/ipsec-tools/glibc-2.20.patch
new file mode 100644
index 000..36efc49
--- /dev/null
+++ b/meta-networking/recipes-support/ipsec-tools/ipsec-tools/glibc-2.20.patch
@@ -0,0 +1,23 @@
+squahes below warning
+ warning: #warning _BSD_SOURCE and _SVID_SOURCE are deprecated, use
_DEFAULT_SOURCE
+
+Seen with glibc 2.20
+
+Signed-off-by: Khem Raj raj.k...@gmail.com
+Upstream-Status: Pending
+Index: ipsec-tools-0.8.2/src/include-glibc/glibc-bugs.h
+===
+--- ipsec-tools-0.8.2.orig/src/include-glibc/glibc-bugs.h 2006-09-09
09:22:08.0 -0700
ipsec-tools-0.8.2/src/include-glibc/glibc-bugs.h 2014-09-03
22:27:22.551563888 -0700
+@@ -4,7 +4,11 @@
+ #define __GLIBC_BUGS_H__ 1
+
+ #define _XOPEN_SOURCE 500
++/* Legacy feature macro.*/
+ #define _BSD_SOURCE
++/* New feature macro that provides everything _BSD_SOURCE and
++ * _SVID_SOURCE provided and possibly more. */
++#define _DEFAULT_SOURCE
+
+ #include features.h
+ #include sys/types.h
diff --git a/meta-networking/recipes-support/ipsec-tools/ipsec-tools_0.8.2.bb
b/meta-networking/recipes-support/ipsec-tools/ipsec-tools_0.8.2.bb
index 208268f..babce40 100644
--- a/meta-networking/recipes-support/ipsec-tools/ipsec-tools_0.8.2.bb
+++ b/meta-networking/recipes-support/ipsec-tools/ipsec-tools_0.8.2.bb
@@ -13,6 +13,7 @@ SRC_URI =
ftp://ftp.netbsd.org/pub/NetBSD/misc/ipsec-tools/0.8/ipsec-tools-${PV
file://0001-racoon-pfkey-avoid-potential-null-pointer-dereferenc.patch \
file://racoon-check-invalid-pointers.patch \
file://racoon-check-invalid-ivm.patch \
+ file://glibc-2.20.patch \
SRC_URI[md5sum] = d53ec14a0a3ece64e09e5e34b3350b41
SRC_URI[sha256sum] =
8eb6b38716e2f3a8a72f1f549c9444c2bc28d52c9536792690564c74fe722f2d
--
2.1.0
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-oe][PATCH 3/6] luajit, acpitests: Fix build on hardfloat arm
luajit as well as acpitests build system has mind of its own and does not
respect CC and friends in makefiles so we have to inject
the CFLAGS via EXTRA_OEMAKE, some of ABI defining params
e.g. float-abi selection is mentioned in TUNE_CCARGS and
not in TOOLCHAIN_OPTIONS. This causes build to go for softfloat
build and that is not what we want.
Signed-off-by: Khem Raj raj.k...@gmail.com
---
meta-oe/recipes-devtools/luajit/luajit_2.0.3.bb | 5 -
meta-oe/recipes-extended/acpica/acpitests_20140424.bb | 2 +-
2 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/meta-oe/recipes-devtools/luajit/luajit_2.0.3.bb
b/meta-oe/recipes-devtools/luajit/luajit_2.0.3.bb
index 684ec14..48137e3 100644
--- a/meta-oe/recipes-devtools/luajit/luajit_2.0.3.bb
+++ b/meta-oe/recipes-devtools/luajit/luajit_2.0.3.bb
@@ -20,7 +20,10 @@ do_configure_prepend() {
sed -i -e s:/lib$:${base_libdir}:g ${S}/Makefile
}
-EXTRA_OEMAKE = 'CROSS=${HOST_PREFIX} TARGET_CFLAGS=${TOOLCHAIN_OPTIONS}
TARGET_LDFLAGS=${TOOLCHAIN_OPTIONS} TARGET_SHLDFLAGS=${TOOLCHAIN_OPTIONS}'
+EXTRA_OEMAKE = 'CROSS=${HOST_PREFIX} \
+TARGET_CFLAGS=${TOOLCHAIN_OPTIONS} ${HOST_CC_ARCH} \
+TARGET_LDFLAGS=${TOOLCHAIN_OPTIONS} \
+TARGET_SHLDFLAGS=${TOOLCHAIN_OPTIONS}'
EXTRA_OEMAKE_append_powerpc = ' HOST_CC=${BUILD_CC} -m32'
EXTRA_OEMAKE_append_x86-64 = ' HOST_CC=${BUILD_CC}'
EXTRA_OEMAKE_append_i586 = ' HOST_CC=${BUILD_CC} -m32'
diff --git a/meta-oe/recipes-extended/acpica/acpitests_20140424.bb
b/meta-oe/recipes-extended/acpica/acpitests_20140424.bb
index 7e145bb..e3c706c 100644
--- a/meta-oe/recipes-extended/acpica/acpitests_20140424.bb
+++ b/meta-oe/recipes-extended/acpica/acpitests_20140424.bb
@@ -18,7 +18,7 @@ SRC_URI[acpica.sha256sum] =
72ece982bbbdfb1b17418f1feb3a9daaa01803d0d41dcf00e19
S = ${WORKDIR}/acpitests-unix-${PV}
-EXTRA_OEMAKE = CC=${TARGET_PREFIX}gcc 'OPT_CFLAGS=-Wall'
+EXTRA_OEMAKE = 'CC=${TARGET_PREFIX}gcc ${HOST_CC_ARCH}' 'OPT_CFLAGS=-Wall'
# The Makefiles expect a specific layout
do_compile() {
--
2.1.0
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-oe][PATCH 2/6] ckermit: Update recipe ckermit_301.bb - ckermit_302.bb
Signed-off-by: Khem Raj raj.k...@gmail.com
---
meta-oe/recipes-support/ckermit/ckermit_301.bb | 57 -
meta-oe/recipes-support/ckermit/ckermit_302.bb | 58 ++
2 files changed, 58 insertions(+), 57 deletions(-)
delete mode 100644 meta-oe/recipes-support/ckermit/ckermit_301.bb
create mode 100644 meta-oe/recipes-support/ckermit/ckermit_302.bb
diff --git a/meta-oe/recipes-support/ckermit/ckermit_301.bb
b/meta-oe/recipes-support/ckermit/ckermit_301.bb
deleted file mode 100644
index b255f5e..000
--- a/meta-oe/recipes-support/ckermit/ckermit_301.bb
+++ /dev/null
@@ -1,57 +0,0 @@
-DESCRIPTION = C-Kermit is a combined serial and network communication \
-software package offering a consistent, medium-independent, \
-cross-platform approach to connection establishment, terminal \
-sessions, file transfer, character-set translation, and automation \
-of communication tasks.
-HOMEPAGE = http://www.columbia.edu/kermit/;
-SECTION = console/network
-LICENSE = BSD-3-Clause
-LIC_FILES_CHKSUM = file://COPYING.TXT;md5=932ca542d6c6cb8a59a0bcd76ab67cc3
-SRC_URI =
ftp://kermit.columbia.edu/kermit/archives/cku${PV}.tar.gz;subdir=${BPN}-${PV};
-
-export CC2 = ${CC}
-export BINDIR = ${bindir}
-export MANDIR = ${mandir}/man1
-export INFODIR = ${infodir}
-
-# Additional flags. For uclibc we add -DNOARROWKEYS which stops ckermit
-# trying to look inside the stdio headers.
-CKERMIT_ADDITIONAL =
-CKERMIT_ADDITIONAL_libc-uclibc = -DNOARROWKEYS
-
-TARGET_CC_ARCH += ${LDFLAGS}
-
-do_compile () {
-# The original makefile doesn't differentiate between CC and CC_FOR_BUILD,
-# so we build wart manually. Note that you need a ckwart.o with the proper
-# timestamp to make this hack work:
-${BUILD_CC} -c ckwart.c
-${BUILD_CC} -o wart ckwart.o
-./wart ckcpro.w ckcpro.c
-
-# read ${S}/ckccfg.txt to understand this :-)
-oe_runmake wermit CFLAGS=${CFLAGS} -DLINUX -DCK_POSIX_SIG \
--DNOTCPOPTS -DLINUXFSSTND -DNOCOTFMC -DPOSIX -DUSE_STRERROR \
--DNOSYSLOG -DHAVE_PTMX -DNO_DNS_SRV -DNOGFTIMER \
--DNOB_50 -DNOB_75 -DNOB_134 -DNOB_150 -DNOB_200 \
--DNOB_1800 -DNOB_3600 -DNOB_7200 -DNOB_76K -DNOB_230K \
--DNOB_460K -DNOB_921K \
--DNOCSETS -DNONET -DNOUNICODE -DNOHELP -DNODEBUG \
--DNOFRILLS -DNOFTP -DNODIAL -DNOPUSH -DNOIKSD -DNOHTTP -DNOFLOAT \
--DNOSERVER -DNOSEXP -DNORLOGIN -DNOOLDMODEMS -DNOSSH -DNOLISTEN \
--DNORESEND -DNOAUTODL -DNOSTREAMING -DNOHINTS -DNOCKXYZ -DNOLEARN \
--DNOMKDIR -DNOPERMS -DNOCKTIMERS -DNOCKREGEX -DNOREALPATH \
--DCK_SMALL -DNOLOGDIAL -DNORENAME -DNOWHATAMI \
-${CKERMIT_ADDITIONAL}
-}
-
-do_install () {
-install -d ${D}${BINDIR} ${D}${MANDIR} ${D}${INFODIR}
-oe_runmake 'DESTDIR=${D}' install
-# Fix up dangling symlink
-rm ${D}${BINDIR}/kermit-sshsub
-(cd ${D}${BINDIR} ln -s ${BINDIR}/kermit kermit-sshusb)
-}
-
-SRC_URI[md5sum] = 59e80f909edf305933af8e0348dcc5d7
-SRC_URI[sha256sum] =
9793eb125f8936b079c6d7e5c3d2ff885cfedc07f9d2dd1e7db928e3029a211a
diff --git a/meta-oe/recipes-support/ckermit/ckermit_302.bb
b/meta-oe/recipes-support/ckermit/ckermit_302.bb
new file mode 100644
index 000..32a6c03
--- /dev/null
+++ b/meta-oe/recipes-support/ckermit/ckermit_302.bb
@@ -0,0 +1,58 @@
+DESCRIPTION = C-Kermit is a combined serial and network communication \
+software package offering a consistent, medium-independent, \
+cross-platform approach to connection establishment, terminal \
+sessions, file transfer, character-set translation, and automation \
+of communication tasks.
+HOMEPAGE = http://www.columbia.edu/kermit/;
+SECTION = console/network
+LICENSE = BSD-3-Clause
+LIC_FILES_CHKSUM = file://COPYING.TXT;md5=932ca542d6c6cb8a59a0bcd76ab67cc3
+
+SRC_URI =
ftp://ftp.kermitproject.org/kermit/archives/cku${PV}.tar.gz;subdir=${BPN}-${PV};
+SRC_URI[md5sum] = eac4dbf18b45775e4cdee5a7c74762b0
+SRC_URI[sha256sum] =
0d5f2cd12bdab9401b4c836854ebbf241675051875557783c332a6a40dac0711
+
+
+export CC2 = ${CC}
+export BINDIR = ${bindir}
+export MANDIR = ${mandir}/man1
+export INFODIR = ${infodir}
+
+# Additional flags. For uclibc we add -DNOARROWKEYS which stops ckermit
+# trying to look inside the stdio headers.
+CKERMIT_ADDITIONAL =
+CKERMIT_ADDITIONAL_libc-uclibc = -DNOARROWKEYS
+
+TARGET_CC_ARCH += ${LDFLAGS}
+
+do_compile () {
+# The original makefile doesn't differentiate between CC and CC_FOR_BUILD,
+# so we build wart manually. Note that you need a ckwart.o with the proper
+# timestamp to make this hack work:
+${BUILD_CC} -c ckwart.c
+${BUILD_CC} -o wart ckwart.o
+./wart ckcpro.w ckcpro.c
+
+# read ${S}/ckccfg.txt to understand this :-)
+oe_runmake wermit CFLAGS=${CFLAGS} -DLINUX -DCK_POSIX_SIG \
+-DNOTCPOPTS -DLINUXFSSTND -DNOCOTFMC -DPOSIX -DUSE_STRERROR \
+-DNOSYSLOG -DHAVE_PTMX -DNO_DNS_SRV -DNOGFTIMER \
+-DNOB_50 -DNOB_75 -DNOB_134 -DNOB_150 -DNOB_200 \
+-DNOB_1800
[oe] [meta-oe][PATCH 6/6] numlockx: Update SRC_URI to somewhere fetchable
Signed-off-by: Khem Raj raj.k...@gmail.com
---
meta-oe/recipes-graphics/numlockx/numlockx_1.2.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-oe/recipes-graphics/numlockx/numlockx_1.2.bb
b/meta-oe/recipes-graphics/numlockx/numlockx_1.2.bb
index ec875f0..47ec504 100644
--- a/meta-oe/recipes-graphics/numlockx/numlockx_1.2.bb
+++ b/meta-oe/recipes-graphics/numlockx/numlockx_1.2.bb
@@ -5,7 +5,7 @@ LICENSE = MIT-X
LIC_FILES_CHKSUM = file://LICENSE;md5=dcb1cc75e21540a4a66b54e38d95b047
DEPENDS = virtual/libx11 libxtst
-SRC_URI = http://home.kde.org/~seli/numlockx/numlockx-${PV}.tar.gz;
+SRC_URI =
http://pkgs.fedoraproject.org/repo/pkgs/numlockx/numlockx-${PV}.tar.gz/be9109370447eae23f6f3f8527bb1a67/numlockx-${PV}.tar.gz;
SRC_URI[md5sum] = be9109370447eae23f6f3f8527bb1a67
SRC_URI[sha256sum] =
e468eb9121c94c9089dc6a287eeb347e900ce04a14be37da29d7696cbce772e4
--
2.1.0
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-networking][PATCH 5/6] lowpan-tools: Move to 0.3.1 release
Also fix the git SRC_URI location
Signed-off-by: Khem Raj raj.k...@gmail.com
---
meta-networking/recipes-support/lowpan-tools/lowpan-tools_git.bb | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta-networking/recipes-support/lowpan-tools/lowpan-tools_git.bb
b/meta-networking/recipes-support/lowpan-tools/lowpan-tools_git.bb
index d8e1ddb..ca10262 100644
--- a/meta-networking/recipes-support/lowpan-tools/lowpan-tools_git.bb
+++ b/meta-networking/recipes-support/lowpan-tools/lowpan-tools_git.bb
@@ -7,10 +7,10 @@ LIC_FILES_CHKSUM =
file://COPYING;md5=751419260aa954499f7abaabaa882bbe
DEPENDS = libnl python
-PV = 0.3+git${SRCPV}
-SRC_URI =
git://linux-zigbee.git.sourceforge.net/gitroot/linux-zigbee/linux-zigbee \
+PV = 0.3.1+git${SRCPV}
+SRC_URI = git://git.code.sf.net/p/linux-zigbee/linux-zigbee \
file://no-help2man.patch
-SRCREV = a1d9615adde6d1a568813c24a128273ed755af04
+SRCREV = 38f42dbfce9e13629263db3bd3b81f14c69bb733
S = ${WORKDIR}/git
--
2.1.0
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-oe][PATCH 4/6] Fix build with glibc 2.20
Signed-off-by: Khem Raj raj.k...@gmail.com
---
.../libmtp/libmtp-1.1.5/glibc-2.20.patch | 36 ++
.../recipes-connectivity/libmtp/libmtp_1.1.5.bb| 1 +
2 files changed, 37 insertions(+)
create mode 100644
meta-oe/recipes-connectivity/libmtp/libmtp-1.1.5/glibc-2.20.patch
diff --git a/meta-oe/recipes-connectivity/libmtp/libmtp-1.1.5/glibc-2.20.patch
b/meta-oe/recipes-connectivity/libmtp/libmtp-1.1.5/glibc-2.20.patch
new file mode 100644
index 000..38b45c2
--- /dev/null
+++ b/meta-oe/recipes-connectivity/libmtp/libmtp-1.1.5/glibc-2.20.patch
@@ -0,0 +1,36 @@
+
+Include config.h so we get the defines available for subsequent
+include files
+
+Fixes errors like
+
+| In file included from
/home/ubuntu/work/upstream/openembedded-core/build/tmp-glibc/sysroots/beaglebone/usr/include/string.h:634:0,
+| from
/home/ubuntu/work/upstream/openembedded-core/build/tmp-glibc/work/cortexa8t2hf-vfp-neon-oe-linux-gnueabi/libmtp/1.1.5-r0/libmtp-1.1.5/src/util.c:36:
+|
/home/ubuntu/work/upstream/openembedded-core/build/tmp-glibc/work/cortexa8t2hf-vfp-neon-oe-linux-gnueabi/libmtp/1.1.5-r0/libmtp-1.1.5/src/util.h:29:7:
error: expected identifier or '(' before '__extension
+__'
+| char *strndup (const char *s, size_t n);
+|^
+|
/home/ubuntu/work/upstream/openembedded-core/build/tmp-glibc/work/cortexa8t2hf-vfp-neon-oe-linux-gnueabi/libmtp/1.1.5-r0/libmtp-1.1.5/src/util.c:111:7:
error: expected identifier or '(' before '__extensio
+n__'
+| char *strndup (const char *s, size_t n)
+|^
+| make[2]: *** [libmtp_la-util.lo] Error 1
+
+
+Signed-off-by: Khem Raj raj.k...@gmail.com
+
+Upstream-Status: Pending
+
+Index: libmtp-1.1.5/src/util.c
+===
+--- libmtp-1.1.5.orig/src/util.c 2011-01-10 05:37:21.0 -0800
libmtp-1.1.5/src/util.c2014-09-03 23:50:44.703563888 -0700
+@@ -22,6 +22,8 @@
+ * Boston, MA 02111-1307, USA.
+ */
+
++#include config.h
++
+ /* MSVC does not have these */
+ #ifndef _MSC_VER
+ #include sys/time.h
diff --git a/meta-oe/recipes-connectivity/libmtp/libmtp_1.1.5.bb
b/meta-oe/recipes-connectivity/libmtp/libmtp_1.1.5.bb
index 004323a..de63c72 100644
--- a/meta-oe/recipes-connectivity/libmtp/libmtp_1.1.5.bb
+++ b/meta-oe/recipes-connectivity/libmtp/libmtp_1.1.5.bb
@@ -19,6 +19,7 @@ SCM_URI = git://git.code.sf.net/p/libmtp/code
SRC_URI = \
${SOURCEFORGE_MIRROR}/${BPN}/${BPN}-${PV}.tar.gz \
file://69-libmtp.rules \
+file://glibc-2.20.patch \
SRC_URI[md5sum] = f80e45c0e6e5798c434bb1c26a7b602d
SRC_URI[sha256sum] =
787679171baf8b3cf2fcc03196c705ab4d7cbc969bd71f9d3696be1ce7f1c63a
--
2.1.0
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [PATCH][meta-networking][master-next] tcpslice: fix the license
From: Roy Li rongqing...@windriver.com
After check the copyright in source file, the license is BSD-4-Clause
Signed-off-by: Roy Li rongqing...@windriver.com
---
meta-networking/recipes-support/tcpdump/tcpslice_1.2a3.bb |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-networking/recipes-support/tcpdump/tcpslice_1.2a3.bb
b/meta-networking/recipes-support/tcpdump/tcpslice_1.2a3.bb
index e5e38b4..203d143 100644
--- a/meta-networking/recipes-support/tcpdump/tcpslice_1.2a3.bb
+++ b/meta-networking/recipes-support/tcpdump/tcpslice_1.2a3.bb
@@ -3,7 +3,7 @@ DESCRIPTION = A tool for extracting parts of a tcpdump packet
trace.
HOMEPAGE = http://www.tcpdump.org/related.html;
SECTION = console/network
-LICENSE = BSD
+LICENSE = BSD-4-Clause
LIC_FILES_CHKSUM =
file://tcpslice.c;endline=20;md5=99519e2e5234d1662a4ce16baa62c64e
SRC_URI = ftp://ftp.ee.lbl.gov/${BP}.tar.gz \
--
1.7.10.4
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-oe][PATCH V2 2/6] ckermit: Update recipe ckermit_301.bb - ckermit_302.bb
Signed-off-by: Khem Raj raj.k...@gmail.com
---
.../recipes-support/ckermit/{ckermit_301.bb = ckermit_302.bb} | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
rename meta-oe/recipes-support/ckermit/{ckermit_301.bb = ckermit_302.bb} (90%)
diff --git a/meta-oe/recipes-support/ckermit/ckermit_301.bb
b/meta-oe/recipes-support/ckermit/ckermit_302.bb
similarity index 90%
rename from meta-oe/recipes-support/ckermit/ckermit_301.bb
rename to meta-oe/recipes-support/ckermit/ckermit_302.bb
index b255f5e..32a6c03 100644
--- a/meta-oe/recipes-support/ckermit/ckermit_301.bb
+++ b/meta-oe/recipes-support/ckermit/ckermit_302.bb
@@ -7,7 +7,11 @@ HOMEPAGE = http://www.columbia.edu/kermit/;
SECTION = console/network
LICENSE = BSD-3-Clause
LIC_FILES_CHKSUM = file://COPYING.TXT;md5=932ca542d6c6cb8a59a0bcd76ab67cc3
-SRC_URI =
ftp://kermit.columbia.edu/kermit/archives/cku${PV}.tar.gz;subdir=${BPN}-${PV};
+
+SRC_URI =
ftp://ftp.kermitproject.org/kermit/archives/cku${PV}.tar.gz;subdir=${BPN}-${PV};
+SRC_URI[md5sum] = eac4dbf18b45775e4cdee5a7c74762b0
+SRC_URI[sha256sum] =
0d5f2cd12bdab9401b4c836854ebbf241675051875557783c332a6a40dac0711
+
export CC2 = ${CC}
export BINDIR = ${bindir}
@@ -52,6 +56,3 @@ do_install () {
rm ${D}${BINDIR}/kermit-sshsub
(cd ${D}${BINDIR} ln -s ${BINDIR}/kermit kermit-sshusb)
}
-
-SRC_URI[md5sum] = 59e80f909edf305933af8e0348dcc5d7
-SRC_URI[sha256sum] =
9793eb125f8936b079c6d7e5c3d2ff885cfedc07f9d2dd1e7db928e3029a211a
--
2.1.0
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [PATCH] tftp-hpa: bug fix on empty file put error
With the feature that checking the disk filled up, the return value of
function write_behind was checked and used to detect the disk status.
While for empty file, without data being written, this function will
return -1 thus the disk filled up error was miss-raised. Fix it.
Signed-off-by: Zhang Xiao xiao.zh...@windriver.com
---
.../tftp-hpa-bug-fix-on-empty-file-put-error.patch | 33 ++
.../recipes-daemons/tftp-hpa/tftp-hpa_5.2.bb | 1 +
2 files changed, 34 insertions(+)
create mode 100644
meta-networking/recipes-daemons/tftp-hpa/files/tftp-hpa-bug-fix-on-empty-file-put-error.patch
diff --git
a/meta-networking/recipes-daemons/tftp-hpa/files/tftp-hpa-bug-fix-on-empty-file-put-error.patch
b/meta-networking/recipes-daemons/tftp-hpa/files/tftp-hpa-bug-fix-on-empty-file-put-error.patch
new file mode 100644
index 000..aa29d9c
--- /dev/null
+++
b/meta-networking/recipes-daemons/tftp-hpa/files/tftp-hpa-bug-fix-on-empty-file-put-error.patch
@@ -0,0 +1,33 @@
+tftp-hpa: bug fix on empty file put error
+
+With the feature that checking the disk filled up, the return value of
+function write_behind was checked and used to detect the disk status.
+While for empty file, without data being written, this function will
+return -1 thus the disk filled up error was miss-raised. Fix it.
+
+Upstream-Status: pending
+
+Signed-off-by: Zhang Xiao xiao.zh...@windriver.com
+---
+ tftpd/tftpd.c | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+--- a/tftpd/tftpd.c
b/tftpd/tftpd.c
+@@ -1692,7 +1692,7 @@ static void tftp_recvfile(const struct f
+ syslog(LOG_WARNING, tftpd: write(ack): %m);
+ goto abort;
+ }
+-if(write_behind(file, pf-f_convert) 0) {
++if(write_behind(file, pf-f_convert) -1) {
+ nak(ENOSPACE, NULL);
+ (void)fclose(file);
+ goto abort;
+@@ -1727,7 +1727,7 @@ static void tftp_recvfile(const struct f
+ goto abort;
+ }
+ } while (size == segsize);
+-if(write_behind(file, pf-f_convert) 0) {
++if(write_behind(file, pf-f_convert) -1) {
+ nak(ENOSPACE, NULL);
+ (void)fclose(file);
+ goto abort;
diff --git a/meta-networking/recipes-daemons/tftp-hpa/tftp-hpa_5.2.bb
b/meta-networking/recipes-daemons/tftp-hpa/tftp-hpa_5.2.bb
index 1951747..e58a4b1 100644
--- a/meta-networking/recipes-daemons/tftp-hpa/tftp-hpa_5.2.bb
+++ b/meta-networking/recipes-daemons/tftp-hpa/tftp-hpa_5.2.bb
@@ -25,6 +25,7 @@ SRC_URI =
http://kernel.org/pub/software/network/tftp/tftp-hpa/tftp-hpa-${PV}.t
file://init \
file://add-error-check-for-disk-filled-up.patch \
file://tftp-hpa-bug-fix-on-separated-CR-and-LF.patch \
+ file://tftp-hpa-bug-fix-on-empty-file-put-error.patch \
SRC_URI[md5sum] = 46c9bd20bbffa62f79c958c7b99aac21
--
1.8.5.2.233.g932f7e4
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-browser][PATCH] chromium: Upgrade to version 37.0.2062.94
This is the current stable release of the 37 series. Since it is no longer
a beta, the DEFAULT_PREFERENCE = -1 bit is removed. Furthermore, this
version adds the angle_use_commit_id flag, which makes the related patch
obsolete.
Signed-off-by: Carlos Rafael Giani d...@pseudoterminal.org
---
.../{chromium_37.0.2062.0.bb = chromium_37.0.2062.94.bb} | 15 +++
1 file changed, 7 insertions(+), 8 deletions(-)
rename recipes-browser/chromium/{chromium_37.0.2062.0.bb =
chromium_37.0.2062.94.bb} (93%)
diff --git a/recipes-browser/chromium/chromium_37.0.2062.0.bb
b/recipes-browser/chromium/chromium_37.0.2062.94.bb
similarity index 93%
rename from recipes-browser/chromium/chromium_37.0.2062.0.bb
rename to recipes-browser/chromium/chromium_37.0.2062.94.bb
index c0e3b36..510b644 100644
--- a/recipes-browser/chromium/chromium_37.0.2062.0.bb
+++ b/recipes-browser/chromium/chromium_37.0.2062.94.bb
@@ -11,16 +11,11 @@ SRC_URI = \
${@bb.utils.contains('PACKAGECONFIG', 'impl-side-painting',
'file://disable-rasterization-whitelist-unlocking-impl-side-painting.patch',
'', d)} \
${@bb.utils.contains('PACKAGECONFIG', 'disable-api-keys-info-bar',
'file://0002-Disable-API-keys-info-bar.patch', '', d)} \
file://unistd-2.patch \
-file://0001-Disable-ANGLE-commit-ID-generation.patch \
file://google-chrome \
file://google-chrome.desktop \
-SRC_URI[md5sum] = 327e528a919239f18db581a8a6d1adea
-SRC_URI[sha256sum] =
6b9ce84df2b6f9d20b209aab16034079cea981b00b8d20660571555f53c815cb
-
-# Chromium 37 is currently in beta status
-DEFAULT_PREFERENCE = -1
-
+SRC_URI[md5sum] = 49bcf221a2e2e5406ae2e69964d01093
+SRC_URI[sha256sum] =
d27c19580b74cbe143131f0bc097557b3b2fb3d2be966e688d8af51a779ce533
# conditionally add ozone-wayland and its patches to the Chromium sources
@@ -38,7 +33,10 @@ OZONE_WAYLAND_EXTRA_PATCHES = \
file://0001-Remove-X-libraries-from-GYP-files.patch \
-SRC_URI += ${@base_conditional('ENABLE_WAYLAND', '1',
'git://github.com/01org/ozone-wayland.git;destsuffix=ozone-wayland-git;branch=Milestone-Summer;rev=a68f96aa1668de6f2a922a37b48d713d5d809ee0',
'', d)}
+OZONE_WAYLAND_GIT_DESTSUFFIX = ozone-wayland-git
+OZONE_WAYLAND_GIT_BRANCH = Milestone-Summer
+OZONE_WAYLAND_GIT_SRCREV = 8346e3cecb5c1331a25ba235f29b72f3f049966a
+SRC_URI += ${@base_conditional('ENABLE_WAYLAND', '1',
'git://github.com/01org/ozone-wayland.git;destsuffix=${OZONE_WAYLAND_GIT_DESTSUFFIX};branch=${OZONE_WAYLAND_GIT_BRANCH};rev=${OZONE_WAYLAND_GIT_SRCREV}',
'', d)}
do_unpack[postfuncs] += ${@base_conditional('ENABLE_WAYLAND', '1',
'copy_ozone_wayland_files', '', d)}
do_patch[prefuncs] += ${@base_conditional('ENABLE_WAYLAND', '1',
'add_ozone_wayland_patches', '', d)}
@@ -81,6 +79,7 @@ PACKAGECONFIG ??= use-egl
PACKAGECONFIG[use-egl] = ,,virtual/egl virtual/libgles2
EXTRA_OEGYP = \
+ -Dangle_use_commit_id=0 \
-Ddisable_fatal_linker_warnings=1 \
${@base_contains('DISTRO_FEATURES', 'ld-is-gold', '',
'-Dlinux_use_gold_binary=0', d)} \
${@base_contains('DISTRO_FEATURES', 'ld-is-gold', '',
'-Dlinux_use_gold_flags=0', d)} \
--
1.8.3.2
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] Style issue for recipes
Hi, Quick question of style for the community to bikeshed on: in the general case should recipes be split into foo_1.2.bb and foo.inc, or should they only split to bb/inc if there are multiple versions and generally there should just be foo_1.2.bb. Specifically I'm looking at the libunwind patch for oe-core (moving from meta-oe) which adds libunwind_1.1.bb and libunwind.inc. Personally I feel that splitting them up complicates packaging and should only be done if there's actually multiple versions being used. Ross -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] Style issue for recipes
On 09/04/2014 10:12 PM, Burton, Ross wrote: Hi, Quick question of style for the community to bikeshed on: in the general case should recipes be split into foo_1.2.bb and foo.inc, or should they only split to bb/inc if there are multiple versions and generally there should just be foo_1.2.bb. I think that put the constants in .inc is helpful for upgrading, for example, the SUMMARY, DESCRIPTION, HOMEPAGE, SECTION, inherit and so on, they are unlikely to change when upgrade. // Robert Specifically I'm looking at the libunwind patch for oe-core (moving from meta-oe) which adds libunwind_1.1.bb and libunwind.inc. Personally I feel that splitting them up complicates packaging and should only be done if there's actually multiple versions being used. Ross -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] Style issue for recipes
On 09/04/2014 10:03 AM, Robert Yang wrote: On 09/04/2014 10:12 PM, Burton, Ross wrote: Hi, Quick question of style for the community to bikeshed on: in the general case should recipes be split into foo_1.2.bb and foo.inc, or should they only split to bb/inc if there are multiple versions and generally there should just be foo_1.2.bb. I think that put the constants in .inc is helpful for upgrading, for example, the SUMMARY, DESCRIPTION, HOMEPAGE, SECTION, inherit and so on, they are unlikely to change when upgrade. I believe most of those carry over when an upgrade is simply a matter of renaming the recipe from foo_1.2.bb to foo_3.4.bb and changing the checksums. I don't think foo.inc is warranted when only one file will ever include it. I agree libunwind is a perfect example of where they can be merged into one file to simplify things, as long as everybody remembers to use -M when generating the patch. Peter -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [OE-core] Style issue for recipes
On 09/04/2014 08:03 AM, Robert Yang wrote: On 09/04/2014 10:12 PM, Burton, Ross wrote: Hi, Quick question of style for the community to bikeshed on: in the general case should recipes be split into foo_1.2.bb and foo.inc, or should they only split to bb/inc if there are multiple versions and generally there should just be foo_1.2.bb. I think that put the constants in .inc is helpful for upgrading, for example, the SUMMARY, DESCRIPTION, HOMEPAGE, SECTION, inherit and so on, they are unlikely to change when upgrade. This is the same reason why I have split a bb into two parts when I submit upgrades. I feel it makes reviewing easier the next time a package gets upgraded. Trying to find the actual changes between a file being deleted and the new one being added might lead to missing something. If there are unintentional consequence by doing this, that is a problem. - Armin // Robert Specifically I'm looking at the libunwind patch for oe-core (moving from meta-oe) which adds libunwind_1.1.bb and libunwind.inc. Personally I feel that splitting them up complicates packaging and should only be done if there's actually multiple versions being used. Ross -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [OE-core] Style issue for recipes
On 4 September 2014 16:41, akuster808 akuster...@gmail.com wrote: This is the same reason why I have split a bb into two parts when I submit upgrades. I feel it makes reviewing easier the next time a package gets upgraded. Trying to find the actual changes between a file being deleted and the new one being added might lead to missing something. If there are unintentional consequence by doing this, that is a problem. This is what git format-patch -M is for: it detects the rename and shows a proper diff. Ross -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] Style issue for recipes
On 4 September 2014 15:12, Burton, Ross ross.bur...@intel.com wrote: Quick question of style for the community to bikeshed on: in the general case should recipes be split into foo_1.2.bb and foo.inc, or should they only split to bb/inc if there are multiple versions and generally there should just be foo_1.2.bb. Another argument against widespread inc files: they encourage the impression that maintaining multiple versions is just a matter of having a .inc file. The moment you start having to put version-specific statements into a .bb you've entered a world of pain in keeping the .bb files in sync, moving options into the .inc as they become used by all versions, and purging old version-specific statements. Ross -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] Style issue for recipes
On Thu, Sep 4, 2014 at 6:34 PM, Burton, Ross ross.bur...@intel.com wrote: On 4 September 2014 15:12, Burton, Ross ross.bur...@intel.com wrote: Quick question of style for the community to bikeshed on: in the general case should recipes be split into foo_1.2.bb and foo.inc, or should they only split to bb/inc if there are multiple versions and generally there should just be foo_1.2.bb. Another argument against widespread inc files: they encourage the impression that maintaining multiple versions is just a matter of having a .inc file. The moment you start having to put version-specific statements into a .bb you've entered a world of pain in keeping the .bb files in sync, moving options into the .inc as they become used by all versions, and purging old version-specific statements. Ross -- I agree with Ross: It often took me time to find out where functionality comes from. Inc-files do only make sense for multiple versions of recipes or if different recipes share same code (only example I can remember is meta-gnome gvfs/gvfs-gdu-volume-monitor circular-dependency hack). My feeling is that the inc-files are still from classic oe times where we had multiple versions for many recipes and most can be merged into recipes without loosing something. Andreas -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] Style issue for recipes
On 09/04/2014 01:29 PM, Andreas Müller wrote: On Thu, Sep 4, 2014 at 6:34 PM, Burton, Ross ross.bur...@intel.com wrote: On 4 September 2014 15:12, Burton, Ross ross.bur...@intel.com wrote: Quick question of style for the community to bikeshed on: in the general case should recipes be split into foo_1.2.bb and foo.inc, or should they only split to bb/inc if there are multiple versions and generally there should just be foo_1.2.bb. Another argument against widespread inc files: they encourage the impression that maintaining multiple versions is just a matter of having a .inc file. The moment you start having to put version-specific statements into a .bb you've entered a world of pain in keeping the .bb files in sync, moving options into the .inc as they become used by all versions, and purging old version-specific statements. Ross -- I agree with Ross: It often took me time to find out where functionality comes from. Inc-files do only make sense for multiple versions of recipes or if different recipes share same code (only example I can remember is meta-gnome gvfs/gvfs-gdu-volume-monitor circular-dependency hack). My feeling is that the inc-files are still from classic oe times where we had multiple versions for many recipes and most can be merged into recipes without loosing something. The qwt recipe uses an include file and two bb files for qt versus qt-embedded builds. I do not know if this is wise, but it is a case not mentioned here. Philip Andreas -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-qt5][PATCH] qtwayland: Change module branch for 5.4
This is to fix the fetcher failure as the stable branch has been
removed. We does not change the revision we are using so this is
a safe change.
Signed-off-by: Otavio Salvador ota...@ossystems.com.br
---
recipes-qt/qt5/qtwayland_git.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/recipes-qt/qt5/qtwayland_git.bb b/recipes-qt/qt5/qtwayland_git.bb
index 28a3760..0bbb5ab 100644
--- a/recipes-qt/qt5/qtwayland_git.bb
+++ b/recipes-qt/qt5/qtwayland_git.bb
@@ -5,6 +5,7 @@ require ${PN}.inc
# qt5-git PV is only to indicate that this recipe is compatible with qt5 5.2.1
SRCREV = 98dca3b54f52f08117c1e0d3a1b4826ed12ef23f
+QT_MODULE_BRANCH = 5.4
SRC_URI += \
file://0001-examples.pro-include-server-buffer-only-when-buildin.patch \
--
2.1.0
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] Error while bitbake meta-toolchain-qt5
On Thu, Sep 4, 2014 at 4:10 AM, Switesh Fulpagare switesh.fulpag...@mindastoneridge.com wrote: Can you please look at this post? I think it is problem with 'git:// qt.gitorious.org/qt/qtwayland.git I just sent a patch fixing it; please try it. -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750 -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] Style issue for recipes
On 4 September 2014 18:54, Philip Balister phi...@balister.org wrote: The qwt recipe uses an include file and two bb files for qt versus qt-embedded builds. I do not know if this is wise, but it is a case not mentioned here. That seems a perfectly legitimate use of an inc as it's factoring out common code. Ross -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-initramfs][PATCH] klibc: klcc: consider --sysroot option and override gcc-cross encoded sysroot
On Monday, September 1, 2014, Andrea Adami andrea.ad...@gmail.com wrote:
For the recipes built with klcc-cross it is necessary to
pass --sysroot otherwise we default to the one encoded in gcc-cross which
actually is the 'first one' built.
The issue was revealed when building for armv4 after having built for
armv5te:
the produced binaries did contain Illegal Instruction (bx lr).
Signed-off-by: Andrea Adami andrea.ad...@gmail.com javascript:;
---
meta-initramfs/classes/klibc.bbclass | 4 ++--
.../klibc/klibc-2.0.4/klcc-consider-sysroot.patch | 14
++
meta-initramfs/recipes-devtools/klibc/klibc.inc| 1 +
3 files changed, 17 insertions(+), 2 deletions(-)
create mode 100644
meta-initramfs/recipes-devtools/klibc/klibc-2.0.4/klcc-consider-sysroot.patch
diff --git a/meta-initramfs/classes/klibc.bbclass
b/meta-initramfs/classes/klibc.bbclass
index ca741cd..8690472 100644
--- a/meta-initramfs/classes/klibc.bbclass
+++ b/meta-initramfs/classes/klibc.bbclass
@@ -4,8 +4,8 @@ DEPENDS =+ klcc-cross
# Default for klcc is to build static binaries.
# Set CC = ${TARGET_PREFIX}klcc -shared to build the dynamic version.
-export CC = ${TARGET_PREFIX}klcc
-export CC_armv4_linux-gnueabi = ${TARGET_PREFIX}klcc -march=armv4
-mthumb-interwork
+export CC = ${TARGET_PREFIX}klcc --sysroot=${STAGING_DIR_TARGET}
+export CC_armv4_linux-gnueabi = ${TARGET_PREFIX}klcc
--sysroot=${STAGING_DIR_TARGET} -march=armv4 -mthumb-interwork
May be you can use TOOLCHAIN_OPTIONS
here
export CPP = ${CC} -E
diff --git
a/meta-initramfs/recipes-devtools/klibc/klibc-2.0.4/klcc-consider-sysroot.patch
b/meta-initramfs/recipes-devtools/klibc/klibc-2.0.4/klcc-consider-sysroot.patch
new file mode 100644
index 000..9bc4835
--- /dev/null
+++
b/meta-initramfs/recipes-devtools/klibc/klibc-2.0.4/klcc-consider-sysroot.patch
@@ -0,0 +1,14 @@
+diff --git a/klcc/klcc.in b/klcc/klcc.in
+index 43d0984..61e9385 100644
+--- a/klcc/klcc.in
b/klcc/klcc.in
+@@ -204,6 +204,9 @@ while ( defined($a = shift(@ARGV)) ) {
+ # Libraries
+ push(@libs, $a);
+ push(@libs, shift(@ARGV)) if ( $2 eq '' );
++} elsif ( $a =~ /^--([sysroot=])(.*)$/ ) {
++ # Override gcc encoded sysroot
++ push(@ccopt, $a);
+ } else {
+ die $0: unknown option: $a\n;
+ }
diff --git a/meta-initramfs/recipes-devtools/klibc/klibc.inc
b/meta-initramfs/recipes-devtools/klibc/klibc.inc
index 0209b20..f3e9972 100644
--- a/meta-initramfs/recipes-devtools/klibc/klibc.inc
+++ b/meta-initramfs/recipes-devtools/klibc/klibc.inc
@@ -16,6 +16,7 @@ SRC_URI_append_linux-uclibceabi =
file://klibc-config-eabi.patch \
SRC_URI += file://klibc-linux-libc-dev.patch \
file://staging.patch \
+file://klcc-consider-sysroot.patch \
S = ${WORKDIR}/git
--
1.9.1
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org javascript:;
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [OE-core] Style issue for recipes
On 09/04/2014 09:26 AM, Burton, Ross wrote: On 4 September 2014 16:41, akuster808 akuster...@gmail.com wrote: This is the same reason why I have split a bb into two parts when I submit upgrades. I feel it makes reviewing easier the next time a package gets upgraded. Trying to find the actual changes between a file being deleted and the new one being added might lead to missing something. If there are unintentional consequence by doing this, that is a problem. This is what git format-patch -M is for: it detects the rename and shows a proper diff. Ah, that is what -M does. That negates my concern. thanks for the info. - Armin Ross -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH 11/13] sdparm: add bash to RDEPENDS_sdparm
On 14-09-01 11:18 AM, Robert Yang wrote:
Bash scripts:
packages-split/sdparm/usr/bin/sas_disk_blink:#!/bin/bash
packages-split/sdparm/usr/bin/scsi_ch_swp:#!/bin/bash
Signed-off-by: Robert Yang liezhi.y...@windriver.com
---
meta-oe/recipes-support/sdparm/sdparm_1.08.bb |2 ++
1 file changed, 2 insertions(+)
diff --git a/meta-oe/recipes-support/sdparm/sdparm_1.08.bb
b/meta-oe/recipes-support/sdparm/sdparm_1.08.bb
index 713e451..be46b96 100644
--- a/meta-oe/recipes-support/sdparm/sdparm_1.08.bb
+++ b/meta-oe/recipes-support/sdparm/sdparm_1.08.bb
@@ -15,3 +15,5 @@ SRC_URI[md5sum] = be5786f37499018ef44f409597c92d42
SRC_URI[sha256sum] =
376b78a414b1a9c47f3f13dbeb963e7a3ec7be126f83927d6856b5f7ac425e57
inherit autotools
+
+RDEPENDS_${PN} += bash
We should move these scripts to a sdparm-scripts sub-pkg.
sdparm is a ~150K executable so making it pull in bash
at 1000K isn't good for embedded systems.
Neither script appears to be essential:
sas_disk_blink - blink the LED on a SAS disk
scsi_ch_swp:
Usage: scsi_ch_swp [-h] [-s 0|1] [-v] [-w] blk_device
...
Access the Software Write Protect (SWP) bit in the SCSI control
mode page and if changed adjust the Linux block device (e.g.
/dev/sdc) settings accordingly. If supported, when the SWP bit
is set (1) the device is read-only; when clear (0) the device
is read-write (i.e. its contents can be read and changed).
When no options given it reads SWP and gets blockdev's RO flag.
Comments or concerns?
--
# Randy MacLeod. SMTS, Linux, Wind River
Direct: 613.963.1350
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH 11/13] sdparm: add bash to RDEPENDS_sdparm
On 09/05/2014 05:10 AM, Randy MacLeod wrote:
On 14-09-01 11:18 AM, Robert Yang wrote:
Bash scripts:
packages-split/sdparm/usr/bin/sas_disk_blink:#!/bin/bash
packages-split/sdparm/usr/bin/scsi_ch_swp:#!/bin/bash
Signed-off-by: Robert Yang liezhi.y...@windriver.com
---
meta-oe/recipes-support/sdparm/sdparm_1.08.bb |2 ++
1 file changed, 2 insertions(+)
diff --git a/meta-oe/recipes-support/sdparm/sdparm_1.08.bb
b/meta-oe/recipes-support/sdparm/sdparm_1.08.bb
index 713e451..be46b96 100644
--- a/meta-oe/recipes-support/sdparm/sdparm_1.08.bb
+++ b/meta-oe/recipes-support/sdparm/sdparm_1.08.bb
@@ -15,3 +15,5 @@ SRC_URI[md5sum] = be5786f37499018ef44f409597c92d42
SRC_URI[sha256sum] =
376b78a414b1a9c47f3f13dbeb963e7a3ec7be126f83927d6856b5f7ac425e57
inherit autotools
+
+RDEPENDS_${PN} += bash
We should move these scripts to a sdparm-scripts sub-pkg.
Good idea, I will do it.
// Robert
sdparm is a ~150K executable so making it pull in bash
at 1000K isn't good for embedded systems.
Neither script appears to be essential:
sas_disk_blink - blink the LED on a SAS disk
scsi_ch_swp:
Usage: scsi_ch_swp [-h] [-s 0|1] [-v] [-w] blk_device
...
Access the Software Write Protect (SWP) bit in the SCSI control
mode page and if changed adjust the Linux block device (e.g.
/dev/sdc) settings accordingly. If supported, when the SWP bit
is set (1) the device is read-only; when clear (0) the device
is read-write (i.e. its contents can be read and changed).
When no options given it reads SWP and gets blockdev's RO flag.
Comments or concerns?
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
