Re: [oe] preferred version not available
On 07/18/11 23:05, Chris Larson wrote: On Mon, Jul 18, 2011 at 2:02 PM, Detlef Vollmannd...@vollmann.ch wrote: Ok, I found the problem: PREFERRED_VERSION refers to PV inside the recipe, not to the part of the filename after '_'. As I tinker with PV inside the recipe, bitbake is actually correct that a PV 'githead' is not available for linux-taurus. All variables which are typically set by the filename can be overridden. Those are simply defaults. See the definitions of PN, PV, and PR in bitbake.conf. Yes, I knew that (I actually wrote the line changing the PV myself). What surprised me (though it makes sense) that PREFERRED_VERSION refers to PV, and not directly to a part of the filename. It's probably still too much of 'make' history in my brain... Detlef ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
[oe] preferred version not available
Hello, this one really drives me crazy. Here's what I do: $ bitbake -D -D -D -D -g linux-taurus | fgrep linux-taurus DEBUG: Cache: /src/ccp-oe/taurus/recipes/linux/linux-taurus_githead.bb is not cached DEBUG: BB /src/ccp-oe/taurus/recipes/linux/linux-taurus_githead.bb: handle(data) DEBUG: LOAD /src/ccp-oe/taurus/recipes/linux/linux-taurus_githead.bb DEBUG: CONF /src/ccp-oe/taurus/recipes/linux/linux-taurus_githead.bb:5: including recipes/linux/ccp-linux.inc DEBUG: providers for linux-taurus are: ['linux-taurus'] NOTE: preferred version githead of linux-taurus not available (for item linux-taurus) It already starts with the first 'DEBUG' line: Why is it not cached. I have some other recipes for linux-taurus with version numbers that don't get parsed again because they are cached. But I can live with that. What really drives me nuts is the last line: it clearly parsed linux-taurus_githead.bb before, doesn't give me any error on it, but then tells me 'preferred version githead of linux-taurus not available'. It's clearly there, so why is it not available? The interesting thing is that I don't have any problems with my other *_githead.bb recipes, only with the linux kernel... I'd really appreciate any help! Detlef ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] preferred version not available
On Tuesday 19 July 2011 08:20:00 Detlef Vollmann wrote: On 07/18/11 23:05, Chris Larson wrote: All variables which are typically set by the filename can be overridden. Those are simply defaults. See the definitions of PN, PV, and PR in bitbake.conf. Yes, I knew that (I actually wrote the line changing the PV myself). What surprised me (though it makes sense) that PREFERRED_VERSION refers to PV, and not directly to a part of the filename. It's probably still too much of 'make' history in my brain... I wonder if it would make sense to add something to the error message that also lists the available versions? Then it would be a little more obvious what you need to set PREFERRED_VERSION to. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] preferred version not available
On 07/19/11 11:53, Paul Eggleton wrote: On Tuesday 19 July 2011 08:20:00 Detlef Vollmann wrote: On 07/18/11 23:05, Chris Larson wrote: All variables which are typically set by the filename can be overridden. Those are simply defaults. See the definitions of PN, PV, and PR in bitbake.conf. Yes, I knew that (I actually wrote the line changing the PV myself). What surprised me (though it makes sense) that PREFERRED_VERSION refers to PV, and not directly to a part of the filename. It's probably still too much of 'make' history in my brain... I wonder if it would make sense to add something to the error message that also lists the available versions? Then it would be a little more obvious what you need to set PREFERRED_VERSION to. That would be great. And while we are in wishlist mode ;-) : With a high enough debug level (I think 2), you'll get a list of providers for a specific target. To get also a list of versions for a specific package (PN), would be really helpful. Detlef ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
[oe] [PATCH] nodejs: Add patch to compile with GCC 4.3.3
* Add a patch to nodejs to allow compiling with GCC versions
less than or equal to 4.3.3.
* Define the function nodejs_get_gcc_ver to allow applying the
patch conditionally based on compiler version.
* Patch based on post at https://github.com/joyent/node/issues/883
Signed-off-by: Chase Maupin chase.mau...@ti.com
---
...01-Add-missing-compiler-flags-for-GCC-4.3.patch | 34
recipes/nodejs/nodejs_0.4.0.bb |9 +
2 files changed, 43 insertions(+), 0 deletions(-)
create mode 100644
recipes/nodejs/files/0001-Add-missing-compiler-flags-for-GCC-4.3.patch
diff --git
a/recipes/nodejs/files/0001-Add-missing-compiler-flags-for-GCC-4.3.patch
b/recipes/nodejs/files/0001-Add-missing-compiler-flags-for-GCC-4.3.patch
new file mode 100644
index 000..080b88f
--- /dev/null
+++ b/recipes/nodejs/files/0001-Add-missing-compiler-flags-for-GCC-4.3.patch
@@ -0,0 +1,34 @@
+From 7cb51ed25b688be08825950ce3f5ce2ad38e3f95 Mon Sep 17 00:00:00 2001
+From: Chase Maupin chase.mau...@ti.com
+Date: Tue, 12 Jul 2011 11:00:48 -0500
+Subject: [PATCH] Add missing compiler flags for GCC 4.3
+
+* When compiling nodejs for GCC 4.3.3 you need to also add the
+ flag -fno-tree-sink.
+* This patch was taken from the thread at:
+* https://github.com/joyent/node/issues/883
+* Believe that no action is taken on this change upstream because
+ it is GCC 4.3.3 specific and is not required for GCC 4.5
+
+Upstream-Status: Denied
+
+Signed-off-by: Chase Maupin chase.mau...@ti.com
+---
+ deps/v8/SConstruct |1 +
+ 1 files changed, 1 insertions(+), 0 deletions(-)
+
+diff --git a/deps/v8/SConstruct b/deps/v8/SConstruct
+index b2542fd..31c4c7b 100644
+--- a/deps/v8/SConstruct
b/deps/v8/SConstruct
+@@ -210,6 +210,7 @@ LIBRARY_FLAGS = {
+ },
+ 'arch:arm': {
+ 'CPPDEFINES': ['V8_TARGET_ARCH_ARM'],
++ 'CCFLAGS': ['-fno-tree-sink'],
+ 'unalignedaccesses:on' : {
+ 'CPPDEFINES' : ['CAN_USE_UNALIGNED_ACCESSES=1']
+ },
+--
+1.7.0.4
+
diff --git a/recipes/nodejs/nodejs_0.4.0.bb b/recipes/nodejs/nodejs_0.4.0.bb
index be3d23e..fe8a878 100644
--- a/recipes/nodejs/nodejs_0.4.0.bb
+++ b/recipes/nodejs/nodejs_0.4.0.bb
@@ -4,11 +4,20 @@ LICENSE = MIT
DEPENDS = openssl
+PR = r1
+
+def nodejs_get_gcc_version(d):
+import subprocess,os,bb
+if os.path.exists(bb.data.getVar('TOOLCHAIN_PATH', d,
1)+'/bin/'+bb.data.getVar('TARGET_PREFIX', d, 1)+'gcc'):
+return subprocess.Popen([bb.data.getVar('TOOLCHAIN_PATH', d,
1)+'/bin/'+bb.data.getVar('TARGET_PREFIX', d, 1)+'gcc', '-v'],
stderr=subprocess.PIPE).communicate()[1].splitlines()[-1].split()[2]
+
SRC_URI = \
http://nodejs.org/dist/node-v${PV}.tar.gz \
file://libev-cross-cc_${PV}.patch \
+SRC_URI += ${@[,
file://0001-Add-missing-compiler-flags-for-GCC-4.3.patch][nodejs_get_gcc_version(d)
= 4.3.3]}
+
SRC_URI[md5sum] = 18f89256751f9b8e27dee8494f508171
SRC_URI[sha256sum] =
4a30bd9963373cb86a994479bdd451ab3b6f2124f0089493366315da79d3408e
--
1.7.0.4
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH] nodejs: Add patch to compile with GCC 4.3.3
Just FYI, this patch is against the nodejs version in the maintenance branch
and was sent to the list so it could be picked up into Koen's staging tree for
his next pull request. The previously sent version was for the OE dev mainline
and has already been accepted.
-Original Message-
From: Chase Maupin [mailto:chasemaupi...@gmail.com]
Sent: Tuesday, July 19, 2011 7:30 AM
To: openembedded-devel@lists.openembedded.org
Cc: Maupin, Chase
Subject: [PATCH] nodejs: Add patch to compile with GCC 4.3.3
* Add a patch to nodejs to allow compiling with GCC versions
less than or equal to 4.3.3.
* Define the function nodejs_get_gcc_ver to allow applying the
patch conditionally based on compiler version.
* Patch based on post at https://github.com/joyent/node/issues/883
Signed-off-by: Chase Maupin chase.mau...@ti.com
---
...01-Add-missing-compiler-flags-for-GCC-4.3.patch | 34
recipes/nodejs/nodejs_0.4.0.bb |9 +
2 files changed, 43 insertions(+), 0 deletions(-)
create mode 100644 recipes/nodejs/files/0001-Add-missing-compiler-
flags-for-GCC-4.3.patch
diff --git a/recipes/nodejs/files/0001-Add-missing-compiler-flags-for-
GCC-4.3.patch b/recipes/nodejs/files/0001-Add-missing-compiler-flags-
for-GCC-4.3.patch
new file mode 100644
index 000..080b88f
--- /dev/null
+++ b/recipes/nodejs/files/0001-Add-missing-compiler-flags-for-GCC-
4.3.patch
@@ -0,0 +1,34 @@
+From 7cb51ed25b688be08825950ce3f5ce2ad38e3f95 Mon Sep 17 00:00:00 2001
+From: Chase Maupin chase.mau...@ti.com
+Date: Tue, 12 Jul 2011 11:00:48 -0500
+Subject: [PATCH] Add missing compiler flags for GCC 4.3
+
+* When compiling nodejs for GCC 4.3.3 you need to also add the
+ flag -fno-tree-sink.
+* This patch was taken from the thread at:
+* https://github.com/joyent/node/issues/883
+* Believe that no action is taken on this change upstream because
+ it is GCC 4.3.3 specific and is not required for GCC 4.5
+
+Upstream-Status: Denied
+
+Signed-off-by: Chase Maupin chase.mau...@ti.com
+---
+ deps/v8/SConstruct |1 +
+ 1 files changed, 1 insertions(+), 0 deletions(-)
+
+diff --git a/deps/v8/SConstruct b/deps/v8/SConstruct
+index b2542fd..31c4c7b 100644
+--- a/deps/v8/SConstruct
b/deps/v8/SConstruct
+@@ -210,6 +210,7 @@ LIBRARY_FLAGS = {
+ },
+ 'arch:arm': {
+ 'CPPDEFINES': ['V8_TARGET_ARCH_ARM'],
++ 'CCFLAGS': ['-fno-tree-sink'],
+ 'unalignedaccesses:on' : {
+ 'CPPDEFINES' : ['CAN_USE_UNALIGNED_ACCESSES=1']
+ },
+--
+1.7.0.4
+
diff --git a/recipes/nodejs/nodejs_0.4.0.bb
b/recipes/nodejs/nodejs_0.4.0.bb
index be3d23e..fe8a878 100644
--- a/recipes/nodejs/nodejs_0.4.0.bb
+++ b/recipes/nodejs/nodejs_0.4.0.bb
@@ -4,11 +4,20 @@ LICENSE = MIT
DEPENDS = openssl
+PR = r1
+
+def nodejs_get_gcc_version(d):
+import subprocess,os,bb
+if os.path.exists(bb.data.getVar('TOOLCHAIN_PATH', d,
1)+'/bin/'+bb.data.getVar('TARGET_PREFIX', d, 1)+'gcc'):
+return subprocess.Popen([bb.data.getVar('TOOLCHAIN_PATH', d,
1)+'/bin/'+bb.data.getVar('TARGET_PREFIX', d, 1)+'gcc', '-v'],
stderr=subprocess.PIPE).communicate()[1].splitlines()[-1].split()[2]
+
SRC_URI = \
http://nodejs.org/dist/node-v${PV}.tar.gz \
file://libev-cross-cc_${PV}.patch \
+SRC_URI += ${@[, file://0001-Add-missing-compiler-flags-for-GCC-
4.3.patch][nodejs_get_gcc_version(d) = 4.3.3]}
+
SRC_URI[md5sum] = 18f89256751f9b8e27dee8494f508171
SRC_URI[sha256sum] =
4a30bd9963373cb86a994479bdd451ab3b6f2124f0089493366315da79d3408e
--
1.7.0.4
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
[oe] Added header file to linux kernel - how to export
Hi, I have made a patch to the linux kernel, involving adding some ioctl's. Relevant definitions are in a .h file. Now I need to access this .h file from another recipe (that builds a utility using those ioctl's) but the headers in sysroots/xxx-linux/usr/include are put there (by linux-libc-headers?) long before the target Linux kernel is patched and built. I'm thinking about adding a do_install_append to the linux recipe but that doesn't feel right. Neither does adding a path from the util recipe build to the work folder of linux kernel. Third alternative would be to build the driver as an LKM but I really like to have it built into the kernel... If any of you have some good advice here I would be very happy! Best Regards, Mats ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] preferred version not available
On Tue, Jul 19, 2011 at 12:20 AM, Detlef Vollmann d...@vollmann.ch wrote: On 07/18/11 23:05, Chris Larson wrote: On Mon, Jul 18, 2011 at 2:02 PM, Detlef Vollmannd...@vollmann.ch wrote: Ok, I found the problem: PREFERRED_VERSION refers to PV inside the recipe, not to the part of the filename after '_'. As I tinker with PV inside the recipe, bitbake is actually correct that a PV 'githead' is not available for linux-taurus. All variables which are typically set by the filename can be overridden. Those are simply defaults. See the definitions of PN, PV, and PR in bitbake.conf. Yes, I knew that (I actually wrote the line changing the PV myself). What surprised me (though it makes sense) that PREFERRED_VERSION refers to PV, and not directly to a part of the filename. I'm not sure why that would be surprising. PN, PV, and PR are what are used. The fact that they default to being based on the filename is just an artifact of how oe does things. You could quite easily change that, and make it required to set them all in the recipe. Bitbake does *not* care about the filename, other than in determining what bbappend to apply to the recipe when an append exists. -- Christopher Larson clarson at kergoth dot com Founder - BitBake, OpenEmbedded, OpenZaurus Maintainer - Tslib Senior Software Engineer, Mentor Graphics ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
[oe] [meta-oe][PATCH v2 0/2] Misc updates
Hey all,
Here's a short 'misc' series with a few changes. First, take oe.dev's
mercurial-native and update to the current version. We don't yet have any
hg:// URIs but this lets us be ready for when we do. Second, one of the
patches guile needs was in the wrong directory to be used/found, so move
it.
v2: Per Paul Menzel, start with r0 not r1 and remember RP reminded me that
NATIVE_INSTALL_WORKS is useless now.
The following changes since commit 7254205d68c9321d7a7073a74a77f46c17a98b27:
Khem Raj (1):
systemd: Replace use of %m in printf formats
are available in the git repository at:
git://git.openembedded.org/meta-openembedded-contrib trini/misc-v2
http://cgit.openembedded.org/cgit.cgi/meta-openembedded-contrib/log/?h=trini/misc-v2
Tom Rini (2):
guile: Move 'configure-fix.patch' to guile-1.8.7 dir
mercurial-native: Add 1.9 version
.../mercurial/mercurial-native_1.9.bb | 22
.../configure-fix.patch|0
2 files changed, 22 insertions(+), 0 deletions(-)
create mode 100644 meta-oe/recipes-devtools/mercurial/mercurial-native_1.9.bb
rename meta-oe/recipes-support/guile/{guile-native-1.8.7 =
guile-1.8.7}/configure-fix.patch (100%)
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
[oe] [meta-oe][PATCH v2 2/2] mercurial-native: Add 1.9 version
This is based on 91c14caa8819b08def8ea99e02949e49604c2e86 from oe.dev
with an update to 1.9.
Signed-off-by: Tom Rini tom_r...@mentor.com
---
.../mercurial/mercurial-native_1.9.bb | 22
1 files changed, 22 insertions(+), 0 deletions(-)
create mode 100644 meta-oe/recipes-devtools/mercurial/mercurial-native_1.9.bb
diff --git a/meta-oe/recipes-devtools/mercurial/mercurial-native_1.9.bb
b/meta-oe/recipes-devtools/mercurial/mercurial-native_1.9.bb
new file mode 100644
index 000..7430a74
--- /dev/null
+++ b/meta-oe/recipes-devtools/mercurial/mercurial-native_1.9.bb
@@ -0,0 +1,22 @@
+DESCRIPTION = The Mercurial distributed SCM
+HOMEPAGE = http://mercurial.selenic.com/;
+SECTION = console/utils
+LICENSE = GPLv2
+LIC_FILES_CHKSUM = file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263
+DEPENDS = python-native
+PR = r0
+
+SRC_URI = http://mercurial.selenic.com/release/mercurial-${PV}.tar.gz;
+SRC_URI[md5sum] = d4842129fa2732eb6ed1180467bc32e2
+SRC_URI[sha256sum] =
711e4b1cd2924a7a88499d6c431a9122390183bf554d4e153edbb3b2f30123e0
+
+S = ${WORKDIR}/mercurial-${PV}
+
+inherit native
+
+EXTRA_OEMAKE = STAGING_LIBDIR=${STAGING_LIBDIR}
STAGING_INCDIR=${STAGING_INCDIR} \
+BUILD_SYS=${BUILD_SYS} HOST_SYS=${HOST_SYS} PREFIX=${prefix}
+
+do_install () {
+oe_runmake -e install-bin DESTDIR=${D} PREFIX=${prefix}
+}
--
1.7.0.4
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
[oe] [meta-oe][PATCH v2 1/2] guile: Move 'configure-fix.patch' to guile-1.8.7 dir
This patch is used by both native and target recipes.
Signed-off-by: Tom Rini tom_r...@mentor.com
---
.../configure-fix.patch|0
1 files changed, 0 insertions(+), 0 deletions(-)
rename meta-oe/recipes-support/guile/{guile-native-1.8.7 =
guile-1.8.7}/configure-fix.patch (100%)
diff --git
a/meta-oe/recipes-support/guile/guile-native-1.8.7/configure-fix.patch
b/meta-oe/recipes-support/guile/guile-1.8.7/configure-fix.patch
similarity index 100%
rename from meta-oe/recipes-support/guile/guile-native-1.8.7/configure-fix.patch
rename to meta-oe/recipes-support/guile/guile-1.8.7/configure-fix.patch
--
1.7.0.4
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Added header file to linux kernel - how to export
Hi,
Your could put something like this:
do_stage_append() {
cp ${S}/my_ioctl.h ${STAGING_KERNEL_DIR}/include/linux
}
in your recipes/linu.bb
With kind regards,
Fabrice
-Ursprüngliche Nachricht-
Von: openembedded-devel-boun...@lists.openembedded.org
[mailto:openembedded-devel-boun...@lists.openembedded.org] Im
Auftrag von Mats Kärrman
Gesendet: Dienstag, 19. Juli 2011 15:57
An: openembedded-devel@lists.openembedded.org
Betreff: [oe] Added header file to linux kernel - how to export
Hi,
I have made a patch to the linux kernel, involving adding
some ioctl's. Relevant definitions are in a .h file. Now I
need to access this .h file from another recipe (that builds
a utility using those ioctl's) but the headers in
sysroots/xxx-linux/usr/include are put there (by
linux-libc-headers?) long before the target Linux kernel is
patched and built.
I'm thinking about adding a do_install_append to the linux
recipe but that doesn't feel right. Neither does adding a
path from the util recipe build to the work folder of linux
kernel. Third alternative would be to build the driver as an
LKM but I really like to have it built into the kernel...
If any of you have some good advice here I would be very happy!
Best Regards,
Mats
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [OE-core][meta-oe] Problems on downloading sources (was [OE-core] Problems downloading xfwm4 4.8.1)
On Monday, July 18, 2011 11:19:01 PM Andreas Mueller wrote: On Monday, July 18, 2011 11:10:55 PM you wrote: Ciao currently I am porting my local oe recipes for xfce-4.8 to oe-core. Everything seems fine so far - except xfwm4. This one drives me totally insane: If you check the fetch log attched and copy the first url into a browser it starts downloading without problems but oe complains. Could somebody please point me onto what is going wrong - if you need further information I'll send... I found a hook on what is going wrong - forget my prevoius mail - sorry fo the noise.. Sorry but my 'hook' was some late night crap. I attached what I did up to now. It is meta-xfce which should live in meta- openembedded. I checked on fresh tmp and without downloaded sources. For (at least) xfwm4 and xfce4-appfinder build fails when downloading sources. For xfce4- appfinder I get: ERROR: Function 'Fetcher failure for URL: 'http://archive.xfce.org/src/xfce/xfce4-appfinder/4.8/xfce4- appfinder-4.8.0.tar.bz2'. Unable to fetch URL http://archive.xfce.org/src/xfce/xfce4-appfinder/4.8/xfce4-appfinder-4.8.0.tar.bz2 from any source.' failed ERROR: Logfile of failure stored in: /home/Superandy/tmp/oe-core- eglibc/work/armv7a-angstrom-linux-gnueabi/xfce4-appfinder-4.8.0- r0/temp/log.do_fetch.30009 Log data follows: | NOTE: fetch http://archive.xfce.org/src/xfce/xfce4-appfinder/4.8/xfce4- appfinder-4.8.0.tar.bz2 | NOTE: fetch http://www.angstrom-distribution.org/unstable/sources/xfce4- appfinder-4.8.0.tar.bz2 | ERROR: Function 'Fetcher failure for URL: 'http://archive.xfce.org/src/xfce/xfce4-appfinder/4.8/xfce4- appfinder-4.8.0.tar.bz2'. Unable to fetch URL http://archive.xfce.org/src/xfce/xfce4-appfinder/4.8/xfce4-appfinder-4.8.0.tar.bz2 from any source.' failed NOTE: package xfce4-appfinder-4.8.0-r0: task do_fetch: Failed If I enter http://archive.xfce.org/src/xfce/xfce4-appfinder/4.8/xfce4- appfinder-4.8.0.tar.bz2 in my browser or perform wget manually, the source file is downloaded properly!! Could somebody please spend some time with the attachment and tell me what's going on here?? Thanks Andreas meta-xfce.tar.gz Description: application/compressed-tar ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [OE-core][meta-oe] Problems on downloading sources (was [OE-core] Problems downloading xfwm4 4.8.1)
On Wed, 2011-07-20 at 00:38 +0200, Andreas Mueller wrote: On Monday, July 18, 2011 11:19:01 PM Andreas Mueller wrote: On Monday, July 18, 2011 11:10:55 PM you wrote: Ciao currently I am porting my local oe recipes for xfce-4.8 to oe-core. Everything seems fine so far - except xfwm4. This one drives me totally insane: If you check the fetch log attched and copy the first url into a browser it starts downloading without problems but oe complains. Could somebody please point me onto what is going wrong - if you need further information I'll send... I found a hook on what is going wrong - forget my prevoius mail - sorry fo the noise.. Sorry but my 'hook' was some late night crap. I attached what I did up to now. It is meta-xfce which should live in meta- openembedded. I checked on fresh tmp and without downloaded sources. For (at least) xfwm4 and xfce4-appfinder build fails when downloading sources. For xfce4- appfinder I get: ERROR: Function 'Fetcher failure for URL: 'http://archive.xfce.org/src/xfce/xfce4-appfinder/4.8/xfce4- appfinder-4.8.0.tar.bz2'. Unable to fetch URL http://archive.xfce.org/src/xfce/xfce4-appfinder/4.8/xfce4-appfinder-4.8.0.tar.bz2 from any source.' failed ERROR: Logfile of failure stored in: /home/Superandy/tmp/oe-core- eglibc/work/armv7a-angstrom-linux-gnueabi/xfce4-appfinder-4.8.0- r0/temp/log.do_fetch.30009 Log data follows: | NOTE: fetch http://archive.xfce.org/src/xfce/xfce4-appfinder/4.8/xfce4- appfinder-4.8.0.tar.bz2 | NOTE: fetch http://www.angstrom-distribution.org/unstable/sources/xfce4- appfinder-4.8.0.tar.bz2 | ERROR: Function 'Fetcher failure for URL: 'http://archive.xfce.org/src/xfce/xfce4-appfinder/4.8/xfce4- appfinder-4.8.0.tar.bz2'. Unable to fetch URL http://archive.xfce.org/src/xfce/xfce4-appfinder/4.8/xfce4-appfinder-4.8.0.tar.bz2 from any source.' failed NOTE: package xfce4-appfinder-4.8.0-r0: task do_fetch: Failed If I enter http://archive.xfce.org/src/xfce/xfce4-appfinder/4.8/xfce4- appfinder-4.8.0.tar.bz2 in my browser or perform wget manually, the source file is downloaded properly!! Could somebody please spend some time with the attachment and tell me what's going on here?? I'd guess it's Yocto #1256[1], namely that fetcher reports a download failure when only the SRC_URI checksums mismatched The idea is that the fetcher retries downloads a few times when the checksums do not match, unfortunately at the default log level this just looks like a fetch failure. Can you run bitbake with -DD and see if you can see a checksum error? Or just verify checksums by hand? Cheers, Joshua 1. http://bugzilla.pokylinux.org/show_bug.cgi?id=1256 -- Joshua Lock Yocto Project Johannes factotum Intel Open Source Technology Centre ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
[oe] [PATCH v2] linux-omap-psp, linux-omap: Added patch to fix MMC timeout errors
This fixes MMC errors due to timeouts on certain SD Cards, following suggestions
to set dto to 14 by Jason Kridner and Steven Kipisz
Details of the issue:
http://talk.maemo.org/showthread.php?p=1000707#post1000707
---
Changes since earlier patch:
* Set dto to 14 instead of doubling timeout
Other notes:
* We have confirmation that this patch fixes the issue, so it is safe to apply
to the maintentance tree
* Also please revert the earlier patch from the dev tree titled
linux-omap-psp: Added patch to fix MMC timeout errors (commit
93e91091c7e2864274207cc7c59e3f64e453f843)
Another thread discussing the issue:
http://www.mail-archive.com/linux-omap@vger.kernel.org/msg42214.html
Thanks!
...mc-Adjust-dto-to-eliminate-timeout-errors.patch | 27
...mc-Adjust-dto-to-eliminate-timeout-errors.patch | 27
recipes/linux/linux-omap-psp_2.6.32.bb |3 +-
recipes/linux/linux-omap_2.6.39.bb |3 +-
4 files changed, 58 insertions(+), 2 deletions(-)
create mode 100644
recipes/linux/linux-omap-2.6.39/beagle/0006-omap-mmc-Adjust-dto-to-eliminate-timeout-errors.patch
create mode 100644
recipes/linux/linux-omap-psp-2.6.32/0047-omap-mmc-Adjust-dto-to-eliminate-timeout-errors.patch
diff --git
a/recipes/linux/linux-omap-2.6.39/beagle/0006-omap-mmc-Adjust-dto-to-eliminate-timeout-errors.patch
b/recipes/linux/linux-omap-2.6.39/beagle/0006-omap-mmc-Adjust-dto-to-eliminate-timeout-errors.patch
new file mode 100644
index 000..7a563b7
--- /dev/null
+++
b/recipes/linux/linux-omap-2.6.39/beagle/0006-omap-mmc-Adjust-dto-to-eliminate-timeout-errors.patch
@@ -0,0 +1,27 @@
+From bd0b2f97c48aa6aac0c6a494f1c6ba5af5de486b Mon Sep 17 00:00:00 2001
+From: Joel A Fernandes agnel.j...@gmail.com
+Date: Mon, 18 Jul 2011 23:13:41 -0500
+Subject: [PATCH] omap_hsmmc: Set dto to max value of 14 to avoid SD Card
timeouts
+
+Signed-off-by: Joel A Fernandes agnel.j...@gmail.com
+---
+ drivers/mmc/host/omap_hsmmc.c |3 +++
+ 1 files changed, 3 insertions(+), 0 deletions(-)
+
+diff --git a/drivers/mmc/host/omap_hsmmc.c b/drivers/mmc/host/omap_hsmmc.c
+index 9646a75..7443647 100644
+--- a/drivers/mmc/host/omap_hsmmc.c
b/drivers/mmc/host/omap_hsmmc.c
+@@ -1049,6 +1049,9 @@ static void set_data_timeout(struct omap_hsmmc_host
*host,
+ dto = 14;
+ }
+
++ /* Set dto to max value of 14 to avoid SD Card timeouts */
++ dto = 14;
++
+ reg = ~DTO_MASK;
+ reg |= dto DTO_SHIFT;
+ OMAP_HSMMC_WRITE(host-base, SYSCTL, reg);
+--
+1.7.0.4
+
diff --git
a/recipes/linux/linux-omap-psp-2.6.32/0047-omap-mmc-Adjust-dto-to-eliminate-timeout-errors.patch
b/recipes/linux/linux-omap-psp-2.6.32/0047-omap-mmc-Adjust-dto-to-eliminate-timeout-errors.patch
new file mode 100644
index 000..7a563b7
--- /dev/null
+++
b/recipes/linux/linux-omap-psp-2.6.32/0047-omap-mmc-Adjust-dto-to-eliminate-timeout-errors.patch
@@ -0,0 +1,27 @@
+From bd0b2f97c48aa6aac0c6a494f1c6ba5af5de486b Mon Sep 17 00:00:00 2001
+From: Joel A Fernandes agnel.j...@gmail.com
+Date: Mon, 18 Jul 2011 23:13:41 -0500
+Subject: [PATCH] omap_hsmmc: Set dto to max value of 14 to avoid SD Card
timeouts
+
+Signed-off-by: Joel A Fernandes agnel.j...@gmail.com
+---
+ drivers/mmc/host/omap_hsmmc.c |3 +++
+ 1 files changed, 3 insertions(+), 0 deletions(-)
+
+diff --git a/drivers/mmc/host/omap_hsmmc.c b/drivers/mmc/host/omap_hsmmc.c
+index 9646a75..7443647 100644
+--- a/drivers/mmc/host/omap_hsmmc.c
b/drivers/mmc/host/omap_hsmmc.c
+@@ -1049,6 +1049,9 @@ static void set_data_timeout(struct omap_hsmmc_host
*host,
+ dto = 14;
+ }
+
++ /* Set dto to max value of 14 to avoid SD Card timeouts */
++ dto = 14;
++
+ reg = ~DTO_MASK;
+ reg |= dto DTO_SHIFT;
+ OMAP_HSMMC_WRITE(host-base, SYSCTL, reg);
+--
+1.7.0.4
+
diff --git a/recipes/linux/linux-omap-psp_2.6.32.bb
b/recipes/linux/linux-omap-psp_2.6.32.bb
index ab9a04a..7a0797a 100644
--- a/recipes/linux/linux-omap-psp_2.6.32.bb
+++ b/recipes/linux/linux-omap-psp_2.6.32.bb
@@ -9,7 +9,7 @@ COMPATIBLE_MACHINE =
am3517-crane|beagleboard|omap3evm|am3517-evm|dm37x-evm|am3
SRCREV = 5fc29e7b2a76a64a739f857858ef0b98294aa155
# The main PR is now using MACHINE_KERNEL_PR, for omap3 see
conf/machine/include/omap3.inc
-MACHINE_KERNEL_PR_append = e+gitr${SRCREV}
+MACHINE_KERNEL_PR_append = f+gitr${SRCREV}
SRC_URI =
git://arago-project.org/git/projects/linux-omap3.git;protocol=http;branch=master
\
file://0001-Added-Crane-Board-support.patch \
@@ -59,6 +59,7 @@ SRC_URI =
git://arago-project.org/git/projects/linux-omap3.git;protocol=http;br
file://0044-ARM-OMAP-beagle-every-known-beagle-except-revB-uses-.patch \
file://0045-ARM-OMAP-beagle-add-support-for-beagleFPGA-expansion.patch \
file://0046-ARM-OMAP-beagle-disable-uart-timeout.patch \
+
