(No subject)

(No subject)

[Lele]

(No subject)

[Theodore A. Roth]

From 2c41e9d95bfedd8a73a29478fbe49e7ec538e7f9 Mon Sep 17 00:00:00 2001
From: Theodore A. Roth <troth@openavr.org>
Date: Thu, 19 Mar 2009 10:50:54 -0700
Subject: [PATCH] doc/usermanual/chapters: Replace references to packages dir with recipes dir.

---
 docs/usermanual/chapters/common_use_cases.xml |    6 +-
 docs/usermanual/chapters/features.xml         |    8 ++--
 docs/usermanual/chapters/getting_oe.xml       |    6 +-
 docs/usermanual/chapters/metadata.xml         |    2 +-
 docs/usermanual/chapters/recipes.xml          |   30 +++++++-------
 docs/usermanual/chapters/usage.xml            |   50 ++++++++++++------------
 6 files changed, 51 insertions(+), 51 deletions(-)

diff --git a/docs/usermanual/chapters/common_use_cases.xml b/docs/usermanual/chapters/common_use_cases.xml
index 4497683..143cbe0 100644
--- a/docs/usermanual/chapters/common_use_cases.xml
+++ b/docs/usermanual/chapters/common_use_cases.xml
@@ -252,10 +252,10 @@ export LOCALDIR=$PWD/secret-isv
 
         <screen>
 DL_DIR = "${OEDIR}/sources"
-BBFILES := "${OEDIR}/openembedded/packages/*/*.bb ${LOCALDIR}/packages/*/*.bb"
+BBFILES := "${OEDIR}/openembedded/recipes/*/*.bb ${LOCALDIR}/recipes/*/*.bb"
 BBFILE_COLLECTIONS = "upstream local"
-BBFILE_PATTERN_upstream = "^${OEDIR}/openembedded/packages/"
-BBFILE_PATTERN_local = "^${LOCALDIR}/packages/"
+BBFILE_PATTERN_upstream = "^${OEDIR}/openembedded/recipes/"
+BBFILE_PATTERN_local = "^${LOCALDIR}/recipes/"
 BBFILE_PRIORITY_upstream = "5"
 BBFILE_PRIORITY_local = "10"
 BBMASK = ""
diff --git a/docs/usermanual/chapters/features.xml b/docs/usermanual/chapters/features.xml
index 8eecaa9..3cbf1d8 100644
--- a/docs/usermanual/chapters/features.xml
+++ b/docs/usermanual/chapters/features.xml
@@ -39,10 +39,10 @@
     <para>This section is a stub, help us by expanding it</para>
 
     <para><screen>
-BBFILES := "${OEDIR}/openembedded/packages/*/*.bb ${LOCALDIR}/packages/*/*.bb"
+BBFILES := "${OEDIR}/openembedded/recipes/*/*.bb ${LOCALDIR}/recipes/*/*.bb"
 BBFILE_COLLECTIONS = "upstream local"
-BBFILE_PATTERN_upstream = "^${OEDIR}/openembedded/packages/"
-BBFILE_PATTERN_local = "^${LOCALDIR}/packages/"
+BBFILE_PATTERN_upstream = "^${OEDIR}/openembedded/recipes/"
+BBFILE_PATTERN_local = "^${LOCALDIR}/recipes/"
 BBFILE_PRIORITY_upstream = "5"
 BBFILE_PRIORITY_local = "10"
 </screen></para>
@@ -75,4 +75,4 @@ MACHINE_FEATURES = "kernel26 apm alsa pcmcia bluetooth irda usbgadget"
 
     <para>This section is a stub, help us by expanding it</para>
   </section>
-</chapter>
\ No newline at end of file
+</chapter>
diff --git a/docs/usermanual/chapters/getting_oe.xml b/docs/usermanual/chapters/getting_oe.xml
index d71ea71..ed7fd11 100644
--- a/docs/usermanual/chapters/getting_oe.xml
+++ b/docs/usermanual/chapters/getting_oe.xml
@@ -232,7 +232,7 @@ $ vi build/conf/local.conf</screen>
         distribution and the Openmoko gta01 machine:
 
         <screen>
-BBFILES = "${OEBASE}/openembedded/packages/*/*.bb"
+BBFILES = "${OEBASE}/openembedded/recipes/*/*.bb"
 DISTRO = "angstrom-2008.1"
 MACHINE = "om-gta01"</screen>
       </para>
@@ -297,11 +297,11 @@ MACHINE = "om-gta01"</screen>
     <para>To build a single package, bypassing the long parse step (and
       therefore its dependencies -- use with care):
 
-      <screen>$ bitbake -b $OEBASE/openembedded/packages/blah/blah.bb</screen>
+      <screen>$ bitbake -b $OEBASE/openembedded/recipes/blah/blah.bb</screen>
     </para>
 
     <para>There are a few groups of special recipes located in subdirectories
-      of the <filename>$OEBASE/openembedded/packages/</filename>
+      of the <filename>$OEBASE/openembedded/recipes/</filename>
       directory. These groups are:
 
       <variablelist>
diff --git a/docs/usermanual/chapters/metadata.xml b/docs/usermanual/chapters/metadata.xml
index 54fb523..3e76b2d 100644
--- a/docs/usermanual/chapters/metadata.xml
+++ b/docs/usermanual/chapters/metadata.xml
@@ -65,7 +65,7 @@
         </varlistentry>
 
         <varlistentry>
-          <term><filename>packages/</filename></term>
+          <term><filename>recipes/</filename></term>
           <listitem>
             <para>Conatins all of the
               <application>BitBake</application> <filename>.bb</filename>
diff --git a/docs/usermanual/chapters/recipes.xml b/docs/usermanual/chapters/recipes.xml
index c1ca456..1107873 100644
--- a/docs/usermanual/chapters/recipes.xml
+++ b/docs/usermanual/chapters/recipes.xml
@@ -1081,9 +1081,9 @@ ${FILE_DIRNAME}/${PN}:${FILE_DIRNAME}/files:${FILE_DIRNAME}"</screen></para>
 
       <para>First we'll create the myhelloworld.c file and a readme file.
       We'll place this in the files subdirectory, which is one of the places
-      that is searched for file:// URI's:<screen>mkdir packages/myhelloworld
-mkdir packages/myhelloworld/files
-cat &gt; packages/myhelloworld/files/myhelloworld.c
+      that is searched for file:// URI's:<screen>mkdir recipes/myhelloworld
+mkdir recipes/myhelloworld/files
+cat &gt; recipes/myhelloworld/files/myhelloworld.c
 #include &lt;stdio.h&gt;
 
 int main(int argc, char** argv)
@@ -1092,11 +1092,11 @@ int main(int argc, char** argv)
         return 0;
 }
 ^D
-cat &gt; packages/myhelloworld/files/README.txt
+cat &gt; recipes/myhelloworld/files/README.txt
 Readme file for myhelloworld.
 ^D</screen></para>
 
-      <para>Now we have a directory for our recipe, packages/myhelloworld, and
+      <para>Now we have a directory for our recipe, recipes/myhelloworld, and
       we've created a files subdirectory in there to store our local files.
       We've created two local files, the C source code for our helloworld
       program and a readme file. Now we need to create the bitbake
@@ -1186,7 +1186,7 @@ PR = "r0"</screen></para>
       </itemizedlist>
 
       <para>We'll consider this release 0 and version 0.1 of a program called
-      helloworld. So we'll name the recipe myhelloworld_0.1.bb:<screen>cat &gt; packages/myhelloworld/myhelloworld_0.1.bb
+      helloworld. So we'll name the recipe myhelloworld_0.1.bb:<screen>cat &gt; recipes/myhelloworld/myhelloworld_0.1.bb
 DESCRIPTION = "Hello world program"
 PR = "r0"
 
@@ -1203,13 +1203,13 @@ do_install() {
         install -m 0644 ${WORKDIR}/README.txt ${D}${docdir}/myhelloworld
 }
 ^D</screen>Now we are ready to build our package, hopefully it'll all work
-      since it's such a simple example:<screen>~/oe%&gt; bitbake -b packages/myhelloworld/myhelloworld_0.1.bb
+      since it's such a simple example:<screen>~/oe%&gt; bitbake -b recipes/myhelloworld/myhelloworld_0.1.bb
 NOTE: package myhelloworld-0.1: started
 NOTE: package myhelloworld-0.1-r0: task do_fetch: started
 NOTE: package myhelloworld-0.1-r0: task do_fetch: completed
 NOTE: package myhelloworld-0.1-r0: task do_unpack: started
-NOTE: Unpacking /home/lenehan/devel/oe/local-packages/myhelloworld/files/helloworld.c to /home/lenehan/devel/oe/build/titan-glibc-25/tmp/work/myhelloworld-0.1-r0/
-NOTE: Unpacking /home/lenehan/devel/oe/local-packages/myhelloworld/files/README.txt to /home/lenehan/devel/oe/build/titan-glibc-25/tmp/work/myhelloworld-0.1-r0/
+NOTE: Unpacking /home/lenehan/devel/oe/local-recipes/myhelloworld/files/helloworld.c to /home/lenehan/devel/oe/build/titan-glibc-25/tmp/work/myhelloworld-0.1-r0/
+NOTE: Unpacking /home/lenehan/devel/oe/local-recipes/myhelloworld/files/README.txt to /home/lenehan/devel/oe/build/titan-glibc-25/tmp/work/myhelloworld-0.1-r0/
 NOTE: package myhelloworld-0.1-r0: task do_unpack: completed
 NOTE: package myhelloworld-0.1-r0: task do_patch: started
 NOTE: package myhelloworld-0.1-r0: task do_patch: completed
@@ -1354,7 +1354,7 @@ tmp/work/myhelloworld-0.1-r0/install/myhelloworld/usr/bin/myhelloworld: ELF 32-b
       of building an autotools based packages.</para>
 
       <para>Let's take a look at the tuxnes recipe which is an example of a
-      very simple autotools based recipe:<screen>%~oe&gt; cat packages/tuxnes/tuxnes_0.75.bb
+      very simple autotools based recipe:<screen>%~oe&gt; cat recipes/tuxnes/tuxnes_0.75.bb
 DESCRIPTION = "Tuxnes Nintendo (8bit) Emulator"
 HOMEPAGE = "http://prdownloads.sourceforge.net/tuxnes/tuxnes-0.75.tar.gz"
 LICENSE = "GPLv2"
@@ -3366,7 +3366,7 @@ do_configure() {
     via the <command>PV</command> variable).</para>
 
     <para>For example if we were to ask bitbake to build procps and the
-    following packages are available:<screen>~/oe%&gt; ls packages/procps 
+    following packages are available:<screen>~/oe%&gt; ls recipes/procps 
 procps-3.1.15/    procps-3.2.1/    procps-3.2.5/    procps-3.2.7/    procps.inc
 procps_3.1.15.bb  procps_3.2.1.bb  procps_3.2.5.bb  procps_3.2.7.bb
 ~/oe%&gt;</screen>then we would expect it to select version
@@ -3397,7 +3397,7 @@ procps_3.1.15.bb  procps_3.2.1.bb  procps_3.2.5.bb  procps_3.2.7.bb
     version until it works. By adding:<screen>DEFAULT_PREFERENCE = "-1"</screen>to
     the recipe this is what will happen. Bitbake will now ignore this version
     (since all of the existing versions have a preference of 0). Note that you
-    can still call bitbake directly on the recipe:<screen>bitbake -b packages/procps/procps_4.0.0.bb</screen>This
+    can still call bitbake directly on the recipe:<screen>bitbake -b recipes/procps/procps_4.0.0.bb</screen>This
     enables you to test, and fix the package manually without having bitbake
     automatically select normally.</para>
 
@@ -3406,7 +3406,7 @@ procps_3.1.15.bb  procps_3.2.1.bb  procps_3.2.5.bb  procps_3.2.7.bb
     example from glibc shows that this version has been disabled for the sh3
     architecture because it doesn't support sh3. This will force bitbake to
     try and select one of the other available versions of glibc
-    instead:<screen>packages/glibc/glibc_2.3.2+cvs20040726.bb:DEFAULT_PREFERENCE_sh3 = "-99"</screen></para>
+    instead:<screen>recipes/glibc/glibc_2.3.2+cvs20040726.bb:DEFAULT_PREFERENCE_sh3 = "-99"</screen></para>
   </section>
 
   <section id="recipes_initscripts" xreflabel="initscripts">
@@ -3634,7 +3634,7 @@ which find
         <listitem>
           <para>The only directories that you can assume exist are those
           listed in the default volatiles file:
-          <command>packages/initscripts/initscripts-1.0/volatiles</command>.</para>
+          <command>recipes/initscripts/initscripts-1.0/volatiles</command>.</para>
         </listitem>
 
         <listitem>
@@ -3707,4 +3707,4 @@ which find
 
     <para></para>
   </section>
-</chapter>
\ No newline at end of file
+</chapter>
diff --git a/docs/usermanual/chapters/usage.xml b/docs/usermanual/chapters/usage.xml
index 9fe20fa..5dd00d6 100644
--- a/docs/usermanual/chapters/usage.xml
+++ b/docs/usermanual/chapters/usage.xml
@@ -574,51 +574,51 @@ NOTE: Resolving missing task queue dependencies
 NOTE: preferred version 2.5 of glibc not available (for item virtual/sh4-linux-libc-for-gcc)
 NOTE: Preparing Runqueue
 NOTE: Executing runqueue
-NOTE: Running task 208 of 226 (ID: 11, /home/lenehan/devel/oe/build/titan-glibc-25/packages/lzo/lzo_1.08.bb, <emphasis
+NOTE: Running task 208 of 226 (ID: 11, /home/lenehan/devel/oe/build/titan-glibc-25/recipes/lzo/lzo_1.08.bb, <emphasis
           role="bold">do_fetch</emphasis>)
 NOTE: package lzo-1.08: started
 NOTE: package lzo-1.08-r14: task <emphasis role="bold">do_fetch</emphasis>: started
 NOTE: package lzo-1.08-r14: task <emphasis role="bold">do_fetch</emphasis>: completed
 NOTE: package lzo-1.08: completed
-NOTE: Running task 209 of 226 (ID: 2, /home/lenehan/devel/oe/build/titan-glibc-25/packages/lzo/lzo_1.08.bb, <emphasis
+NOTE: Running task 209 of 226 (ID: 2, /home/lenehan/devel/oe/build/titan-glibc-25/recipes/lzo/lzo_1.08.bb, <emphasis
           role="bold">do_unpack</emphasis>)
 NOTE: package lzo-1.08: started
 NOTE: package lzo-1.08-r14: task <emphasis role="bold">do_unpack</emphasis>: started
 NOTE: Unpacking /home/lenehan/devel/oe/sources/lzo-1.08.tar.gz to /home/lenehan/devel/oe/build/titan-glibc-25/tmp/work/lzo-1.08-r14/
 NOTE: package lzo-1.08-r14: task <emphasis role="bold">do_unpack</emphasis>: completed
 NOTE: package lzo-1.08: completed
-NOTE: Running task 216 of 226 (ID: 3, /home/lenehan/devel/oe/build/titan-glibc-25/packages/lzo/lzo_1.08.bb, <emphasis
+NOTE: Running task 216 of 226 (ID: 3, /home/lenehan/devel/oe/build/titan-glibc-25/recipes/lzo/lzo_1.08.bb, <emphasis
           role="bold">do_patch</emphasis>)
 NOTE: package lzo-1.08: started
 NOTE: package lzo-1.08-r14: task <emphasis role="bold">do_patch</emphasis>: started
 NOTE: package lzo-1.08-r14: task <emphasis role="bold">do_patch</emphasis>: completed
 NOTE: package lzo-1.08: completed
-NOTE: Running task 217 of 226 (ID: 4, /home/lenehan/devel/oe/build/titan-glibc-25/packages/lzo/lzo_1.08.bb, <emphasis
+NOTE: Running task 217 of 226 (ID: 4, /home/lenehan/devel/oe/build/titan-glibc-25/recipes/lzo/lzo_1.08.bb, <emphasis
           role="bold">do_configure</emphasis>)
 NOTE: package lzo-1.08: started
 NOTE: package lzo-1.08-r14: task <emphasis role="bold">do_configure</emphasis>: started
 NOTE: package lzo-1.08-r14: task <emphasis role="bold">do_configure</emphasis>: completed
 NOTE: package lzo-1.08: completed
-NOTE: Running task 218 of 226 (ID: 12, /home/lenehan/devel/oe/build/titan-glibc-25/packages/lzo/lzo_1.08.bb, <emphasis
+NOTE: Running task 218 of 226 (ID: 12, /home/lenehan/devel/oe/build/titan-glibc-25/recipes/lzo/lzo_1.08.bb, <emphasis
           role="bold">do_qa_configure</emphasis>)
 NOTE: package lzo-1.08: started
 NOTE: package lzo-1.08-r14: task <emphasis role="bold">do_qa_configure</emphasis>: started
 NOTE: Checking sanity of the config.log file
 NOTE: package lzo-1.08-r14: task <emphasis role="bold">do_qa_configure</emphasis>: completed
 NOTE: package lzo-1.08: completed
-NOTE: Running task 219 of 226 (ID: 0, /home/lenehan/devel/oe/build/titan-glibc-25/packages/lzo/lzo_1.08.bb, <emphasis
+NOTE: Running task 219 of 226 (ID: 0, /home/lenehan/devel/oe/build/titan-glibc-25/recipes/lzo/lzo_1.08.bb, <emphasis
           role="bold">do_compile</emphasis>)
 NOTE: package lzo-1.08: started
 NOTE: package lzo-1.08-r14: task <emphasis role="bold">do_compile</emphasis>: started
 NOTE: package lzo-1.08-r14: task <emphasis role="bold">do_compile</emphasis>: completed
 NOTE: package lzo-1.08: completed
-NOTE: Running task 220 of 226 (ID: 1, /home/lenehan/devel/oe/build/titan-glibc-25/packages/lzo/lzo_1.08.bb, <emphasis
+NOTE: Running task 220 of 226 (ID: 1, /home/lenehan/devel/oe/build/titan-glibc-25/recipes/lzo/lzo_1.08.bb, <emphasis
           role="bold">do_install</emphasis>)
 NOTE: package lzo-1.08: started
 NOTE: package lzo-1.08-r14: task <emphasis role="bold">do_install</emphasis>: started
 NOTE: package lzo-1.08-r14: task <emphasis role="bold">do_install</emphasis>: completed
 NOTE: package lzo-1.08: completed
-NOTE: Running task 221 of 226 (ID: 5, /home/lenehan/devel/oe/build/titan-glibc-25/packages/lzo/lzo_1.08.bb, <emphasis
+NOTE: Running task 221 of 226 (ID: 5, /home/lenehan/devel/oe/build/titan-glibc-25/recipes/lzo/lzo_1.08.bb, <emphasis
           role="bold">do_package</emphasis>)
 NOTE: package lzo-1.08: started
 NOTE: package lzo-1.08-r14: task <emphasis role="bold">do_package</emphasis>: started
@@ -631,7 +631,7 @@ NOTE: Checking Package: lzo-locale
 NOTE: DONE with PACKAGE QA
 NOTE: package lzo-1.08-r14: task <emphasis role="bold">do_package</emphasis>: completed
 NOTE: package lzo-1.08: completed
-NOTE: Running task 222 of 226 (ID: 8, /home/lenehan/devel/oe/build/titan-glibc-25/packages/lzo/lzo_1.08.bb, <emphasis
+NOTE: Running task 222 of 226 (ID: 8, /home/lenehan/devel/oe/build/titan-glibc-25/recipes/lzo/lzo_1.08.bb, <emphasis
           role="bold">do_package_write</emphasis>)
 NOTE: package lzo-1.08: started
 NOTE: package lzo-1.08-r14: task <emphasis role="bold">do_package_write</emphasis>: started
@@ -642,23 +642,23 @@ Packaged contents of lzo-dev into /home/lenehan/devel/oe/build/titan-glibc-25/tm
 NOTE: Not creating empty archive for lzo-locale-1.08-r14
 NOTE: package lzo-1.08-r14: task <emphasis role="bold">do_package_write</emphasis>: completed
 NOTE: package lzo-1.08: completed
-NOTE: Running task 223 of 226 (ID: 6, /home/lenehan/devel/oe/build/titan-glibc-25/packages/lzo/lzo_1.08.bb, do_populate_staging)
+NOTE: Running task 223 of 226 (ID: 6, /home/lenehan/devel/oe/build/titan-glibc-25/recipes/lzo/lzo_1.08.bb, do_populate_staging)
 NOTE: package lzo-1.08: started
 NOTE: package lzo-1.08-r14: task <emphasis role="bold">do_populate_staging</emphasis>: started
 NOTE: package lzo-1.08-r14: task <emphasis role="bold">do_populate_staging</emphasis>: completed
 NOTE: package lzo-1.08: completed
-NOTE: Running task 224 of 226 (ID: 9, /home/lenehan/devel/oe/build/titan-glibc-25/packages/lzo/lzo_1.08.bb, do_qa_staging)
+NOTE: Running task 224 of 226 (ID: 9, /home/lenehan/devel/oe/build/titan-glibc-25/recipes/lzo/lzo_1.08.bb, do_qa_staging)
 NOTE: package lzo-1.08: started
 NOTE: package lzo-1.08-r14: task <emphasis role="bold">do_qa_staging</emphasis>: started
 NOTE: QA checking staging
 NOTE: package lzo-1.08-r14: task <emphasis role="bold">do_qa_staging</emphasis>: completed
 NOTE: package lzo-1.08: completed
-NOTE: Running task 225 of 226 (ID: 7, /home/lenehan/devel/oe/build/titan-glibc-25/packages/lzo/lzo_1.08.bb, do_distribute_sources)
+NOTE: Running task 225 of 226 (ID: 7, /home/lenehan/devel/oe/build/titan-glibc-25/recipes/lzo/lzo_1.08.bb, do_distribute_sources)
 NOTE: package lzo-1.08: started
 NOTE: package lzo-1.08-r14: task <emphasis role="bold">do_distribute_sources</emphasis>: started
 NOTE: package lzo-1.08-r14: task <emphasis role="bold">do_distribute_sources</emphasis>: completed
 NOTE: package lzo-1.08: completed
-NOTE: Running task 226 of 226 (ID: 10, /home/lenehan/devel/oe/build/titan-glibc-25/packages/lzo/lzo_1.08.bb, do_build)
+NOTE: Running task 226 of 226 (ID: 10, /home/lenehan/devel/oe/build/titan-glibc-25/recipes/lzo/lzo_1.08.bb, do_build)
 NOTE: package lzo-1.08: started
 NOTE: package lzo-1.08-r14: task <emphasis role="bold">do_build</emphasis>: started
 NOTE: package lzo-1.08-r14: task <emphasis role="bold">do_build</emphasis>: completed
@@ -827,7 +827,7 @@ NOTE: build 200705041709: completed</screen><note>
 
     <para>To determine the full list of tasks available for a specific recipe
     you can run bitbake on the recipe and asking it for the full list of
-    available tasks:<screen>~%&gt; bitbake -b packages/perl/perl_5.8.8.bb -c listtasks
+    available tasks:<screen>~%&gt; bitbake -b recipes/perl/perl_5.8.8.bb -c listtasks
 NOTE: package perl-5.8.8: started
 NOTE: package perl-5.8.8-r11: task do_listtasks: started
 do_fetchall
@@ -1020,27 +1020,27 @@ NOTE: package perl-5.8.8: completed
 
     <para>A typically development session might involve editing files in the
     working directory and then recompiling until it all works:<screen>[<emphasis>... test ...</emphasis>]
-~%&gt; bitbake -b packages/testapp/testapp_4.3.bb -c compile -D
+~%&gt; bitbake -b recipes/testapp/testapp_4.3.bb -c compile -D
 
 [<emphasis>... save a copy of main.c and make some changes ...</emphasis>]
 ~%&gt; vi tmp/work/testapp-4.3-r0/main.c
-~%&gt; bitbake -b packages/testapp/testapp_4.3.bb -c compile -D -f
+~%&gt; bitbake -b recipes/testapp/testapp_4.3.bb -c compile -D -f
 
 [<emphasis>... create a patch and add it to the recipe ...</emphasis>]
-~%&gt; vi packages/testapp/testapp_4.3.bb
+~%&gt; vi recipes/testapp/testapp_4.3.bb
 
 [<emphasis>... test from clean ...</emphasis>]
-~%&gt; bitbake -b packages/testapp/testapp_4.3.bb -c clean
-~%&gt; bitbake -b packages/testapp/testapp_4.3.bb
+~%&gt; bitbake -b recipes/testapp/testapp_4.3.bb -c clean
+~%&gt; bitbake -b recipes/testapp/testapp_4.3.bb
 
 [<emphasis>... NOTE: How to create the patch is not covered at this point ...</emphasis>]</screen></para>
 
     <para>Here's another example showing how you might go about fixing up the
-    packaging in your recipe:<screen>~%&gt; bitbake -b packages/testapp/testapp_4.3.bb -c install -f
-~%&gt; bitbake -b packages/testapp/testapp_4.3.bb -c stage -f
+    packaging in your recipe:<screen>~%&gt; bitbake -b recipes/testapp/testapp_4.3.bb -c install -f
+~%&gt; bitbake -b recipes/testapp/testapp_4.3.bb -c stage -f
 ~%&gt; find tmp/work/testapp_4.3/install
 ...
-~%&gt; vi packages/testapp/testapp_4.3.bb</screen>At this stage you play with
+~%&gt; vi recipes/testapp/testapp_4.3.bb</screen>At this stage you play with
     the <emphasis role="bold">PACKAGE_</emphasis> and <emphasis
     role="bold">FILES_</emphasis> variables and then repeat the above
     sequence.</para>
@@ -1103,7 +1103,7 @@ BB&gt;&gt; build net-snmp</screen>Note that you can use wildcards in the
             role="bold">devshell</emphasis>"</screen></para>
 
       <para>With the inclusion of this class you'll find that devshell is
-      added as a new task that you can use on recipes:<screen>~%&gt; bitbake -b packages/lzo/lzo_1.08.bb -c listtasks
+      added as a new task that you can use on recipes:<screen>~%&gt; bitbake -b recipes/lzo/lzo_1.08.bb -c listtasks
 NOTE: package lzo-1.08: started
 NOTE: package lzo-1.08-r14: task do_listtasks: started
 <emphasis role="bold">do_devshell</emphasis>
@@ -1130,7 +1130,7 @@ NOTE: package lzo-1.08-r14: task do_listtasks: completed
 NOTE: package lzo-1.08: completed</screen></para>
 
       <para>To bring up the devshell you call bitbake on a recipe and ask it
-      for the devshell task:<screen>~%&gt; ./bb -b packages/lzo/lzo_1.08.bb -c devshell
+      for the devshell task:<screen>~%&gt; ./bb -b recipes/lzo/lzo_1.08.bb -c devshell
 NOTE: package lzo-1.08: started
 NOTE: package lzo-1.08-r14: task do_devshell: started
 [<emphasis>... devshell will appear here ...</emphasis>]
@@ -1190,4 +1190,4 @@ bash: alias: `./configure': invalid alias name
 
     <para>[To be done]</para>
   </section>
-</chapter>
\ No newline at end of file
+</chapter>
-- 
1.5.4.3

Signed-off-by: Theodore A. Roth <taroth@gmail.com>

(No subject)

[Rolf Leggewie]

Am I missing something here?



From 6b2ebec94fbd9c86041df4900d4af744610f9877 Mon Sep 17 00:00:00 2001
From: Rolf Leggewie <oe-devel@rolf.leggewie.biz>
Date: Tue, 9 Jun 2009 11:53:36 +0900
Subject: [PATCH] zaurus-2.6.inc: drop machine specific MACHINE_KERNEL_PR.

Will result in kernel rebuild for tosa and collie.
---
 conf/machine/include/zaurus-kernel.inc |    2 --
 1 files changed, 0 insertions(+), 2 deletions(-)

diff --git a/conf/machine/include/zaurus-kernel.inc b/conf/machine/include/zaurus-kernel.inc
index 2ca00da..0e8fbfa 100644
--- a/conf/machine/include/zaurus-kernel.inc
+++ b/conf/machine/include/zaurus-kernel.inc
@@ -8,8 +8,6 @@ PREFERRED_PROVIDER_virtual/kernel_tosa = "linux"
 
 # Increase PR everytime you change something in the kernel
 MACHINE_KERNEL_PR = "r11"
-MACHINE_KERNEL_PR_collie = "r8"
-MACHINE_KERNEL_PR_tosa = "r4"
 
 MACHINE_KERNEL_PR_pn-linux-kexecboot = "r13"
 
-- 
1.6.0.4

(No subject)

[Rolf Leggewie]

Rolf Leggewie wrote:
> Am I missing something here?

yes ;-)

Still learning how to use git send-email.

(No subject)

[Rolf Leggewie]

please ignore this patch for now.

(No subject)

[Gregory Machairidis]

php.inc have an error on the URI

this is the correct for a working task, us2.php.net dont have that file
anymore...

SRC_URI =     "http://museum.php.net/php5/php-${PV}.tar.bz2\
               file://acinclude-xml2-config.patch;patch=1"


NOTE: Running task 365 of 921 (ID: 525, /stuff/openembedded/recipes/php/
php-native_5.2.6.bb, do_fetch)
NOTE: fetch http://us2.php.net/distributions/php-5.2.6.tar.bz2
--15:31:22--  http://us2.php.net/distributions/php-5.2.6.tar.bz2
Resolving us2.php.net... 64.71.164.5, 2001:470:0:b9::4047:a405
Connecting to us2.php.net|64.71.164.5|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location:
http://us2.php.net/search.php?show=quickref&lang=en&pattern=distributions%2Fphp-5.2.6.tar.bz2[following]
--15:31:23--
http://us2.php.net/search.php?show=quickref&lang=en&pattern=distributions%2Fphp-5.2.6.tar.bz2
Reusing existing connection to us2.php.net:80.
HTTP request sent, awaiting response... 302 Found
Location:
http://us2.php.net/manual-lookup.php?pattern=distributions%2Fphp-5.2.6.tar.bz2&lang=en[following]
--15:31:23--
http://us2.php.net/manual-lookup.php?pattern=distributions%2Fphp-5.2.6.tar.bz2&lang=en
Reusing existing connection to us2.php.net:80.
HTTP request sent, awaiting response... 200 OK
Length: 6310 (6.2K) [text/html]
Saving to:
`/stuff/sources/manual-lookup.php?pattern=distributions%2Fphp-5.2.6.tar.bz2&lang=en'

100%[=====================================================================================================================>]
6,310       26.0K/s   in 0.2s

15:31:24 (26.0 KB/s) -
`/stuff/sources/manual-lookup.php?pattern=distributions%2Fphp-5.2.6.tar.bz2&lang=en'
saved [6310/6310]

NOTE: Task failed: Fetch failed:
http://us2.php.net/distributions/php-5.2.6.tar.bz2
ERROR: TaskFailed event exception, aborting
ERROR: Build of /stuff/openembedded/recipes/php/php-native_5.2.6.bb do_fetch
failed

(No subject)

[saleh usman]

How I can solve this problem? any solution? guidance? tutorial?Plz help me in moving forword.RegardsSaleh >>>>BBFILES = "/oe/org.openembedded.dev/packages/*/*.bb  /oe/ossie_collection/packages/*/*.bb"
This seems wrong

>>>>NOTE: Handling BitBake files: \ (0014/0014) [100 %]
In fact you get just 14 items...

>>Dunno about ossie, but in openembedded we moved from 'packages' to 'recipes'.

>>Regards

>>Andrea
 >>>>I've built console-image without adding the following lines in local.conf

 file and it has been built successfully.Now when I've added these lines it is

giving  error.Attached is local.conf file.

>> >>ANGSTROM_EXTRA_INSTALL = " screen oprofile ossie-fm-from-file "

BBFILES = "/oe/org.openembedded.dev/packages/*/*.bb  /oe/ossie_collection/packages/*/*.bb"

BBFILE_COLLECTIONS = "upstream ossie"

BBFILE_PATTERN_upstream = "^/oe/org.openembedded.dev/packages"

BBFILE_PRIORITY_upstream = "5"

BBFILE_PATTERN_ossie = "^/oe/ossie/packages"

BBFILE_PRIORITY_ossie = "10"

Where oe is directory in which I've placed openembedded.

 Terminal window is showing following error.

[saleh <at> localhost ~]$ bitbake console-image

NOTE: Out of date cache found, rebuilding...

NOTE: Handling BitBake files: \ (0014/0014) [100 %]

NOTE: Parsing finished. 0 cached, 14 parsed, 0 skipped, 0 masked.

 ERROR: Nothing PROVIDES 'console-image' 		 	   		  
_________________________________________________________________
Keep your friends updated—even when you’re not signed in.
http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_5:092010

(No subject)

[majo huber]

Hi@all,

when compiling classpath I get the following error:

jm@pc-jm:~/localcvs/oe/stuff/openembedded$ bitbake classpath -c build
NOTE: Handling BitBake files: \ (8095/8095) [100 %]
NOTE: Parsing finished. 7448 cached, 317 parsed, 330 skipped, 0 masked.
NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing runqueue
NOTE: Running task 1335 of 1946 (ID: 284,
/home/jm/localcvs/oe/stuff/openembedded/recipes/antlr/antlr-native_2.7.7.bb,
do_compile)
ERROR: function do_compile failed
ERROR: log data follows
(/home/jm/oe/tmp/work/i686-linux/antlr-native-2.7.7-r0/temp/log.do_compile.20706)
| Exception in thread "main" java.lang.NoClassDefFoundError:
org/eclipse/jdt/internal/compiler/batch/Main
|    <<No stacktrace available>>
| Caused by: java.lang.ClassNotFoundException:
org.eclipse.jdt.internal.compiler.batch.Main not found in
java.lang.ClassLoader$1{urls=[], parent=null}
|    at java.net.URLClassLoader.findClass(URLClassLoader.java:529)
|    at java.lang.ClassLoader.loadClass(ClassLoader.java:341)
|    at java.lang.ClassLoader$1.loadClass(ClassLoader.java:1112)
|    at java.lang.ClassLoader.loadClass(ClassLoader.java:293)
NOTE: Task failed:
/home/jm/oe/tmp/work/i686-linux/antlr-native-2.7.7-r0/temp/log.do_compile.20706
ERROR: TaskFailed event exception, aborting
ERROR: Build of
/home/jm/localcvs/oe/stuff/openembedded/recipes/antlr/antlr-native_2.7.7.bb
do_compile failed
ERROR: Task 284
(/home/jm/localcvs/oe/stuff/openembedded/recipes/antlr/antlr-native_2.7.7.bb,
do_compile) failed
NOTE: Tasks Summary: Attempted 1334 tasks of which 1334 didn't need to
be rerun and 1 failed.
ERROR: '/home/jm/localcvs/oe/stuff/openembedded/recipes/antlr/antlr-native_2.7.7.bb'
failed


Has anybody an idea how to resolve this issue?
I saw that the classpath has recently changed from 0.97 to 0.98
(according to git). And I'm pretty sure that I compiled this earlier
and had no problems. I'm no Java guy, so I don't really know where to
start. Is it possible that it has someting to do with the Host
platform (Ubuntu 9.10)?

Thanks in advance,
majo

(No subject)

[Soumya R]

Hi All,

   I am running bibake micro-image i got the following error,

NOTE: Running task 965 of 970 (ID: 93, /home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/mtd/mtd-utils-native_1.3.1.bb, do_package_write)
NOTE: Running task 966 of 970 (ID: 18, /home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/images/micro-image.bb, do_package_update_index_ipk)
ERROR: function do_package_update_index_ipk failed
ERROR: log data follows (/home/likewise-open/KPIT/soumyar/oe/build/tmp/work/at91sam9263ek-angstrom-linux-gnueabi/micro-image-1.0-r0/temp/log.do_package_update_index_ipk.24831)
| + ipkgarchs='all any noarch arm  armv4 armv4t armv5te at91sam9263ek'
| + '[' '!' -z '' ']'
| + mkdir -p /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk
| + touch /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/Packages
| + ipkg-make-index -r /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/Packages -p /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/Packages -l /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/Packages.filelist -m /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk
| /home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/ipkg.py:39: DeprecationWarning: the md5 module is deprecated; use hashlib instead
|   import md5
| 
| + for arch in '$ipkgarchs'
| + '[' -e /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/ ']'
| + touch /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/Packages
| + ipkg-make-index -r /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/Packages -p /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/Packages -l /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/Packages.filelist -m /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/
| /home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/ipkg.py:39: DeprecationWarning: the md5 module is deprecated; use hashlib instead
|   import md5
| Traceback (most recent call last):
|   File "/home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/ipkg-make-index", line 114, in <module>
|     pkg = ipkg.Package(filename)
|   File "/home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/ipkg.py", line 161, in __init__
|     tarStream = ar.open("control.tar.gz")
|   File "/home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/arfile.py", line 59, in open
|     f = self._scan(fname)
|   File "/home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/arfile.py", line 79, in _scan
|     size = int(descriptor[5])
| IndexError: list index out of range
NOTE: Task failed: /home/likewise-open/KPIT/soumyar/oe/build/tmp/work/at91sam9263ek-angstrom-linux-gnueabi/micro-image-1.0-r0/temp/log.do_package_update_index_ipk.24831
ERROR: TaskFailed event exception, aborting
ERROR: Build of /home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/images/micro-image.bb do_package_update_index_ipk failed
NOTE: Running task 967 of 970 (ID: 95, /home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/mtd/mtd-utils-native_1.3.1.bb, do_package_stage)
ERROR: Task 18 (/home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/images/micro-image.bb, do_package_update_index_ipk) failed
NOTE: Waiting for 1 active tasks to finish
NOTE: 1: /home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/mtd/mtd-utils-native_1.3.1.bb, do_package_stage (24841)
NOTE: Tasks Summary: Attempted 965 tasks of which 927 didn't need to be rerun and 1 failed.
ERROR: '/home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/images/micro-image.bb' failed
KPIT\soumyar@d-5289lnx:~/oe/build$ 

   Anybody can help me out to resolve this.Any suggestions are welcome:-)

Thanks in advance:-)

Regards,
Soumya

(No subject)

[Hodgson, Simon]

Let me guess, you're using Ubuntu 10.4 to build?

Edit the file:
home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/arfile.py

Change the line:
size = int(descriptor[5])

To:
size = int(descriptor[3])

I'm afraid I can't explain why you need to do this, only that it works for me.

Simon

-----Original Message-----
From: openembedded-devel-bounces@lists.openembedded.org [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of Soumya R
Sent: 02 June 2010 10:20
To: openembedded-devel@lists.openembedded.org
Cc: angstrom-distro-devel@linuxtogo.org
Subject: [oe] (no subject)

Hi All,

   I am running bibake micro-image i got the following error,

NOTE: Running task 965 of 970 (ID: 93, /home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/mtd/mtd-utils-native_1.3.1.bb, do_package_write)
NOTE: Running task 966 of 970 (ID: 18, /home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/images/micro-image.bb, do_package_update_index_ipk)
ERROR: function do_package_update_index_ipk failed
ERROR: log data follows (/home/likewise-open/KPIT/soumyar/oe/build/tmp/work/at91sam9263ek-angstrom-linux-gnueabi/micro-image-1.0-r0/temp/log.do_package_update_index_ipk.24831)
| + ipkgarchs='all any noarch arm  armv4 armv4t armv5te at91sam9263ek'
| + '[' '!' -z '' ']'
| + mkdir -p /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk
| + touch /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/Packages
| + ipkg-make-index -r /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/Packages -p /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/Packages -l /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/Packages.filelist -m /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk
| /home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/ipkg.py:39: DeprecationWarning: the md5 module is deprecated; use hashlib instead
|   import md5
| 
| + for arch in '$ipkgarchs'
| + '[' -e /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/ ']'
| + touch /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/Packages
| + ipkg-make-index -r /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/Packages -p /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/Packages -l /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/Packages.filelist -m /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/
| /home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/ipkg.py:39: DeprecationWarning: the md5 module is deprecated; use hashlib instead
|   import md5
| Traceback (most recent call last):
|   File "/home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/ipkg-make-index", line 114, in <module>
|     pkg = ipkg.Package(filename)
|   File "/home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/ipkg.py", line 161, in __init__
|     tarStream = ar.open("control.tar.gz")
|   File "/home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/arfile.py", line 59, in open
|     f = self._scan(fname)
|   File "/home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/arfile.py", line 79, in _scan
|     size = int(descriptor[5])
| IndexError: list index out of range
NOTE: Task failed: /home/likewise-open/KPIT/soumyar/oe/build/tmp/work/at91sam9263ek-angstrom-linux-gnueabi/micro-image-1.0-r0/temp/log.do_package_update_index_ipk.24831
ERROR: TaskFailed event exception, aborting
ERROR: Build of /home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/images/micro-image.bb do_package_update_index_ipk failed
NOTE: Running task 967 of 970 (ID: 95, /home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/mtd/mtd-utils-native_1.3.1.bb, do_package_stage)
ERROR: Task 18 (/home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/images/micro-image.bb, do_package_update_index_ipk) failed
NOTE: Waiting for 1 active tasks to finish
NOTE: 1: /home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/mtd/mtd-utils-native_1.3.1.bb, do_package_stage (24841)
NOTE: Tasks Summary: Attempted 965 tasks of which 927 didn't need to be rerun and 1 failed.
ERROR: '/home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/images/micro-image.bb' failed
KPIT\soumyar@d-5289lnx:~/oe/build$ 

   Anybody can help me out to resolve this.Any suggestions are welcome:-)

Thanks in advance:-)

Regards,
Soumya


_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

(No subject)

[Soumya R]

Ya you are right i am using Ubuntu 10.4..
Thanks a lot for the reply it worked..

Thank you so much:-)

Regards,
Soumya
________________________________________
From: openembedded-devel-bounces@lists.openembedded.org [openembedded-devel-bounces@lists.openembedded.org] On Behalf Of Hodgson, Simon [Simon.Hodgson@nortechonline.co.uk]
Sent: Wednesday, June 02, 2010 9:11 PM
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] (no subject)

Let me guess, you're using Ubuntu 10.4 to build?

Edit the file:
home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/arfile.py

Change the line:
size = int(descriptor[5])

To:
size = int(descriptor[3])

I'm afraid I can't explain why you need to do this, only that it works for me.

Simon

-----Original Message-----
From: openembedded-devel-bounces@lists.openembedded.org [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of Soumya R
Sent: 02 June 2010 10:20
To: openembedded-devel@lists.openembedded.org
Cc: angstrom-distro-devel@linuxtogo.org
Subject: [oe] (no subject)

Hi All,

   I am running bibake micro-image i got the following error,

NOTE: Running task 965 of 970 (ID: 93, /home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/mtd/mtd-utils-native_1.3.1.bb, do_package_write)
NOTE: Running task 966 of 970 (ID: 18, /home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/images/micro-image.bb, do_package_update_index_ipk)
ERROR: function do_package_update_index_ipk failed
ERROR: log data follows (/home/likewise-open/KPIT/soumyar/oe/build/tmp/work/at91sam9263ek-angstrom-linux-gnueabi/micro-image-1.0-r0/temp/log.do_package_update_index_ipk.24831)
| + ipkgarchs='all any noarch arm  armv4 armv4t armv5te at91sam9263ek'
| + '[' '!' -z '' ']'
| + mkdir -p /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk
| + touch /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/Packages
| + ipkg-make-index -r /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/Packages -p /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/Packages -l /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/Packages.filelist -m /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk
| /home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/ipkg.py:39: DeprecationWarning: the md5 module is deprecated; use hashlib instead
|   import md5
|
| + for arch in '$ipkgarchs'
| + '[' -e /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/ ']'
| + touch /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/Packages
| + ipkg-make-index -r /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/Packages -p /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/Packages -l /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/Packages.filelist -m /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/
| /home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/ipkg.py:39: DeprecationWarning: the md5 module is deprecated; use hashlib instead
|   import md5
| Traceback (most recent call last):
|   File "/home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/ipkg-make-index", line 114, in <module>
|     pkg = ipkg.Package(filename)
|   File "/home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/ipkg.py", line 161, in __init__
|     tarStream = ar.open("control.tar.gz")
|   File "/home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/arfile.py", line 59, in open
|     f = self._scan(fname)
|   File "/home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/arfile.py", line 79, in _scan
|     size = int(descriptor[5])
| IndexError: list index out of range
NOTE: Task failed: /home/likewise-open/KPIT/soumyar/oe/build/tmp/work/at91sam9263ek-angstrom-linux-gnueabi/micro-image-1.0-r0/temp/log.do_package_update_index_ipk.24831
ERROR: TaskFailed event exception, aborting
ERROR: Build of /home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/images/micro-image.bb do_package_update_index_ipk failed
NOTE: Running task 967 of 970 (ID: 95, /home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/mtd/mtd-utils-native_1.3.1.bb, do_package_stage)
ERROR: Task 18 (/home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/images/micro-image.bb, do_package_update_index_ipk) failed
NOTE: Waiting for 1 active tasks to finish
NOTE: 1: /home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/mtd/mtd-utils-native_1.3.1.bb, do_package_stage (24841)
NOTE: Tasks Summary: Attempted 965 tasks of which 927 didn't need to be rerun and 1 failed.
ERROR: '/home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/images/micro-image.bb' failed
KPIT\soumyar@d-5289lnx:~/oe/build$

   Anybody can help me out to resolve this.Any suggestions are welcome:-)

Thanks in advance:-)

Regards,
Soumya


_______________________________________________
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

(No subject)

[Khem Raj]

On Wed, Jun 2, 2010 at 7:37 PM, Soumya R <Soumya.R@kpitcummins.com> wrote:
> Ya you are right i am using Ubuntu 10.4..
> Thanks a lot for the reply it worked..
>
> Thank you so much:-)

are you using .dev ?. I don't see this issue here locally on ubuntu
10.04. whats your distro
and machine.it could be issue in ipkg-utils-native

Thx
-Khem

> home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/arfile.py
>
> Change the line:
> size = int(descriptor[5])
>
> To:
> size = int(descriptor[3])
>
> I'm afraid I can't explain why you need to do this, only that it works for me.
>
> Simon
>
> -----Original Message-----
> From: openembedded-devel-bounces@lists.openembedded.org [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of Soumya R
> Sent: 02 June 2010 10:20
> To: openembedded-devel@lists.openembedded.org
> Cc: angstrom-distro-devel@linuxtogo.org
> Subject: [oe] (no subject)
>
> Hi All,
>
>   I am running bibake micro-image i got the following error,
>
> NOTE: Running task 965 of 970 (ID: 93, /home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/mtd/mtd-utils-native_1.3.1.bb, do_package_write)
> NOTE: Running task 966 of 970 (ID: 18, /home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/images/micro-image.bb, do_package_update_index_ipk)
> ERROR: function do_package_update_index_ipk failed
> ERROR: log data follows (/home/likewise-open/KPIT/soumyar/oe/build/tmp/work/at91sam9263ek-angstrom-linux-gnueabi/micro-image-1.0-r0/temp/log.do_package_update_index_ipk.24831)
> | + ipkgarchs='all any noarch arm  armv4 armv4t armv5te at91sam9263ek'
> | + '[' '!' -z '' ']'
> | + mkdir -p /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk
> | + touch /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/Packages
> | + ipkg-make-index -r /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/Packages -p /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/Packages -l /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/Packages.filelist -m /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk
> | /home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/ipkg.py:39: DeprecationWarning: the md5 module is deprecated; use hashlib instead
> |   import md5
> |
> | + for arch in '$ipkgarchs'
> | + '[' -e /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/ ']'
> | + touch /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/Packages
> | + ipkg-make-index -r /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/Packages -p /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/Packages -l /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/Packages.filelist -m /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/
> | /home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/ipkg.py:39: DeprecationWarning: the md5 module is deprecated; use hashlib instead
> |   import md5
> | Traceback (most recent call last):
> |   File "/home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/ipkg-make-index", line 114, in <module>
> |     pkg = ipkg.Package(filename)
> |   File "/home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/ipkg.py", line 161, in __init__
> |     tarStream = ar.open("control.tar.gz")
> |   File "/home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/arfile.py", line 59, in open
> |     f = self._scan(fname)
> |   File "/home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/arfile.py", line 79, in _scan
> |     size = int(descriptor[5])
> | IndexError: list index out of range
> NOTE: Task failed: /home/likewise-open/KPIT/soumyar/oe/build/tmp/work/at91sam9263ek-angstrom-linux-gnueabi/micro-image-1.0-r0/temp/log.do_package_update_index_ipk.24831
> ERROR: TaskFailed event exception, aborting
> ERROR: Build of /home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/images/micro-image.bb do_package_update_index_ipk failed
> NOTE: Running task 967 of 970 (ID: 95, /home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/mtd/mtd-utils-native_1.3.1.bb, do_package_stage)
> ERROR: Task 18 (/home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/images/micro-image.bb, do_package_update_index_ipk) failed
> NOTE: Waiting for 1 active tasks to finish
> NOTE: 1: /home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/mtd/mtd-utils-native_1.3.1.bb, do_package_stage (24841)
> NOTE: Tasks Summary: Attempted 965 tasks of which 927 didn't need to be rerun and 1 failed.
> ERROR: '/home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/images/micro-image.bb' failed
> KPIT\soumyar@d-5289lnx:~/oe/build$
>
>   Anybody can help me out to resolve this.Any suggestions are welcome:-)
>
> Thanks in advance:-)
>
> Regards,
> Soumya
>
>
> _______________________________________________
> 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
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

(No subject)

[Hodgson, Simon]

I'm using Angstrom, and at91sam9g20-ek, on two machines with new installs of Ubuntu 10.4 we see this problem, on another that was upgraded from 9.10 we don't see it.

-----Original Message-----
From: openembedded-devel-bounces@lists.openembedded.org [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of Khem Raj
Sent: 03 June 2010 06:11
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] (no subject)

On Wed, Jun 2, 2010 at 7:37 PM, Soumya R <Soumya.R@kpitcummins.com> wrote:
> Ya you are right i am using Ubuntu 10.4..
> Thanks a lot for the reply it worked..
>
> Thank you so much:-)

are you using .dev ?. I don't see this issue here locally on ubuntu
10.04. whats your distro
and machine.it could be issue in ipkg-utils-native

Thx
-Khem

> home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/arfile.py
>
> Change the line:
> size = int(descriptor[5])
>
> To:
> size = int(descriptor[3])
>
> I'm afraid I can't explain why you need to do this, only that it works for me.
>
> Simon
>
> -----Original Message-----
> From: openembedded-devel-bounces@lists.openembedded.org [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of Soumya R
> Sent: 02 June 2010 10:20
> To: openembedded-devel@lists.openembedded.org
> Cc: angstrom-distro-devel@linuxtogo.org
> Subject: [oe] (no subject)
>
> Hi All,
>
>   I am running bibake micro-image i got the following error,
>
> NOTE: Running task 965 of 970 (ID: 93, /home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/mtd/mtd-utils-native_1.3.1.bb, do_package_write)
> NOTE: Running task 966 of 970 (ID: 18, /home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/images/micro-image.bb, do_package_update_index_ipk)
> ERROR: function do_package_update_index_ipk failed
> ERROR: log data follows (/home/likewise-open/KPIT/soumyar/oe/build/tmp/work/at91sam9263ek-angstrom-linux-gnueabi/micro-image-1.0-r0/temp/log.do_package_update_index_ipk.24831)
> | + ipkgarchs='all any noarch arm  armv4 armv4t armv5te at91sam9263ek'
> | + '[' '!' -z '' ']'
> | + mkdir -p /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk
> | + touch /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/Packages
> | + ipkg-make-index -r /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/Packages -p /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/Packages -l /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/Packages.filelist -m /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk
> | /home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/ipkg.py:39: DeprecationWarning: the md5 module is deprecated; use hashlib instead
> |   import md5
> |
> | + for arch in '$ipkgarchs'
> | + '[' -e /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/ ']'
> | + touch /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/Packages
> | + ipkg-make-index -r /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/Packages -p /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/Packages -l /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/Packages.filelist -m /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/
> | /home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/ipkg.py:39: DeprecationWarning: the md5 module is deprecated; use hashlib instead
> |   import md5
> | Traceback (most recent call last):
> |   File "/home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/ipkg-make-index", line 114, in <module>
> |     pkg = ipkg.Package(filename)
> |   File "/home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/ipkg.py", line 161, in __init__
> |     tarStream = ar.open("control.tar.gz")
> |   File "/home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/arfile.py", line 59, in open
> |     f = self._scan(fname)
> |   File "/home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/arfile.py", line 79, in _scan
> |     size = int(descriptor[5])
> | IndexError: list index out of range
> NOTE: Task failed: /home/likewise-open/KPIT/soumyar/oe/build/tmp/work/at91sam9263ek-angstrom-linux-gnueabi/micro-image-1.0-r0/temp/log.do_package_update_index_ipk.24831
> ERROR: TaskFailed event exception, aborting
> ERROR: Build of /home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/images/micro-image.bb do_package_update_index_ipk failed
> NOTE: Running task 967 of 970 (ID: 95, /home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/mtd/mtd-utils-native_1.3.1.bb, do_package_stage)
> ERROR: Task 18 (/home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/images/micro-image.bb, do_package_update_index_ipk) failed
> NOTE: Waiting for 1 active tasks to finish
> NOTE: 1: /home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/mtd/mtd-utils-native_1.3.1.bb, do_package_stage (24841)
> NOTE: Tasks Summary: Attempted 965 tasks of which 927 didn't need to be rerun and 1 failed.
> ERROR: '/home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/images/micro-image.bb' failed
> KPIT\soumyar@d-5289lnx:~/oe/build$
>
>   Anybody can help me out to resolve this.Any suggestions are welcome:-)
>
> Thanks in advance:-)
>
> Regards,
> Soumya
>
>
> _______________________________________________
> 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
>
>
>
> _______________________________________________
> 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

(No subject)

[Soumya R]

Hi,
    
MACHINE = "at91sam9263ek"
DISTRO = "angstrom-2008.1"
    
  I am new to this open embedded so you may seem may question is silly..
I need to know wat i need to deploy to my target and where the final image is stored..
Please help me out.. Thanks in advance :-)

Regards,
Soumya
________________________________________
From: openembedded-devel-bounces@lists.openembedded.org [openembedded-devel-bounces@lists.openembedded.org] On Behalf Of Khem Raj [raj.khem@gmail.com]
Sent: Thursday, June 03, 2010 10:40 AM
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] (no subject)

On Wed, Jun 2, 2010 at 7:37 PM, Soumya R <Soumya.R@kpitcummins.com> wrote:
> Ya you are right i am using Ubuntu 10.4..
> Thanks a lot for the reply it worked..
>
> Thank you so much:-)

are you using .dev ?. I don't see this issue here locally on ubuntu
10.04. whats your distro
and machine.it could be issue in ipkg-utils-native

Thx
-Khem

> home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/arfile.py
>
> Change the line:
> size = int(descriptor[5])
>
> To:
> size = int(descriptor[3])
>
> I'm afraid I can't explain why you need to do this, only that it works for me.
>
> Simon
>
> -----Original Message-----
> From: openembedded-devel-bounces@lists.openembedded.org [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of Soumya R
> Sent: 02 June 2010 10:20
> To: openembedded-devel@lists.openembedded.org
> Cc: angstrom-distro-devel@linuxtogo.org
> Subject: [oe] (no subject)
>
> Hi All,
>
>   I am running bibake micro-image i got the following error,
>
> NOTE: Running task 965 of 970 (ID: 93, /home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/mtd/mtd-utils-native_1.3.1.bb, do_package_write)
> NOTE: Running task 966 of 970 (ID: 18, /home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/images/micro-image.bb, do_package_update_index_ipk)
> ERROR: function do_package_update_index_ipk failed
> ERROR: log data follows (/home/likewise-open/KPIT/soumyar/oe/build/tmp/work/at91sam9263ek-angstrom-linux-gnueabi/micro-image-1.0-r0/temp/log.do_package_update_index_ipk.24831)
> | + ipkgarchs='all any noarch arm  armv4 armv4t armv5te at91sam9263ek'
> | + '[' '!' -z '' ']'
> | + mkdir -p /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk
> | + touch /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/Packages
> | + ipkg-make-index -r /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/Packages -p /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/Packages -l /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/Packages.filelist -m /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk
> | /home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/ipkg.py:39: DeprecationWarning: the md5 module is deprecated; use hashlib instead
> |   import md5
> |
> | + for arch in '$ipkgarchs'
> | + '[' -e /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/ ']'
> | + touch /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/Packages
> | + ipkg-make-index -r /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/Packages -p /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/Packages -l /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/Packages.filelist -m /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/
> | /home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/ipkg.py:39: DeprecationWarning: the md5 module is deprecated; use hashlib instead
> |   import md5
> | Traceback (most recent call last):
> |   File "/home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/ipkg-make-index", line 114, in <module>
> |     pkg = ipkg.Package(filename)
> |   File "/home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/ipkg.py", line 161, in __init__
> |     tarStream = ar.open("control.tar.gz")
> |   File "/home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/arfile.py", line 59, in open
> |     f = self._scan(fname)
> |   File "/home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/arfile.py", line 79, in _scan
> |     size = int(descriptor[5])
> | IndexError: list index out of range
> NOTE: Task failed: /home/likewise-open/KPIT/soumyar/oe/build/tmp/work/at91sam9263ek-angstrom-linux-gnueabi/micro-image-1.0-r0/temp/log.do_package_update_index_ipk.24831
> ERROR: TaskFailed event exception, aborting
> ERROR: Build of /home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/images/micro-image.bb do_package_update_index_ipk failed
> NOTE: Running task 967 of 970 (ID: 95, /home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/mtd/mtd-utils-native_1.3.1.bb, do_package_stage)
> ERROR: Task 18 (/home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/images/micro-image.bb, do_package_update_index_ipk) failed
> NOTE: Waiting for 1 active tasks to finish
> NOTE: 1: /home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/mtd/mtd-utils-native_1.3.1.bb, do_package_stage (24841)
> NOTE: Tasks Summary: Attempted 965 tasks of which 927 didn't need to be rerun and 1 failed.
> ERROR: '/home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/images/micro-image.bb' failed
> KPIT\soumyar@d-5289lnx:~/oe/build$
>
>   Anybody can help me out to resolve this.Any suggestions are welcome:-)
>
> Thanks in advance:-)
>
> Regards,
> Soumya
>
>
> _______________________________________________
> 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
>
>
>
> _______________________________________________
> 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

(No subject)

[Nicolas Ferre]

Le 03/06/2010 14:13, Soumya R :
> Hi,
>     
> MACHINE = "at91sam9263ek"
> DISTRO = "angstrom-2008.1"
>     
>   I am new to this open embedded so you may seem may question is silly..
> I need to know wat i need to deploy to my target and where the final image is stored..
> Please help me out.. Thanks in advance :-)

I advice you to go on
http://www.linux4sam.org
and follow the documentation there. You will have an example of the
deployment of such a distribution.

In an OE build, here are the resulting images:
tmp/deploy/glibc/images/at91sam9263ek/

- Linux kernel (as a uImage suitable for u-boot):
  uImage-2.6.30-r1-at91sam9263ek.bin
- Angstrom rootfs:

Angstrom-x11-at91sam9-image-glibc-ipk-2009.X-stable-at91sam9263ek.rootfs.jffs2

For micro-image, you will find a different name but at the same location.

IPK packages are located here:
tmp/deploy/glibc/ipk/

Hope that it helps,
-- 
Nicolas Ferre

(No subject)

[Soumya R]

Hi All,
      
     I get the following error when I run bitbake avn-image

NOTE: Handling BitBake files: \ (0172/0172) [100 %]
NOTE: Parsing finished. 163 cached, 7 parsed, 2 skipped, 0 masked.
NOTE: Resolving any missing task queue dependencies
ERROR: '['/home/likewise-open/KPIT/soumyar/openembedded/recipes/glibc/glibc_2.10.1.bb']' RDEPENDS/RRECOMMENDS or otherwise requires the runtime entity 'linux-libc-headers-dev' but it wasn't found in any PACKAGE or RPROVIDES variables
NOTE: Runtime target 'linux-libc-headers-dev' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['linux-libc-headers-dev']
ERROR: Required build target 'avn-image' has no buildable providers.
Missing or unbuildable dependency chain was: ['avn-image', 'opkg-native', 'gnu-config-native']

               How do I resolve this error?? Any suggestions is badly needed..

Thanks in advance

Regards,
Soumya

(No subject)

[Khem Raj]

On Tue, Jun 8, 2010 at 1:22 AM, Soumya R <Soumya.R@kpitcummins.com> wrote:
> Hi All,
>
>     I get the following error when I run bitbake avn-image
>
> NOTE: Handling BitBake files: \ (0172/0172) [100 %]
> NOTE: Parsing finished. 163 cached, 7 parsed, 2 skipped, 0 masked.
> NOTE: Resolving any missing task queue dependencies
> ERROR: '['/home/likewise-open/KPIT/soumyar/openembedded/recipes/glibc/glibc_2.10.1.bb']' RDEPENDS/RRECOMMENDS or otherwise requires the runtime entity 'linux-libc-headers-dev' but it wasn't found in any PACKAGE or RPROVIDES variables
> NOTE: Runtime target 'linux-libc-headers-dev' is unbuildable, removing...
> Missing or unbuildable dependency chain was: ['linux-libc-headers-dev']
> ERROR: Required build target 'avn-image' has no buildable providers.
> Missing or unbuildable dependency chain was: ['avn-image', 'opkg-native', 'gnu-config-native']
>
>               How do I resolve this error?? Any suggestions is badly needed..

post you local.conf somewhere. and take time to add some subject to the mail
many people have filters to send subjectless emails to /dev/null

>
> Thanks in advance
>
> Regards,
> Soumya
>
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

(No subject)

[Soumya R]

Hi All,
 
     I am using ubuntu 10.4 LTS and i am trying to build my own customized image
for mipsel.. When i run bitbake avn-image i get the following error.

cp: cannot stat `/home/likewise-open/KPIT/soumyar/openembedded/recipes/python/python-native-2.6.4/05-enable-ctypes-cross-build.patch': No such file or directory
NOTE: Task failed: 
ERROR: TaskFailed event exception, aborting
ERROR: Build of /home/likewise-open/KPIT/soumyar/openembedded/recipes/python/python-native_2.6.4.bb do_unpack failed
ERROR: Task 749 (/home/likewise-open/KPIT/soumyar/openembedded/recipes/python/python-native_2.6.4.bb, do_unpack) failed
NOTE: Waiting for 3 active tasks to finish

  I am unable to tar Python-2.6.4.tar.bz2 by using the command 
tar -zxvf Python-2.6.4.tar.bz2
gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Exiting with failure status due to previous errors
  
   so i downgraded the gzip but still the same error.. If anybody got the same error and resolved it please help me out.. I am stuck here:-(


Thanks in advance :-)

Regards,
Soumya



  

(No subject)

[Frans Meulenbroeks]

2010/6/10 Soumya R <Soumya.R@kpitcummins.com>:
> Hi All,

Hi,

I think it was already told to you that it is better to use a subject line.
More chance of getting a response.

>
>     I am using ubuntu 10.4 LTS and i am trying to build my own customized image
> for mipsel.. When i run bitbake avn-image i get the following error.
>
> cp: cannot stat `/home/likewise-open/KPIT/soumyar/openembedded/recipes/python/python-native-2.6.4/05-enable-ctypes-cross-build.patch': No such file or directory
> NOTE: Task failed:
> ERROR: TaskFailed event exception, aborting
> ERROR: Build of /home/likewise-open/KPIT/soumyar/openembedded/recipes/python/python-native_2.6.4.bb do_unpack failed
> ERROR: Task 749 (/home/likewise-open/KPIT/soumyar/openembedded/recipes/python/python-native_2.6.4.bb, do_unpack) failed
> NOTE: Waiting for 3 active tasks to finish
>
>  I am unable to tar Python-2.6.4.tar.bz2 by using the command
> tar -zxvf Python-2.6.4.tar.bz2
> gzip: stdin: not in gzip format
> tar: Child returned status 1
> tar: Exiting with failure status due to previous errors
>
>   so i downgraded the gzip but still the same error.. If anybody got the same error and resolved it please help me out.. I am stuck here:-(

Read.
It tells the file is not in gzip format.
The file has .bz2 extension so it is probably a bzip2
tar -z decompresses with gzip, tar -j juses bunzip2

And if you have a decent tar you can just omit it and it will find out by itself

Frans.
>
>
> Thanks in advance :-)
>
> Regards,
> Soumya
>
>
>
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

(No subject)

["Andreas Müller"]

-- 
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

(No subject)

[Soumya R]

Hi All,

      I need to include root file system in my uImage how can i
do that in OpenEmbedded.

Regards,
Soumya

(No subject)

[Khem Raj]

On Thu, Jul 1, 2010 at 3:19 AM, Soumya R <Soumya.R@kpitcummins.com> wrote:
> Hi All,
>
>      I need to include root file system in my uImage how can i
> do that in OpenEmbedded.

look into initramfs.
Dont you think adding subject to email makes sense.?

>
> Regards,
> Soumya
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

(No subject)

[Soumya R]

Thanks for the reply.. Yes ofcourse i forgot it will not repeat again sorry..

Regards,
Soumya
________________________________________
From: openembedded-devel-bounces@lists.openembedded.org [openembedded-devel-bounces@lists.openembedded.org] On Behalf Of Khem Raj [raj.khem@gmail.com]
Sent: Friday, July 02, 2010 12:34 AM
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] (no subject)

On Thu, Jul 1, 2010 at 3:19 AM, Soumya R <Soumya.R@kpitcummins.com> wrote:
> Hi All,
>
>      I need to include root file system in my uImage how can i
> do that in OpenEmbedded.

look into initramfs.
Dont you think adding subject to email makes sense.?

>
> Regards,
> Soumya
>
>
>
> _______________________________________________
> 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

(No subject)

[Soumya R]

(No subject)

[Nick Lee]

It turned out to be a likewise-open issue (for us at least) - if we log 
in as a normal user (i.e. not through likewise-open), the build works 
fine.  If we log in using likewise-open, the python file needs to be 
patched as described, but this then breaks the build for normal logins! 
  Our solution was to just not use likewise-open.

Nick

On 03/06/10 09:24, Hodgson, Simon wrote:
> I'm using Angstrom, and at91sam9g20-ek, on two machines with new installs of Ubuntu 10.4 we see this problem, on another that was upgraded from 9.10 we don't see it.
>
> -----Original Message-----
> From: openembedded-devel-bounces@lists.openembedded.org [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of Khem Raj
> Sent: 03 June 2010 06:11
> To: openembedded-devel@lists.openembedded.org
> Subject: Re: [oe] (no subject)
>
> On Wed, Jun 2, 2010 at 7:37 PM, Soumya R<Soumya.R@kpitcummins.com>  wrote:
>> Ya you are right i am using Ubuntu 10.4..
>> Thanks a lot for the reply it worked..
>>
>> Thank you so much:-)
>
> are you using .dev ?. I don't see this issue here locally on ubuntu
> 10.04. whats your distro
> and machine.it could be issue in ipkg-utils-native
>
> Thx
> -Khem
>
>> home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/arfile.py
>>
>> Change the line:
>> size = int(descriptor[5])
>>
>> To:
>> size = int(descriptor[3])
>>
>> I'm afraid I can't explain why you need to do this, only that it works for me.
>>
>> Simon
>>
>> -----Original Message-----
>> From: openembedded-devel-bounces@lists.openembedded.org [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of Soumya R
>> Sent: 02 June 2010 10:20
>> To: openembedded-devel@lists.openembedded.org
>> Cc: angstrom-distro-devel@linuxtogo.org
>> Subject: [oe] (no subject)
>>
>> Hi All,
>>
>>    I am running bibake micro-image i got the following error,
>>
>> NOTE: Running task 965 of 970 (ID: 93, /home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/mtd/mtd-utils-native_1.3.1.bb, do_package_write)
>> NOTE: Running task 966 of 970 (ID: 18, /home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/images/micro-image.bb, do_package_update_index_ipk)
>> ERROR: function do_package_update_index_ipk failed
>> ERROR: log data follows (/home/likewise-open/KPIT/soumyar/oe/build/tmp/work/at91sam9263ek-angstrom-linux-gnueabi/micro-image-1.0-r0/temp/log.do_package_update_index_ipk.24831)
>> | + ipkgarchs='all any noarch arm  armv4 armv4t armv5te at91sam9263ek'
>> | + '[' '!' -z '' ']'
>> | + mkdir -p /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk
>> | + touch /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/Packages
>> | + ipkg-make-index -r /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/Packages -p /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/Packages -l /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/Packages.filelist -m /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk
>> | /home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/ipkg.py:39: DeprecationWarning: the md5 module is deprecated; use hashlib instead
>> |   import md5
>> |
>> | + for arch in '$ipkgarchs'
>> | + '[' -e /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/ ']'
>> | + touch /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/Packages
>> | + ipkg-make-index -r /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/Packages -p /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/Packages -l /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/Packages.filelist -m /home/likewise-open/KPIT/soumyar/oe/build/tmp/deploy/glibc/ipk/all/
>> | /home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/ipkg.py:39: DeprecationWarning: the md5 module is deprecated; use hashlib instead
>> |   import md5
>> | Traceback (most recent call last):
>> |   File "/home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/ipkg-make-index", line 114, in<module>
>> |     pkg = ipkg.Package(filename)
>> |   File "/home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/ipkg.py", line 161, in __init__
>> |     tarStream = ar.open("control.tar.gz")
>> |   File "/home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/arfile.py", line 59, in open
>> |     f = self._scan(fname)
>> |   File "/home/likewise-open/KPIT/soumyar/oe/build/tmp/sysroots/i686-linux/usr/bin/arfile.py", line 79, in _scan
>> |     size = int(descriptor[5])
>> | IndexError: list index out of range
>> NOTE: Task failed: /home/likewise-open/KPIT/soumyar/oe/build/tmp/work/at91sam9263ek-angstrom-linux-gnueabi/micro-image-1.0-r0/temp/log.do_package_update_index_ipk.24831
>> ERROR: TaskFailed event exception, aborting
>> ERROR: Build of /home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/images/micro-image.bb do_package_update_index_ipk failed
>> NOTE: Running task 967 of 970 (ID: 95, /home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/mtd/mtd-utils-native_1.3.1.bb, do_package_stage)
>> ERROR: Task 18 (/home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/images/micro-image.bb, do_package_update_index_ipk) failed
>> NOTE: Waiting for 1 active tasks to finish
>> NOTE: 1: /home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/mtd/mtd-utils-native_1.3.1.bb, do_package_stage (24841)
>> NOTE: Tasks Summary: Attempted 965 tasks of which 927 didn't need to be rerun and 1 failed.
>> ERROR: '/home/likewise-open/KPIT/soumyar/oe/openembedded/recipes/images/micro-image.bb' failed
>> KPIT\soumyar@d-5289lnx:~/oe/build$
>>
>>    Anybody can help me out to resolve this.Any suggestions are welcome:-)
>>
>> Thanks in advance:-)
>>
>> Regards,
>> Soumya
>>
>>
>> _______________________________________________
>> 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
>>
>>
>>
>> _______________________________________________
>> 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

(No subject)

[Denis 'GNUtoo' Carikli]

Hi,

Is it possible to move /etc/rcS.d/S98configure before S40networking, 
so usb0 comes up at first boot, or is there some problems that would 
be introduced from such move?

Here's my problem:
on the bug machine,with Angstrom, at first boot usb0 doesn't come up 
in a console-image.
It is very annoying because the only way to get control of the machine 
is trough ssh on usbnet.

At second boot it works fine.

If I move /etc/rcS.d/S98configure before S40networking it 
works fine at first boot.

I will send a patch that changes the order of S40networking  
and S98configure to S40configure and S41networking.

Denis.

(No subject)

[Denis 'GNUtoo' Carikli]

Sorry for the lack of Subject, 

I tried to send a first mail and had an error while sending it.

Then I pasted the content of the saved mail(git-send-email often errors
for me so I saved it as a precaution),forgetting to paste the Subject.

Denis.

(No subject)

[Hauser, Wolfgang (external)]

Hello,

is there a recipe for TrueCrypt available which is usable for OE
2011.03-maintenance based environment ?

Regards
Wolfgang Hauser

(No subject)

[Craig McQueen]

I am new to OE. I am trying to build OE from the git repository, for Freescale i.MX28, following the instructions here:

http://www.imxdev.org/wiki/index.php?title=All_Boards_OpenEmbedded

I am having a build failure trying to fetch elftosb-10.12.01.tar.gz. The command I run is:

 bitbake bootstrap-image

The error is pasted at the bottom of this message.

Is bootstrap-image still a valid build target?

What needs to be fixed to build elftosb?

I am trying to build from git 'master' branch, commit b50fde72d5789b3185f9a7c64924280bb063cfad. Building on Ubuntu 11.10.

Regards,
Craig McQueen


NOTE: Running task 1299 of 4060 (ID: 844, virtual:native:/home/craigm/openembedded/stuff/openembedded/recipes/freescale/elftosb_10.12.01.bb, do_fetch)
NOTE: package elftosb-native-10.12.01-r0: task do_fetch: Started
--2012-05-01 15:12:26--  http://foss.doredevelopment.dk/mirrors/imx/elftosb-10.12.01.tar.gz
 Resolving foss.doredevelopment.dk... 62.95.78.42
 Connecting to foss.doredevelopment.dk|62.95.78.42|:80... failed: Connection timed out.
 Retrying.
 
 --2012-05-01 15:15:39--  (try: 2)  http://foss.doredevelopment.dk/mirrors/imx/elftosb-10.12.01.tar.gz
 Connecting to foss.doredevelopment.dk|62.95.78.42|:80... failed: Connection timed out.
 Retrying.
 
 --2012-05-01 15:18:50--  (try: 3)  http://foss.doredevelopment.dk/mirrors/imx/elftosb-10.12.01.tar.gz
 Connecting to foss.doredevelopment.dk|62.95.78.42|:80... failed: Connection timed out.
 Retrying.
 
 --2012-05-01 15:22:03--  (try: 4)  http://foss.doredevelopment.dk/mirrors/imx/elftosb-10.12.01.tar.gz
 Connecting to foss.doredevelopment.dk|62.95.78.42|:80... failed: Connection timed out.
 Retrying.
 
 --2012-05-01 15:25:16--  (try: 5)  http://foss.doredevelopment.dk/mirrors/imx/elftosb-10.12.01.tar.gz
 Connecting to foss.doredevelopment.dk|62.95.78.42|:80... failed: Connection timed out.
 Giving up.
 
 --2012-05-01 15:28:25--  http://mirrors.openembedded.org/elftosb-10.12.01.tar.gz
 Resolving mirrors.openembedded.org... 82.197.159.157
 Connecting to mirrors.openembedded.org|82.197.159.157|:80... failed: No route to host.
 --2012-05-01 15:28:28--  http://sources.openembedded.org/elftosb-10.12.01.tar.gz
 Resolving sources.openembedded.org... 140.211.169.152
 Connecting to sources.openembedded.org|140.211.169.152|:80... connected.
 HTTP request sent, awaiting response... 404 Not Found
 2012-05-01 15:28:29 ERROR 404: Not Found.
 
 --2012-05-01 15:28:29--  http://www.angstrom-distribution.org/unstable/sources/elftosb-10.12.01.tar.gz
 Resolving www.angstrom-distribution.org... 188.40.83.200
 Connecting to www.angstrom-distribution.org|188.40.83.200|:80... connected.
 HTTP request sent, awaiting response... 404 Not Found
 2012-05-01 15:28:31 ERROR 404: Not Found.
 
NOTE: package elftosb-native-10.12.01-r0: task Fetch failed: Unable to fetch URL http://foss.doredevelopment.dk/mirrors/imx/elftosb-10.12.01.tar.gz from any source.: Failed
ERROR: Function 'Fetch failed: Unable to fetch URL http://foss.doredevelopment.dk/mirrors/imx/elftosb-10.12.01.tar.gz from any source.' failed
ERROR: Task 844 (virtual:native:/home/craigm/openembedded/stuff/openembedded/recipes/freescale/elftosb_10.12.01.bb, do_fetch) failed with exit code '1'
ERROR: 'virtual:native:/home/craigm/openembedded/stuff/openembedded/recipes/freescale/elftosb_10.12.01.bb' failed
craigm@fw-linux:~/openembedded$

(No subject)

[Radoslav Kolev]

On Tue, May 1, 2012 at 10:57 AM, Craig McQueen
<craig.mcqueen@beamcommunications.com> wrote:
> I am new to OE. I am trying to build OE from the git repository, for Freescale i.MX28, following the instructions here:

If you're starting a new project may be it's better to base it on
oe-core. Have a look here:
http://groups.google.com/group/meta-fsl-arm

> I am having a build failure trying to fetch elftosb-10.12.01.tar.gz. The command I run is:

change the SRC_URI to this one in the elftosb recipe:

SRC_URI = "http://repository.timesys.com/buildsources/e/elftosb/elftosb-${PV}/elftosb-${PV}.tar.gz"

Regards,
Rado

(No subject)

[Andreas Müller]

after updating all my repos (angstrom+few extra layers) I get

  /home/Superandy/data/oe-core/sources/meta-intel/meta-sugarbay/recipes-kernel/linux/linux-yocto_3.2.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-crownbay/recipes-kernel/linux/linux-yocto_3.2.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-emenlow/recipes-kernel/linux/linux-yocto_3.2.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-fishriver/recipes-kernel/linux/linux-yocto_3.2.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-fri2/recipes-kernel/linux/linux-yocto_3.2.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-jasperforest/recipes-kernel/linux/linux-yocto_3.2.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-n450/recipes-kernel/linux/linux-yocto_3.2.bbappend
  /home/Superandy/data/oe-core/sources/meta-handheld/recipes-kernel/linux/linux-yocto_3.2.bbappend
  /home/Superandy/data/oe-core/sources/meta-openembedded/meta-oe/recipes-connectivity/dhcp/dhcp_4.2.3-P2.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-sugarbay/recipes-bsp/formfactor/formfactor_0.0.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-crownbay/recipes-bsp/formfactor/formfactor_0.0.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-emenlow/recipes-bsp/formfactor/formfactor_0.0.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-fishriver/recipes-bsp/formfactor/formfactor_0.0.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-fri2/recipes-bsp/formfactor/formfactor_0.0.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-jasperforest/recipes-bsp/formfactor/formfactor_0.0.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-n450/recipes-bsp/formfactor/formfactor_0.0.bbappend
  /home/Superandy/data/oe-core/sources/meta-smartphone/meta-nokia/recipes-bsp/formfactor/formfactor_0.0.bbappend
  /home/Superandy/data/oe-core/sources/meta-handheld/recipes-bsp/formfactor/formfactor_0.0.bbappend
  /home/Superandy/data/oe-core/sources/meta-ti/recipes-bsp/formfactor/formfactor_0.0.bbappend
  /home/Superandy/data/oe-core/sources/meta-smartphone/meta-nokia/recipes-multimedia/mplayer/mplayer2_git.bbappend
  /home/Superandy/data/oe-core/sources/meta-smartphone/meta-openmoko/recipes-multimedia/mplayer/mplayer2_git.bbappend
  /home/Superandy/data/oe-core/sources/meta-angstrom/recipes-core/update-rc.d/update-rc.d_0.7.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-sugarbay/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-crownbay/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-emenlow/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-fishriver/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-fri2/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-jasperforest/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-n450/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend
  /home/Superandy/data/oe-core/sources/meta-openembedded/meta-oe/recipes-connectivity/wpa-supplicant/wpa-supplicant_0.7.3.bbappend
  /home/Superandy/data/oe-core/sources/meta-smartphone/meta-palm/recipes-bsp/x-load/x-load_git.bbappend
  /home/Superandy/data/oe-core/sources/meta-gumstix/recipes-bsp/x-load/x-load_git.bbappend
  /home/Superandy/data/oe-core/sources/meta-angstrom/recipes-extended/zypper/zypper_git.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-sugarbay/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-crownbay/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-emenlow/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-fishriver/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-fri2/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-jasperforest/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-n450/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend
  /home/Superandy/data/oe-core/sources/meta-openembedded/toolchain-layer/recipes-devtools/gcc/gcc-runtime_4.6.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-emenlow/recipes-qt/qt4/qt4-x11-free_4.8.1.bbappend
  /home/Superandy/data/oe-core/sources/meta-openembedded/meta-oe/recipes-qt/qt4/qt4-x11-free_4.8.1.bbappend
  /home/Superandy/data/oe-core/sources/meta-kde/recipes-misc-support/qt4-x11-free_4.8.1.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-fri2/recipes-bsp/alsa-state/alsa-state.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-n450/recipes-bsp/alsa-state/alsa-state.bbappend
  /home/Superandy/data/oe-core/sources/meta-ti/recipes-bsp/alsa-state/alsa-state.bbappend
  /home/Superandy/data/oe-core/sources/meta-smartphone/meta-palm/recipes-graphics/tslib/tslib_git.bbappend
  /home/Superandy/data/oe-core/sources/meta-openembedded/meta-oe/recipes-connectivity/openssh/openssh_6.0p1.bbappend
  /home/Superandy/data/oe-core/sources/meta-handheld/recipes-bsp/kexecboot/kexecboot-klibc_git.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-emenlow/recipes-gnome/tasks/task-core-sdk-gmae.bbappend
  /home/Superandy/data/oe-core/sources/meta-openembedded/toolchain-layer/recipes-devtools/gcc/gcc-crosssdk-intermediate_4.6.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-sugarbay/recipes-kernel/linux/linux-yocto_3.0.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-crownbay/recipes-kernel/linux/linux-yocto_3.0.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-emenlow/recipes-kernel/linux/linux-yocto_3.0.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-fishriver/recipes-kernel/linux/linux-yocto_3.0.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-fri2/recipes-kernel/linux/linux-yocto_3.0.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-jasperforest/recipes-kernel/linux/linux-yocto_3.0.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-n450/recipes-kernel/linux/linux-yocto_3.0.bbappend
  /home/Superandy/data/oe-core/sources/meta-openembedded/toolchain-layer/recipes-devtools/gcc/gcc_4.6.bbappend
  /home/Superandy/data/oe-core/sources/meta-openembedded/meta-oe/recipes-qt/tasks/task-qte-toolchain-target.bbappend
  /home/Superandy/data/oe-core/sources/meta-openembedded/meta-oe/recipes-qt/qt4/qt4-embedded_4.8.1.bbappend
  /home/Superandy/data/oe-core/sources/meta-angstrom/recipes-core/base-files/base-files_3.0.14.bbappend
  /home/Superandy/data/oe-core/sources/meta-smartphone/meta-nokia/recipes-core/base-files/base-files_3.0.14.bbappend
  /home/Superandy/data/oe-core/sources/meta-smartphone/meta-openmoko/recipes-core/base-files/base-files_3.0.14.bbappend
  /home/Superandy/data/oe-core/sources/meta-kde/recipes-misc-support/qt4-native_4.8.1.bbappend
  /home/Superandy/data/oe-core/sources/meta-ti/recipes-core/netbase/netbase_4.47.bbappend
  /home/Superandy/data/oe-core/sources/meta-openembedded/meta-oe/recipes-extended/lighttpd/lighttpd_1.4.30.bbappend
  /home/Superandy/data/oe-core/sources/meta-openembedded/meta-oe/recipes-multimedia/gstreamer/gst-ffmpeg_0.10.13.bbappend
  /home/Superandy/data/oe-core/sources/meta-smartphone/meta-openmoko/recipes-graphics/drm/libdrm_2.4.34.bbappend
  /home/Superandy/data/oe-core/sources/meta-gumstix/recipes-bsp/powervr-drivers/omap3-sgx-modules_4.05.00.03.bbappend
  /home/Superandy/data/oe-core/sources/meta-openembedded/meta-oe/recipes-core/dropbear/dropbear_2012.55.bbappend
  /home/Superandy/data/oe-core/sources/meta-openembedded/toolchain-layer/recipes-devtools/gcc/gcc-cross_4.6.bbappend
  /home/Superandy/data/oe-core/sources/meta-smartphone/meta-openmoko/recipes-multimedia/mplayer/mplayer-common.bbappend
  /home/Superandy/data/oe-core/sources/meta-freescale/recipes-bsp/u-boot/u-boot_git.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-sugarbay/recipes-core/tasks/task-core-tools-profile.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-crownbay/recipes-core/tasks/task-core-tools-profile.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-emenlow/recipes-core/tasks/task-core-tools-profile.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-fishriver/recipes-core/tasks/task-core-tools-profile.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-fri2/recipes-core/tasks/task-core-tools-profile.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-jasperforest/recipes-core/tasks/task-core-tools-profile.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-n450/recipes-core/tasks/task-core-tools-profile.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-sugarbay/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-emenlow/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-fishriver/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-fri2/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-jasperforest/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-n450/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
  /home/Superandy/data/oe-core/sources/meta-smartphone/meta-htc/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
  /home/Superandy/data/oe-core/sources/meta-smartphone/meta-nokia/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
  /home/Superandy/data/oe-core/sources/meta-smartphone/meta-openmoko/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
  /home/Superandy/data/oe-core/sources/meta-smartphone/meta-palm/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
  /home/Superandy/data/oe-core/sources/meta-handheld/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
  /home/Superandy/data/oe-core/sources/meta-ti/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
  /home/Superandy/data/oe-core/sources/meta-openembedded/meta-oe/recipes-extended/cronie/cronie_1.4.8.bbappend
  /home/Superandy/data/oe-core/sources/meta-smartphone/meta-nokia/recipes-core/initscripts/initscripts_1.0.bbappend
  /home/Superandy/data/oe-core/sources/meta-smartphone/meta-openmoko/recipes-core/initscripts/initscripts_1.0.bbappend
  /home/Superandy/data/oe-core/sources/meta-smartphone/meta-palm/recipes-core/initscripts/initscripts_1.0.bbappend
  /home/Superandy/data/oe-core/sources/meta-openembedded/meta-oe/recipes-gnome/gtk+/gtk-update-icon-cache-runonce.bbappend
  /home/Superandy/data/oe-core/sources/meta-openembedded/meta-oe/recipes-extended/polkit/polkit_0.104.bbappend
  /home/Superandy/data/oe-core/sources/meta-openembedded/toolchain-layer/recipes-devtools/gcc/gcc-cross-canadian_4.6.bbappend
  /home/Superandy/data/oe-core/sources/meta-smartphone/meta-nokia/recipes-graphics/xinput-calibrator/pointercal-xinput_0.0.bbappend
  /home/Superandy/data/oe-core/sources/meta-smartphone/meta-openmoko/recipes-graphics/xinput-calibrator/pointercal-xinput_0.0.bbappend
  /home/Superandy/data/oe-core/sources/meta-gumstix/recipes-kernel/linux/linux_3.0.bbappend
  /home/Superandy/data/oe-core/sources/meta-handheld/recipes-kernel/linux/linux-yocto-tiny-kexecboot_3.2.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/meta-emenlow/recipes-gnome/tasks/task-core-standalone-gmae-sdk-target.bbappend
  /home/Superandy/data/oe-core/sources/meta-smartphone/meta-openmoko/recipes-core/tasks/task-base.bbappend
  /home/Superandy/data/oe-core/sources/meta-handheld/recipes-bsp/kexecboot/kexecboot_git.bbappend
  /home/Superandy/data/oe-core/sources/meta-smartphone/meta-nokia/recipes-core/systemd/systemd-machine-units_1.0.bbappend
  /home/Superandy/data/oe-core/sources/meta-smartphone/meta-openmoko/recipes-core/systemd/systemd-machine-units_1.0.bbappend
  /home/Superandy/data/oe-core/sources/meta-openembedded/meta-gnome/recipes-gnome/gtk+/gtk+_2.24.8.bbappend
  /home/Superandy/data/oe-core/sources/meta-openembedded/meta-oe/recipes-connectivity/connman/connman_0.79.bbappend
  /home/Superandy/data/oe-core/sources/meta-smartphone/meta-palm/recipes-support/lvm2/lvm2_2.02.85.bbappend
  /home/Superandy/data/oe-core/sources/meta-smartphone/meta-openmoko/recipes-graphics/mesa/mesa-dri_7.11.bbappend
  /home/Superandy/data/oe-core/sources/meta-openembedded/toolchain-layer/recipes-devtools/gcc/gcc-crosssdk-initial_4.6.bbappend
  /home/Superandy/data/oe-core/sources/meta-browser/recipes-support/nspr/nspr_4.8.9.bbappend
  /home/Superandy/data/oe-core/sources/meta-openembedded/meta-oe/recipes-graphics/xorg-lib/pixman_0.25.2.bbappend
  /home/Superandy/data/oe-core/sources/meta-angstrom/recipes-core/sysvinit/sysvinit_2.88dsf.bbappend
  /home/Superandy/data/oe-core/sources/meta-smartphone/meta-openmoko/recipes-navigation/gpsd/gpsd_3.4.bbappend
  /home/Superandy/data/oe-core/sources/meta-openembedded/meta-oe/recipes-bsp/keymaps/keymaps_1.0.bbappend
  /home/Superandy/data/oe-core/sources/meta-smartphone/meta-nokia/recipes-bsp/keymaps/keymaps_1.0.bbappend
  /home/Superandy/data/oe-core/sources/meta-handheld/recipes-bsp/keymaps/keymaps_1.0.bbappend
  /home/Superandy/data/oe-core/sources/meta-openembedded/meta-oe/recipes-core/busybox/busybox_1.19.4.bbappend
  /home/Superandy/data/oe-core/sources/meta-openembedded/toolchain-layer/recipes-devtools/gcc/gcc-cross-intermediate_4.6.bbappend
  /home/Superandy/data/oe-core/sources/meta-intel/common/recipes-kernel/linux-firmware/linux-firmware_git.bbappend
  /home/Superandy/data/oe-core/sources/meta-openembedded/toolchain-layer/recipes-devtools/gcc/gcc-crosssdk_4.6.bbappend
  /home/Superandy/data/oe-core/sources/meta-openembedded/toolchain-layer/recipes-devtools/gcc/gcc-cross-initial_4.6.bbappend
  /home/Superandy/data/oe-core/sources/meta-gumstix/recipes-kernel/linux/linux-mainline_3.2.bbappend
  /home/Superandy/data/oe-core/sources/meta-openembedded/toolchain-layer/recipes-devtools/gcc/libgcc_4.6.bbappend
  /home/Superandy/data/oe-core/sources/meta-handheld/recipes-core/udev/udev_164.bbappend

Strange: many recipes are available. Anybody else with similar experience?

Andreas

(No subject)

[Henning Heinold]

Hi,

yes, that means the recpies are deleted in oe-core. For a quick workaround just delete the append files.
Another issue for now is the removing of the linux-tools.inc So you have to delete the include in all
the kernel recipes.

Bye Henning

(No subject)

[Joe MacDonald]

Forwarding a patch I received last week from Colin Walters.  Initially I
thought it was duplicating the patch for cyrus-sasl from Roy Li, but it
actaully seems to be solving a related problem that isn't quite the same.
If anything, it looks like perhaps the earlier change may make the thing
Colin was fixing more common.

-- 
-Joe MacDonald.
:wq

(No subject)

[Philip Balister]

I was trying to get this recipe into meta-oe before the daisy branch, but 
it had to wait on some other patches to get into oe-core.

Now that these are in place, it would be very helpful for people using
GNU Radio from daisy if this recipe was in the meta-oe/daisy.

Thanks,

Philip

(No subject)

[Khem Raj]

On Fri, Jul 11, 2014 at 7:54 AM, Philip Balister <philip@balister.org> wrote:
>
> I was trying to get this recipe into meta-oe before the daisy branch, but
> it had to wait on some other patches to get into oe-core.

which one?

>
> Now that these are in place, it would be very helpful for people using
> GNU Radio from daisy if this recipe was in the meta-oe/daisy.
>
> Thanks,
>
> Philip
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel

(No subject)

[Joe MacDonald]

These four are bridge measures I took to get my images building again
while merging the backlog of meta-networking patches.  I'm now circling
back to clear out first the waf issue, which I think will resolve the
samba and libldb (and related library) errors, then start looking at the
excess of blacklisting we've had to do lately.

-- 
Joe MacDonald
:wq

(No subject)

[Andrej Rode]

This patchset adds python-mprpc and python-gsocketpool to meta-python.
mprpc is a messagepack RPC implementation for python.

(No subject)

[Мар'ян Пріцак]

Hi all,

I'm trying to build an image that's supposed to be used as rootfs for
container.
Is there a way to build image rootfs without Linux kernel and modules?

BR,
Marian

(No subject)

[Josef Holzmayr]

Hi Maryan,

On 19.06.2017 16:57, Мар'ян Пріцак wrote:
> I'm trying to build an image that's supposed to be used as rootfs for
> container.
> Is there a way to build image rootfs without Linux kernel and modules?

The simplest solution is to just refer to linux-dummy:
https://layers.openembedded.org/layerindex/recipe/41/

If you're not in a hurry, I expect to push a layer doing exactly what 
you describe to github, as I'm working on that too.

Greetz
-- 
Josef Holzmayr
Software Developer Embedded Systems

Tel: +49 8444 9204-48
Fax: +49 8444 9204-50

R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
www.rsi-elektrotechnik.de
———————————————
Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
Ust-IdNr: DE 128592548

_____________________________________________________________
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548

(No subject)

[Tamtamis, Panagiotis]

[-- Attachment #1: Type: text/plain, Size: 1644 bytes --]

Hi Maryan,

> -----Original Message-----
> From: openembedded-devel-bounces@lists.openembedded.org
> [mailto:openembedded-devel-bounces@lists.openembedded.org] On
> Behalf Of Josef Holzmayr
> Sent: Monday, June 19, 2017 10:02 PM
> To: Мар'ян Пріцак; openembeded-devel
> Subject: Re: [oe] (no subject)
> 
> Hi Maryan,
> 
> On 19.06.2017 16:57, Мар'ян Пріцак wrote:
> > I'm trying to build an image that's supposed to be used as rootfs for
> > container.
> > Is there a way to build image rootfs without Linux kernel and modules?

I use the following in my image recipe:

FORCE_RO_REMOVE = "1"
ROOTFS_RO_UNNEEDED += " kernel-${LINUX_VERSION} kernel-image-${LINUX_VERSION} kernel-image-uimage-${LINUX_VERSION}"

With the above you force the image production to remove unwanted packets. You can add also the modules that you don't want.
See if this can work in your case also.

> 
> The simplest solution is to just refer to linux-dummy:
> https://layers.openembedded.org/layerindex/recipe/41/
> 
> If you're not in a hurry, I expect to push a layer doing exactly what you
> describe to github, as I'm working on that too.
> 
> Greetz
> --
> Josef Holzmayr
> Software Developer Embedded Systems
> 
> Tel: +49 8444 9204-48
> Fax: +49 8444 9204-50
> 
> R-S-I Elektrotechnik GmbH & Co. KG
> Woelkestrasse 11
> D-85301 Schweitenkirchen
> www.rsi-elektrotechnik.de
> ———————————————
> Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393
> Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
> Ust-IdNr: DE 128592548

Br,
Tamis

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 4874 bytes --]

(No subject)

[Josef Holzmayr]

Hi Tamis,

On 20.06.2017 10:07, Tamtamis, Panagiotis wrote:
> I use the following in my image recipe:
> 
> FORCE_RO_REMOVE = "1"
> ROOTFS_RO_UNNEEDED += " kernel-${LINUX_VERSION} kernel-image-${LINUX_VERSION} kernel-image-uimage-${LINUX_VERSION}"

While that might work, it actually builds all the stuff and then only 
excludes it from the rootfs generation. But if we actually never ever 
want a kernel, why spend the compile time? :)

Greetz
-- 
Josef Holzmayr
Software Developer Embedded Systems

Tel: +49 8444 9204-48
Fax: +49 8444 9204-50

R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
www.rsi-elektrotechnik.de
———————————————
Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
Ust-IdNr: DE 128592548

_____________________________________________________________
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548

(No subject)

[Tamtamis, Panagiotis]

[-- Attachment #1: Type: text/plain, Size: 678 bytes --]

Hello Josef,

> Hi Tamis,
>
> On 20.06.2017 10:07, Tamtamis, Panagiotis wrote:
> > I use the following in my image recipe:
> >
> > FORCE_RO_REMOVE = "1"
> > ROOTFS_RO_UNNEEDED += " kernel-${LINUX_VERSION} kernel-image-
> ${LINUX_VERSION} kernel-image-uimage-${LINUX_VERSION}"
>
> While that might work, it actually builds all the stuff and then only 
> excludes it
> from the rootfs generation. But if we actually never ever want a kernel, why
> spend the compile time? :)

I agree with you. Even if cross compiling in production server does not take 
that much time, it is not the optimal solution.
I will also see your layer at GitHub  :-).

Br,
Tamis


[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 4874 bytes --]

(No subject)

[Мар'ян Пріцак]

Thanks guys, linux-dummy worked for me.

BR,
Marian

On Tue, Jun 20, 2017 at 5:32 PM Tamtamis, Panagiotis <
panagiotis.tamtamis@unify.com> wrote:

> Hello Josef,
>
> > Hi Tamis,
> >
> > On 20.06.2017 10:07, Tamtamis, Panagiotis wrote:
> > > I use the following in my image recipe:
> > >
> > > FORCE_RO_REMOVE = "1"
> > > ROOTFS_RO_UNNEEDED += " kernel-${LINUX_VERSION} kernel-image-
> > ${LINUX_VERSION} kernel-image-uimage-${LINUX_VERSION}"
> >
> > While that might work, it actually builds all the stuff and then only
> > excludes it
> > from the rootfs generation. But if we actually never ever want a kernel,
> why
> > spend the compile time? :)
>
> I agree with you. Even if cross compiling in production server does not
> take
> that much time, it is not the optimal solution.
> I will also see your layer at GitHub  :-).
>
> Br,
> Tamis
>
>

(No subject)

[Parthiban Nallathambi]

As I lost the message ID of the actual request for bitbake recipe
for xscreensaver, I am sending in a separate email

(No subject)

[William Delacre]

Hi ! :-)

I’m facing issues when trying to run ‘bitbake python-twisted’ (do_compile
error)

Log says :
“Download error on https://pypi.python.org/simple/incremental/: [Errno -3]
Temporary failure in name resolution

............

distutils.errors.DistutilsError : Could not find suitable distribution for
Requirement.parse(‘incremental>=16.10.1’)”

First of all I’m not connected to internet, so I’ve pre-downloaded all the
required packages (twisted-17.9.0.tar.bz2 & incremental-17.5.0.tar.gz are
present in my build/downloads folder)

It’s the first time I have some “downloading issues” and I’m stuck on it
for a few hours now..

Any tips for me ?

Thanks in advance !

(No subject)

[Mark Asselstine]

On Mon, Jul 23, 2018 at 8:28 AM, William Delacre
<williamdelacre@gmail.com> wrote:
> Hi ! :-)
>
> I’m facing issues when trying to run ‘bitbake python-twisted’ (do_compile
> error)
>
> Log says :
> “Download error on https://pypi.python.org/simple/incremental/: [Errno -3]
> Temporary failure in name resolution
>
> ............
>
> distutils.errors.DistutilsError : Could not find suitable distribution for
> Requirement.parse(‘incremental>=16.10.1’)”
>
> First of all I’m not connected to internet, so I’ve pre-downloaded all the
> required packages (twisted-17.9.0.tar.bz2 & incremental-17.5.0.tar.gz are
> present in my build/downloads folder)
>
> It’s the first time I have some “downloading issues” and I’m stuck on it
> for a few hours now..
>
> Any tips for me ?

Check all aspects of what you have manually downloaded and populated
in your downloads. My guess is that a checksum or some other detail
isn't matching and it is rejecting what you have and thus attempting
to re-download the file.

Mark

>
> Thanks in advance !
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel

(No subject)

[Mark Asselstine]

On Thu, Jul 26, 2018 at 3:40 PM, Mark Asselstine
<mark.asselstine@windriver.com> wrote:
> On Mon, Jul 23, 2018 at 8:28 AM, William Delacre
> <williamdelacre@gmail.com> wrote:
>> Hi ! :-)
>>
>> I’m facing issues when trying to run ‘bitbake python-twisted’ (do_compile
>> error)
>>
>> Log says :
>> “Download error on https://pypi.python.org/simple/incremental/: [Errno -3]
>> Temporary failure in name resolution

With the additional info you sent me along with a second look at the
error I can fairly confidently say I know what the issue is.

Python, like some other languages (ruby, go...) will attempt to
download dependencies/requirements if they are not present. This is
done "outside" of the bitbake system and thus will ignore
BB_NO_NETWORK and is generally a bad thing. It isn't quite host
contamination but it is very similar. What we do with our python
recipes in bitbake is review a python package's source setup.py,
requirements.txt...files in order to determine what other python
packages are needed, add them as RDEPENDS or similar in order to avoid
the python attempting to complete a download such as this.

In this case python-twisted 'requires' python-incremental but the
Rocko version of the python-twisted recipe lacks the needed assignment
to ensure this is available in the recipe sysroot and thus the
attempted download.

Cherry pick commit b08b570c8624303acbb6bb064a7bda466a679df4
[python-twisted: avoid downloading build dependencies] to Rocko and
you will be good to go. You should also follow up this thread with a
request to have this commit put onto Rocko to avoid others hitting the
same issue.

Mark

>>
>> ............
>>
>> distutils.errors.DistutilsError : Could not find suitable distribution for
>> Requirement.parse(‘incremental>=16.10.1’)”
>>
>> First of all I’m not connected to internet, so I’ve pre-downloaded all the
>> required packages (twisted-17.9.0.tar.bz2 & incremental-17.5.0.tar.gz are
>> present in my build/downloads folder)
>>
>> It’s the first time I have some “downloading issues” and I’m stuck on it
>> for a few hours now..
>>
>> Any tips for me ?
>
> Check all aspects of what you have manually downloaded and populated
> in your downloads. My guess is that a checksum or some other detail
> isn't matching and it is rejecting what you have and thus attempting
> to re-download the file.
>
> Mark
>
>>
>> Thanks in advance !
>> --
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel

(No subject)

[William Delacre]

Thanks a lot for the answer, it worked perfectly !

There is just one point I don’t really understand : why do we need to add a
dependency to ‘python-incremental-NATIVE’ ?

What would happen if I just add to the python-twisted recipe :

DEPENDS += “${PYTHON_PN}-incremental“

William

Le ven. 27 juil. 2018 à 17:03, Mark Asselstine <
mark.asselstine@windriver.com> a écrit :

> On Thu, Jul 26, 2018 at 3:40 PM, Mark Asselstine
> <mark.asselstine@windriver.com> wrote:
> > On Mon, Jul 23, 2018 at 8:28 AM, William Delacre
> > <williamdelacre@gmail.com> wrote:
> >> Hi ! :-)
> >>
> >> I’m facing issues when trying to run ‘bitbake python-twisted’
> (do_compile
> >> error)
> >>
> >> Log says :
> >> “Download error on https://pypi.python.org/simple/incremental/: [Errno
> -3]
> >> Temporary failure in name resolution
>
> With the additional info you sent me along with a second look at the
> error I can fairly confidently say I know what the issue is.
>
> Python, like some other languages (ruby, go...) will attempt to
> download dependencies/requirements if they are not present. This is
> done "outside" of the bitbake system and thus will ignore
> BB_NO_NETWORK and is generally a bad thing. It isn't quite host
> contamination but it is very similar. What we do with our python
> recipes in bitbake is review a python package's source setup.py,
> requirements.txt...files in order to determine what other python
> packages are needed, add them as RDEPENDS or similar in order to avoid
> the python attempting to complete a download such as this.
>
> In this case python-twisted 'requires' python-incremental but the
> Rocko version of the python-twisted recipe lacks the needed assignment
> to ensure this is available in the recipe sysroot and thus the
> attempted download.
>
> Cherry pick commit b08b570c8624303acbb6bb064a7bda466a679df4
> [python-twisted: avoid downloading build dependencies] to Rocko and
> you will be good to go. You should also follow up this thread with a
> request to have this commit put onto Rocko to avoid others hitting the
> same issue.
>
> Mark
>
> >>
> >> ............
> >>
> >> distutils.errors.DistutilsError : Could not find suitable distribution
> for
> >> Requirement.parse(‘incremental>=16.10.1’)”
> >>
> >> First of all I’m not connected to internet, so I’ve pre-downloaded all
> the
> >> required packages (twisted-17.9.0.tar.bz2 & incremental-17.5.0.tar.gz
> are
> >> present in my build/downloads folder)
> >>
> >> It’s the first time I have some “downloading issues” and I’m stuck on it
> >> for a few hours now..
> >>
> >> Any tips for me ?
> >
> > Check all aspects of what you have manually downloaded and populated
> > in your downloads. My guess is that a checksum or some other detail
> > isn't matching and it is rejecting what you have and thus attempting
> > to re-download the file.
> >
> > Mark
> >
> >>
> >> Thanks in advance !
> >> --
> >> _______________________________________________
> >> Openembedded-devel mailing list
> >> Openembedded-devel@lists.openembedded.org
> >> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>

(No subject)

[Mark Asselstine]

On Friday, July 27, 2018 12:04:37 PM EDT William Delacre wrote:
> Thanks a lot for the answer, it worked perfectly !
> 
> There is just one point I don’t really understand : why do we need to add a
> dependency to ‘python-incremental-NATIVE’ ?
> 
> What would happen if I just add to the python-twisted recipe :
> 
> DEPENDS += “${PYTHON_PN}-incremental“

This would assume that python is completely arch independent, which it is not. 
Assume for example python-incremental had some C extensions, using DEPENDS 
would build them for the target arch yet possibly attempt to run them on your 
build host. -native takes care of this.

Some may say this is a bit of a hack since the difference in ARCH *might* 
equate to a difference in behavior. But I have dealt with many python recipes 
and have yet to run into any scenario where this potential issue exists.

At least that is what I can recall at the moment. Unfortunately I have 
forgotten some of the subtleties that might be in play.

Mark

> 
> William
> 
> Le ven. 27 juil. 2018 à 17:03, Mark Asselstine <
> 
> mark.asselstine@windriver.com> a écrit :
> > On Thu, Jul 26, 2018 at 3:40 PM, Mark Asselstine
> > 
> > <mark.asselstine@windriver.com> wrote:
> > > On Mon, Jul 23, 2018 at 8:28 AM, William Delacre
> > > 
> > > <williamdelacre@gmail.com> wrote:
> > >> Hi ! :-)
> > >> 
> > >> I’m facing issues when trying to run ‘bitbake python-twisted’
> > 
> > (do_compile
> > 
> > >> error)
> > >> 
> > >> Log says :
> > >> “Download error on https://pypi.python.org/simple/incremental/: [Errno
> > 
> > -3]
> > 
> > >> Temporary failure in name resolution
> > 
> > With the additional info you sent me along with a second look at the
> > error I can fairly confidently say I know what the issue is.
> > 
> > Python, like some other languages (ruby, go...) will attempt to
> > download dependencies/requirements if they are not present. This is
> > done "outside" of the bitbake system and thus will ignore
> > BB_NO_NETWORK and is generally a bad thing. It isn't quite host
> > contamination but it is very similar. What we do with our python
> > recipes in bitbake is review a python package's source setup.py,
> > requirements.txt...files in order to determine what other python
> > packages are needed, add them as RDEPENDS or similar in order to avoid
> > the python attempting to complete a download such as this.
> > 
> > In this case python-twisted 'requires' python-incremental but the
> > Rocko version of the python-twisted recipe lacks the needed assignment
> > to ensure this is available in the recipe sysroot and thus the
> > attempted download.
> > 
> > Cherry pick commit b08b570c8624303acbb6bb064a7bda466a679df4
> > [python-twisted: avoid downloading build dependencies] to Rocko and
> > you will be good to go. You should also follow up this thread with a
> > request to have this commit put onto Rocko to avoid others hitting the
> > same issue.
> > 
> > Mark
> > 
> > >> ............
> > >> 
> > >> distutils.errors.DistutilsError : Could not find suitable distribution
> > 
> > for
> > 
> > >> Requirement.parse(‘incremental>=16.10.1’)”
> > >> 
> > >> First of all I’m not connected to internet, so I’ve pre-downloaded all
> > 
> > the
> > 
> > >> required packages (twisted-17.9.0.tar.bz2 & incremental-17.5.0.tar.gz
> > 
> > are
> > 
> > >> present in my build/downloads folder)
> > >> 
> > >> It’s the first time I have some “downloading issues” and I’m stuck on
> > >> it
> > >> for a few hours now..
> > >> 
> > >> Any tips for me ?
> > > 
> > > Check all aspects of what you have manually downloaded and populated
> > > in your downloads. My guess is that a checksum or some other detail
> > > isn't matching and it is rejecting what you have and thus attempting
> > > to re-download the file.
> > > 
> > > Mark
> > > 
> > >> Thanks in advance !
> > >> --
> > >> _______________________________________________
> > >> Openembedded-devel mailing list
> > >> Openembedded-devel@lists.openembedded.org
> > >> http://lists.openembedded.org/mailman/listinfo/openembedded-devel

(No subject)

[William Delacre]

Okay, it makes sense!

My question may seem stupid but then why don’t we always use ‘-native’ for
the dependencies ?

Is it because sometimes we know that the behavior of ‘foo’ and ‘foo-native’
would be the same, independently of the architecture ?

William

Le ven. 27 juil. 2018 à 18:16, Mark Asselstine <
mark.asselstine@windriver.com> a écrit :

> On Friday, July 27, 2018 12:04:37 PM EDT William Delacre wrote:
> > Thanks a lot for the answer, it worked perfectly !
> >
> > There is just one point I don’t really understand : why do we need to
> add a
> > dependency to ‘python-incremental-NATIVE’ ?
> >
> > What would happen if I just add to the python-twisted recipe :
> >
> > DEPENDS += “${PYTHON_PN}-incremental“
>
> This would assume that python is completely arch independent, which it is
> not.
> Assume for example python-incremental had some C extensions, using DEPENDS
> would build them for the target arch yet possibly attempt to run them on
> your
> build host. -native takes care of this.
>
> Some may say this is a bit of a hack since the difference in ARCH *might*
> equate to a difference in behavior. But I have dealt with many python
> recipes
> and have yet to run into any scenario where this potential issue exists.
>
> At least that is what I can recall at the moment. Unfortunately I have
> forgotten some of the subtleties that might be in play.
>
> Mark
>
> >
> > William
> >
> > Le ven. 27 juil. 2018 à 17:03, Mark Asselstine <
> >
> > mark.asselstine@windriver.com> a écrit :
> > > On Thu, Jul 26, 2018 at 3:40 PM, Mark Asselstine
> > >
> > > <mark.asselstine@windriver.com> wrote:
> > > > On Mon, Jul 23, 2018 at 8:28 AM, William Delacre
> > > >
> > > > <williamdelacre@gmail.com> wrote:
> > > >> Hi ! :-)
> > > >>
> > > >> I’m facing issues when trying to run ‘bitbake python-twisted’
> > >
> > > (do_compile
> > >
> > > >> error)
> > > >>
> > > >> Log says :
> > > >> “Download error on https://pypi.python.org/simple/incremental/:
> [Errno
> > >
> > > -3]
> > >
> > > >> Temporary failure in name resolution
> > >
> > > With the additional info you sent me along with a second look at the
> > > error I can fairly confidently say I know what the issue is.
> > >
> > > Python, like some other languages (ruby, go...) will attempt to
> > > download dependencies/requirements if they are not present. This is
> > > done "outside" of the bitbake system and thus will ignore
> > > BB_NO_NETWORK and is generally a bad thing. It isn't quite host
> > > contamination but it is very similar. What we do with our python
> > > recipes in bitbake is review a python package's source setup.py,
> > > requirements.txt...files in order to determine what other python
> > > packages are needed, add them as RDEPENDS or similar in order to avoid
> > > the python attempting to complete a download such as this.
> > >
> > > In this case python-twisted 'requires' python-incremental but the
> > > Rocko version of the python-twisted recipe lacks the needed assignment
> > > to ensure this is available in the recipe sysroot and thus the
> > > attempted download.
> > >
> > > Cherry pick commit b08b570c8624303acbb6bb064a7bda466a679df4
> > > [python-twisted: avoid downloading build dependencies] to Rocko and
> > > you will be good to go. You should also follow up this thread with a
> > > request to have this commit put onto Rocko to avoid others hitting the
> > > same issue.
> > >
> > > Mark
> > >
> > > >> ............
> > > >>
> > > >> distutils.errors.DistutilsError : Could not find suitable
> distribution
> > >
> > > for
> > >
> > > >> Requirement.parse(‘incremental>=16.10.1’)”
> > > >>
> > > >> First of all I’m not connected to internet, so I’ve pre-downloaded
> all
> > >
> > > the
> > >
> > > >> required packages (twisted-17.9.0.tar.bz2 &
> incremental-17.5.0.tar.gz
> > >
> > > are
> > >
> > > >> present in my build/downloads folder)
> > > >>
> > > >> It’s the first time I have some “downloading issues” and I’m stuck
> on
> > > >> it
> > > >> for a few hours now..
> > > >>
> > > >> Any tips for me ?
> > > >
> > > > Check all aspects of what you have manually downloaded and populated
> > > > in your downloads. My guess is that a checksum or some other detail
> > > > isn't matching and it is rejecting what you have and thus attempting
> > > > to re-download the file.
> > > >
> > > > Mark
> > > >
> > > >> Thanks in advance !
> > > >> --
> > > >> _______________________________________________
> > > >> Openembedded-devel mailing list
> > > >> Openembedded-devel@lists.openembedded.org
> > > >> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>
>
>
>
>

(No subject)

[William Delacre]

Alright, thabks !

And I guess if it’s a tool I need during runtime on the target, I add it in
the RDPENDS variable ?

Le ven. 27 juil. 2018 à 18:40, S. Lockwood-Childs <sjl@vctlabs.com> a
écrit :

> It depends on the role of the particular dependency:
>
> * tool you need to run during build             <-- native dependency
> * library you need to link against during build <-- target dependency
>
> --SJLC
>
> On Fri, Jul 27, 2018 at 06:25:27PM +0200, William Delacre wrote:
> > Okay, it makes sense!
> >
> > My question may seem stupid but then why don’t we always use ‘-native’
> for
> > the dependencies ?
> >
> > Is it because sometimes we know that the behavior of ‘foo’ and
> ‘foo-native’
> > would be the same, independently of the architecture ?
> >
> > William
> >
> > Le ven. 27 juil. 2018 à 18:16, Mark Asselstine <
> > mark.asselstine@windriver.com> a écrit :
> >
> > > On Friday, July 27, 2018 12:04:37 PM EDT William Delacre wrote:
> > > > Thanks a lot for the answer, it worked perfectly !
> > > >
> > > > There is just one point I don’t really understand : why do we need to
> > > add a
> > > > dependency to ‘python-incremental-NATIVE’ ?
> > > >
> > > > What would happen if I just add to the python-twisted recipe :
> > > >
> > > > DEPENDS += “${PYTHON_PN}-incremental“
> > >
> > > This would assume that python is completely arch independent, which it
> is
> > > not.
> > > Assume for example python-incremental had some C extensions, using
> DEPENDS
> > > would build them for the target arch yet possibly attempt to run them
> on
> > > your
> > > build host. -native takes care of this.
> > >
> > > Some may say this is a bit of a hack since the difference in ARCH
> *might*
> > > equate to a difference in behavior. But I have dealt with many python
> > > recipes
> > > and have yet to run into any scenario where this potential issue
> exists.
> > >
> > > At least that is what I can recall at the moment. Unfortunately I have
> > > forgotten some of the subtleties that might be in play.
> > >
> > > Mark
> > >
> > > >
> > > > William
> > > >
> > > > Le ven. 27 juil. 2018 à 17:03, Mark Asselstine <
> > > >
> > > > mark.asselstine@windriver.com> a écrit :
> > > > > On Thu, Jul 26, 2018 at 3:40 PM, Mark Asselstine
> > > > >
> > > > > <mark.asselstine@windriver.com> wrote:
> > > > > > On Mon, Jul 23, 2018 at 8:28 AM, William Delacre
> > > > > >
> > > > > > <williamdelacre@gmail.com> wrote:
> > > > > >> Hi ! :-)
> > > > > >>
> > > > > >> I’m facing issues when trying to run ‘bitbake python-twisted’
> > > > >
> > > > > (do_compile
> > > > >
> > > > > >> error)
> > > > > >>
> > > > > >> Log says :
> > > > > >> “Download error on https://pypi.python.org/simple/incremental/:
> > > [Errno
> > > > >
> > > > > -3]
> > > > >
> > > > > >> Temporary failure in name resolution
> > > > >
> > > > > With the additional info you sent me along with a second look at
> the
> > > > > error I can fairly confidently say I know what the issue is.
> > > > >
> > > > > Python, like some other languages (ruby, go...) will attempt to
> > > > > download dependencies/requirements if they are not present. This is
> > > > > done "outside" of the bitbake system and thus will ignore
> > > > > BB_NO_NETWORK and is generally a bad thing. It isn't quite host
> > > > > contamination but it is very similar. What we do with our python
> > > > > recipes in bitbake is review a python package's source setup.py,
> > > > > requirements.txt...files in order to determine what other python
> > > > > packages are needed, add them as RDEPENDS or similar in order to
> avoid
> > > > > the python attempting to complete a download such as this.
> > > > >
> > > > > In this case python-twisted 'requires' python-incremental but the
> > > > > Rocko version of the python-twisted recipe lacks the needed
> assignment
> > > > > to ensure this is available in the recipe sysroot and thus the
> > > > > attempted download.
> > > > >
> > > > > Cherry pick commit b08b570c8624303acbb6bb064a7bda466a679df4
> > > > > [python-twisted: avoid downloading build dependencies] to Rocko and
> > > > > you will be good to go. You should also follow up this thread with
> a
> > > > > request to have this commit put onto Rocko to avoid others hitting
> the
> > > > > same issue.
> > > > >
> > > > > Mark
> > > > >
> > > > > >> ............
> > > > > >>
> > > > > >> distutils.errors.DistutilsError : Could not find suitable
> > > distribution
> > > > >
> > > > > for
> > > > >
> > > > > >> Requirement.parse(‘incremental>=16.10.1’)”
> > > > > >>
> > > > > >> First of all I’m not connected to internet, so I’ve
> pre-downloaded
> > > all
> > > > >
> > > > > the
> > > > >
> > > > > >> required packages (twisted-17.9.0.tar.bz2 &
> > > incremental-17.5.0.tar.gz
> > > > >
> > > > > are
> > > > >
> > > > > >> present in my build/downloads folder)
> > > > > >>
> > > > > >> It’s the first time I have some “downloading issues” and I’m
> stuck
> > > on
> > > > > >> it
> > > > > >> for a few hours now..
> > > > > >>
> > > > > >> Any tips for me ?
> > > > > >
> > > > > > Check all aspects of what you have manually downloaded and
> populated
> > > > > > in your downloads. My guess is that a checksum or some other
> detail
> > > > > > isn't matching and it is rejecting what you have and thus
> attempting
> > > > > > to re-download the file.
> > > > > >
> > > > > > Mark
> > > > > >
> > > > > >> Thanks in advance !
> > > > > >> --
> > > > > >> _______________________________________________
> > > > > >> Openembedded-devel mailing list
> > > > > >> Openembedded-devel@lists.openembedded.org
> > > > > >>
> 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
>

(No subject)

[S. Lockwood-Childs]

It depends on the role of the particular dependency:

* tool you need to run during build             <-- native dependency
* library you need to link against during build <-- target dependency

--SJLC

On Fri, Jul 27, 2018 at 06:25:27PM +0200, William Delacre wrote:
> Okay, it makes sense!
> 
> My question may seem stupid but then why don’t we always use ‘-native’ for
> the dependencies ?
> 
> Is it because sometimes we know that the behavior of ‘foo’ and ‘foo-native’
> would be the same, independently of the architecture ?
> 
> William
> 
> Le ven. 27 juil. 2018 à 18:16, Mark Asselstine <
> mark.asselstine@windriver.com> a écrit :
> 
> > On Friday, July 27, 2018 12:04:37 PM EDT William Delacre wrote:
> > > Thanks a lot for the answer, it worked perfectly !
> > >
> > > There is just one point I don’t really understand : why do we need to
> > add a
> > > dependency to ‘python-incremental-NATIVE’ ?
> > >
> > > What would happen if I just add to the python-twisted recipe :
> > >
> > > DEPENDS += “${PYTHON_PN}-incremental“
> >
> > This would assume that python is completely arch independent, which it is
> > not.
> > Assume for example python-incremental had some C extensions, using DEPENDS
> > would build them for the target arch yet possibly attempt to run them on
> > your
> > build host. -native takes care of this.
> >
> > Some may say this is a bit of a hack since the difference in ARCH *might*
> > equate to a difference in behavior. But I have dealt with many python
> > recipes
> > and have yet to run into any scenario where this potential issue exists.
> >
> > At least that is what I can recall at the moment. Unfortunately I have
> > forgotten some of the subtleties that might be in play.
> >
> > Mark
> >
> > >
> > > William
> > >
> > > Le ven. 27 juil. 2018 à 17:03, Mark Asselstine <
> > >
> > > mark.asselstine@windriver.com> a écrit :
> > > > On Thu, Jul 26, 2018 at 3:40 PM, Mark Asselstine
> > > >
> > > > <mark.asselstine@windriver.com> wrote:
> > > > > On Mon, Jul 23, 2018 at 8:28 AM, William Delacre
> > > > >
> > > > > <williamdelacre@gmail.com> wrote:
> > > > >> Hi ! :-)
> > > > >>
> > > > >> I’m facing issues when trying to run ‘bitbake python-twisted’
> > > >
> > > > (do_compile
> > > >
> > > > >> error)
> > > > >>
> > > > >> Log says :
> > > > >> “Download error on https://pypi.python.org/simple/incremental/:
> > [Errno
> > > >
> > > > -3]
> > > >
> > > > >> Temporary failure in name resolution
> > > >
> > > > With the additional info you sent me along with a second look at the
> > > > error I can fairly confidently say I know what the issue is.
> > > >
> > > > Python, like some other languages (ruby, go...) will attempt to
> > > > download dependencies/requirements if they are not present. This is
> > > > done "outside" of the bitbake system and thus will ignore
> > > > BB_NO_NETWORK and is generally a bad thing. It isn't quite host
> > > > contamination but it is very similar. What we do with our python
> > > > recipes in bitbake is review a python package's source setup.py,
> > > > requirements.txt...files in order to determine what other python
> > > > packages are needed, add them as RDEPENDS or similar in order to avoid
> > > > the python attempting to complete a download such as this.
> > > >
> > > > In this case python-twisted 'requires' python-incremental but the
> > > > Rocko version of the python-twisted recipe lacks the needed assignment
> > > > to ensure this is available in the recipe sysroot and thus the
> > > > attempted download.
> > > >
> > > > Cherry pick commit b08b570c8624303acbb6bb064a7bda466a679df4
> > > > [python-twisted: avoid downloading build dependencies] to Rocko and
> > > > you will be good to go. You should also follow up this thread with a
> > > > request to have this commit put onto Rocko to avoid others hitting the
> > > > same issue.
> > > >
> > > > Mark
> > > >
> > > > >> ............
> > > > >>
> > > > >> distutils.errors.DistutilsError : Could not find suitable
> > distribution
> > > >
> > > > for
> > > >
> > > > >> Requirement.parse(‘incremental>=16.10.1’)”
> > > > >>
> > > > >> First of all I’m not connected to internet, so I’ve pre-downloaded
> > all
> > > >
> > > > the
> > > >
> > > > >> required packages (twisted-17.9.0.tar.bz2 &
> > incremental-17.5.0.tar.gz
> > > >
> > > > are
> > > >
> > > > >> present in my build/downloads folder)
> > > > >>
> > > > >> It’s the first time I have some “downloading issues” and I’m stuck
> > on
> > > > >> it
> > > > >> for a few hours now..
> > > > >>
> > > > >> Any tips for me ?
> > > > >
> > > > > Check all aspects of what you have manually downloaded and populated
> > > > > in your downloads. My guess is that a checksum or some other detail
> > > > > isn't matching and it is rejecting what you have and thus attempting
> > > > > to re-download the file.
> > > > >
> > > > > Mark
> > > > >
> > > > >> Thanks in advance !
> > > > >> --
> > > > >> _______________________________________________
> > > > >> Openembedded-devel mailing list
> > > > >> Openembedded-devel@lists.openembedded.org
> > > > >> 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

(No subject)

[Mark Asselstine]

On Friday, July 27, 2018 12:42:44 PM EDT William Delacre wrote:
> Alright, thabks !
> 
> And I guess if it’s a tool I need during runtime on the target, I add it in
> the RDPENDS variable ?

Correct.

Note as well that I did make a note of why the -native version of incremental 
was needed, to work around a circular dependency, as captured in the commit 
log.

In general with python we definitely make assumptions around arch independence 
and the strategy has survived most if not all we have thrown at it.

Mark

> 
> Le ven. 27 juil. 2018 à 18:40, S. Lockwood-Childs <sjl@vctlabs.com> a
> 
> écrit :
> > It depends on the role of the particular dependency:
> > 
> > * tool you need to run during build             <-- native dependency
> > * library you need to link against during build <-- target dependency
> > 
> > --SJLC
> > 
> > On Fri, Jul 27, 2018 at 06:25:27PM +0200, William Delacre wrote:
> > > Okay, it makes sense!
> > > 
> > > My question may seem stupid but then why don’t we always use ‘-native’
> > 
> > for
> > 
> > > the dependencies ?
> > > 
> > > Is it because sometimes we know that the behavior of ‘foo’ and
> > 
> > ‘foo-native’
> > 
> > > would be the same, independently of the architecture ?
> > > 
> > > William
> > > 
> > > Le ven. 27 juil. 2018 à 18:16, Mark Asselstine <
> > > 
> > > mark.asselstine@windriver.com> a écrit :
> > > > On Friday, July 27, 2018 12:04:37 PM EDT William Delacre wrote:
> > > > > Thanks a lot for the answer, it worked perfectly !
> > > > > 
> > > > > There is just one point I don’t really understand : why do we need
> > > > > to
> > > > 
> > > > add a
> > > > 
> > > > > dependency to ‘python-incremental-NATIVE’ ?
> > > > > 
> > > > > What would happen if I just add to the python-twisted recipe :
> > > > > 
> > > > > DEPENDS += “${PYTHON_PN}-incremental“
> > > > 
> > > > This would assume that python is completely arch independent, which it
> > 
> > is
> > 
> > > > not.
> > > > Assume for example python-incremental had some C extensions, using
> > 
> > DEPENDS
> > 
> > > > would build them for the target arch yet possibly attempt to run them
> > 
> > on
> > 
> > > > your
> > > > build host. -native takes care of this.
> > > > 
> > > > Some may say this is a bit of a hack since the difference in ARCH
> > 
> > *might*
> > 
> > > > equate to a difference in behavior. But I have dealt with many python
> > > > recipes
> > > > and have yet to run into any scenario where this potential issue
> > 
> > exists.
> > 
> > > > At least that is what I can recall at the moment. Unfortunately I have
> > > > forgotten some of the subtleties that might be in play.
> > > > 
> > > > Mark
> > > > 
> > > > > William
> > > > > 
> > > > > Le ven. 27 juil. 2018 à 17:03, Mark Asselstine <
> > > > > 
> > > > > mark.asselstine@windriver.com> a écrit :
> > > > > > On Thu, Jul 26, 2018 at 3:40 PM, Mark Asselstine
> > > > > > 
> > > > > > <mark.asselstine@windriver.com> wrote:
> > > > > > > On Mon, Jul 23, 2018 at 8:28 AM, William Delacre
> > > > > > > 
> > > > > > > <williamdelacre@gmail.com> wrote:
> > > > > > >> Hi ! :-)
> > > > > > >> 
> > > > > > >> I’m facing issues when trying to run ‘bitbake python-twisted’
> > > > > > 
> > > > > > (do_compile
> > > > > > 
> > > > > > >> error)
> > > > > > >> 
> > > > > > >> Log says :
> > > > 
> > > > > > >> “Download error on https://pypi.python.org/simple/incremental/:
> > > > [Errno
> > > > 
> > > > > > -3]
> > > > > > 
> > > > > > >> Temporary failure in name resolution
> > > > > > 
> > > > > > With the additional info you sent me along with a second look at
> > 
> > the
> > 
> > > > > > error I can fairly confidently say I know what the issue is.
> > > > > > 
> > > > > > Python, like some other languages (ruby, go...) will attempt to
> > > > > > download dependencies/requirements if they are not present. This
> > > > > > is
> > > > > > done "outside" of the bitbake system and thus will ignore
> > > > > > BB_NO_NETWORK and is generally a bad thing. It isn't quite host
> > > > > > contamination but it is very similar. What we do with our python
> > > > > > recipes in bitbake is review a python package's source setup.py,
> > > > > > requirements.txt...files in order to determine what other python
> > > > > > packages are needed, add them as RDEPENDS or similar in order to
> > 
> > avoid
> > 
> > > > > > the python attempting to complete a download such as this.
> > > > > > 
> > > > > > In this case python-twisted 'requires' python-incremental but the
> > > > > > Rocko version of the python-twisted recipe lacks the needed
> > 
> > assignment
> > 
> > > > > > to ensure this is available in the recipe sysroot and thus the
> > > > > > attempted download.
> > > > > > 
> > > > > > Cherry pick commit b08b570c8624303acbb6bb064a7bda466a679df4
> > > > > > [python-twisted: avoid downloading build dependencies] to Rocko
> > > > > > and
> > > > > > you will be good to go. You should also follow up this thread with
> > 
> > a
> > 
> > > > > > request to have this commit put onto Rocko to avoid others hitting
> > 
> > the
> > 
> > > > > > same issue.
> > > > > > 
> > > > > > Mark
> > > > > > 
> > > > > > >> ............
> > > > > > >> 
> > > > > > >> distutils.errors.DistutilsError : Could not find suitable
> > > > 
> > > > distribution
> > > > 
> > > > > > for
> > > > > > 
> > > > > > >> Requirement.parse(‘incremental>=16.10.1’)”
> > > > > > >> 
> > > > > > >> First of all I’m not connected to internet, so I’ve
> > 
> > pre-downloaded
> > 
> > > > all
> > > > 
> > > > > > the
> > > > > > 
> > > > > > >> required packages (twisted-17.9.0.tar.bz2 &
> > > > 
> > > > incremental-17.5.0.tar.gz
> > > > 
> > > > > > are
> > > > > > 
> > > > > > >> present in my build/downloads folder)
> > > > > > >> 
> > > > > > >> It’s the first time I have some “downloading issues” and I’m
> > 
> > stuck
> > 
> > > > on
> > > > 
> > > > > > >> it
> > > > > > >> for a few hours now..
> > > > > > >> 
> > > > > > >> Any tips for me ?
> > > > > > > 
> > > > > > > Check all aspects of what you have manually downloaded and
> > 
> > populated
> > 
> > > > > > > in your downloads. My guess is that a checksum or some other
> > 
> > detail
> > 
> > > > > > > isn't matching and it is rejecting what you have and thus
> > 
> > attempting
> > 
> > > > > > > to re-download the file.
> > > > > > > 
> > > > > > > Mark
> > > > > > > 
> > > > > > >> Thanks in advance !
> > > > > > >> --
> > > > > > >> _______________________________________________
> > > > > > >> Openembedded-devel mailing list
> > > > > > >> Openembedded-devel@lists.openembedded.org
> > 
> > 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

(No subject)

[William Delacre]

Le ven. 27 juil. 2018 à 18:40, S. Lockwood-Childs <sjl@vctlabs.com> a
écrit :

> It depends on the role of the particular dependency:
>
> * tool you need to run during build             <-- native dependency
> * library you need to link against during build <-- target dependency


Thanks for the precision :-)

My question may seem a bit stupid but how do you know which is which ?
Let’s say I want to write a recipe to install any specific software on my
target, how do I choose the dependencies ?
I have to refer to the software Makefile/CMakeList ?

William

>
>
> --SJLC
>
> On Fri, Jul 27, 2018 at 06:25:27PM +0200, William Delacre wrote:
> > Okay, it makes sense!
> >
> > My question may seem stupid but then why don’t we always use ‘-native’
> for
> > the dependencies ?
> >
> > Is it because sometimes we know that the behavior of ‘foo’ and
> ‘foo-native’
> > would be the same, independently of the architecture ?
> >
> > William
> >
> > Le ven. 27 juil. 2018 à 18:16, Mark Asselstine <
> > mark.asselstine@windriver.com> a écrit :
> >
> > > On Friday, July 27, 2018 12:04:37 PM EDT William Delacre wrote:
> > > > Thanks a lot for the answer, it worked perfectly !
> > > >
> > > > There is just one point I don’t really understand : why do we need to
> > > add a
> > > > dependency to ‘python-incremental-NATIVE’ ?
> > > >
> > > > What would happen if I just add to the python-twisted recipe :
> > > >
> > > > DEPENDS += “${PYTHON_PN}-incremental“
> > >
> > > This would assume that python is completely arch independent, which it
> is
> > > not.
> > > Assume for example python-incremental had some C extensions, using
> DEPENDS
> > > would build them for the target arch yet possibly attempt to run them
> on
> > > your
> > > build host. -native takes care of this.
> > >
> > > Some may say this is a bit of a hack since the difference in ARCH
> *might*
> > > equate to a difference in behavior. But I have dealt with many python
> > > recipes
> > > and have yet to run into any scenario where this potential issue
> exists.
> > >
> > > At least that is what I can recall at the moment. Unfortunately I have
> > > forgotten some of the subtleties that might be in play.
> > >
> > > Mark
> > >
> > > >
> > > > William
> > > >
> > > > Le ven. 27 juil. 2018 à 17:03, Mark Asselstine <
> > > >
> > > > mark.asselstine@windriver.com> a écrit :
> > > > > On Thu, Jul 26, 2018 at 3:40 PM, Mark Asselstine
> > > > >
> > > > > <mark.asselstine@windriver.com> wrote:
> > > > > > On Mon, Jul 23, 2018 at 8:28 AM, William Delacre
> > > > > >
> > > > > > <williamdelacre@gmail.com> wrote:
> > > > > >> Hi ! :-)
> > > > > >>
> > > > > >> I’m facing issues when trying to run ‘bitbake python-twisted’
> > > > >
> > > > > (do_compile
> > > > >
> > > > > >> error)
> > > > > >>
> > > > > >> Log says :
> > > > > >> “Download error on https://pypi.python.org/simple/incremental/:
> > > [Errno
> > > > >
> > > > > -3]
> > > > >
> > > > > >> Temporary failure in name resolution
> > > > >
> > > > > With the additional info you sent me along with a second look at
> the
> > > > > error I can fairly confidently say I know what the issue is.
> > > > >
> > > > > Python, like some other languages (ruby, go...) will attempt to
> > > > > download dependencies/requirements if they are not present. This is
> > > > > done "outside" of the bitbake system and thus will ignore
> > > > > BB_NO_NETWORK and is generally a bad thing. It isn't quite host
> > > > > contamination but it is very similar. What we do with our python
> > > > > recipes in bitbake is review a python package's source setup.py,
> > > > > requirements.txt...files in order to determine what other python
> > > > > packages are needed, add them as RDEPENDS or similar in order to
> avoid
> > > > > the python attempting to complete a download such as this.
> > > > >
> > > > > In this case python-twisted 'requires' python-incremental but the
> > > > > Rocko version of the python-twisted recipe lacks the needed
> assignment
> > > > > to ensure this is available in the recipe sysroot and thus the
> > > > > attempted download.
> > > > >
> > > > > Cherry pick commit b08b570c8624303acbb6bb064a7bda466a679df4
> > > > > [python-twisted: avoid downloading build dependencies] to Rocko and
> > > > > you will be good to go. You should also follow up this thread with
> a
> > > > > request to have this commit put onto Rocko to avoid others hitting
> the
> > > > > same issue.
> > > > >
> > > > > Mark
> > > > >
> > > > > >> ............
> > > > > >>
> > > > > >> distutils.errors.DistutilsError : Could not find suitable
> > > distribution
> > > > >
> > > > > for
> > > > >
> > > > > >> Requirement.parse(‘incremental>=16.10.1’)”
> > > > > >>
> > > > > >> First of all I’m not connected to internet, so I’ve
> pre-downloaded
> > > all
> > > > >
> > > > > the
> > > > >
> > > > > >> required packages (twisted-17.9.0.tar.bz2 &
> > > incremental-17.5.0.tar.gz
> > > > >
> > > > > are
> > > > >
> > > > > >> present in my build/downloads folder)
> > > > > >>
> > > > > >> It’s the first time I have some “downloading issues” and I’m
> stuck
> > > on
> > > > > >> it
> > > > > >> for a few hours now..
> > > > > >>
> > > > > >> Any tips for me ?
> > > > > >
> > > > > > Check all aspects of what you have manually downloaded and
> populated
> > > > > > in your downloads. My guess is that a checksum or some other
> detail
> > > > > > isn't matching and it is rejecting what you have and thus
> attempting
> > > > > > to re-download the file.
> > > > > >
> > > > > > Mark
> > > > > >
> > > > > >> Thanks in advance !
> > > > > >> --
> > > > > >> _______________________________________________
> > > > > >> Openembedded-devel mailing list
> > > > > >> Openembedded-devel@lists.openembedded.org
> > > > > >>
> 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
>

(No subject)

[Mark Asselstine]

On Tuesday, July 31, 2018 7:54:22 AM EDT William Delacre wrote:
> Le ven. 27 juil. 2018 à 18:40, S. Lockwood-Childs <sjl@vctlabs.com> a
> 
> écrit :
> > It depends on the role of the particular dependency:
> > 
> > * tool you need to run during build             <-- native dependency
> > * library you need to link against during build <-- target dependency
> 
> Thanks for the precision :-)
> 
> My question may seem a bit stupid but how do you know which is which ?
> Let’s say I want to write a recipe to install any specific software on my
> target, how do I choose the dependencies ?
> I have to refer to the software Makefile/CMakeList ?

It is not always easy to see via code inspection. I would suggest keep a 
second build for a different arch than your build host, possibly ARM. Start by 
using the non-native DEPENDS and only if there is an issue with the ARM build 
look at using -native for a DEPENDS.

To be honest I haven't had to worry about this too much as it is rare to run 
into issues.

Mark

> 
> William
> 
> > --SJLC
> > 
> > On Fri, Jul 27, 2018 at 06:25:27PM +0200, William Delacre wrote:
> > > Okay, it makes sense!
> > > 
> > > My question may seem stupid but then why don’t we always use ‘-native’
> > 
> > for
> > 
> > > the dependencies ?
> > > 
> > > Is it because sometimes we know that the behavior of ‘foo’ and
> > 
> > ‘foo-native’
> > 
> > > would be the same, independently of the architecture ?
> > > 
> > > William
> > > 
> > > Le ven. 27 juil. 2018 à 18:16, Mark Asselstine <
> > > 
> > > mark.asselstine@windriver.com> a écrit :
> > > > On Friday, July 27, 2018 12:04:37 PM EDT William Delacre wrote:
> > > > > Thanks a lot for the answer, it worked perfectly !
> > > > > 
> > > > > There is just one point I don’t really understand : why do we need
> > > > > to
> > > > 
> > > > add a
> > > > 
> > > > > dependency to ‘python-incremental-NATIVE’ ?
> > > > > 
> > > > > What would happen if I just add to the python-twisted recipe :
> > > > > 
> > > > > DEPENDS += “${PYTHON_PN}-incremental“
> > > > 
> > > > This would assume that python is completely arch independent, which it
> > 
> > is
> > 
> > > > not.
> > > > Assume for example python-incremental had some C extensions, using
> > 
> > DEPENDS
> > 
> > > > would build them for the target arch yet possibly attempt to run them
> > 
> > on
> > 
> > > > your
> > > > build host. -native takes care of this.
> > > > 
> > > > Some may say this is a bit of a hack since the difference in ARCH
> > 
> > *might*
> > 
> > > > equate to a difference in behavior. But I have dealt with many python
> > > > recipes
> > > > and have yet to run into any scenario where this potential issue
> > 
> > exists.
> > 
> > > > At least that is what I can recall at the moment. Unfortunately I have
> > > > forgotten some of the subtleties that might be in play.
> > > > 
> > > > Mark
> > > > 
> > > > > William
> > > > > 
> > > > > Le ven. 27 juil. 2018 à 17:03, Mark Asselstine <
> > > > > 
> > > > > mark.asselstine@windriver.com> a écrit :
> > > > > > On Thu, Jul 26, 2018 at 3:40 PM, Mark Asselstine
> > > > > > 
> > > > > > <mark.asselstine@windriver.com> wrote:
> > > > > > > On Mon, Jul 23, 2018 at 8:28 AM, William Delacre
> > > > > > > 
> > > > > > > <williamdelacre@gmail.com> wrote:
> > > > > > >> Hi ! :-)
> > > > > > >> 
> > > > > > >> I’m facing issues when trying to run ‘bitbake python-twisted’
> > > > > > 
> > > > > > (do_compile
> > > > > > 
> > > > > > >> error)
> > > > > > >> 
> > > > > > >> Log says :
> > > > 
> > > > > > >> “Download error on https://pypi.python.org/simple/incremental/:
> > > > [Errno
> > > > 
> > > > > > -3]
> > > > > > 
> > > > > > >> Temporary failure in name resolution
> > > > > > 
> > > > > > With the additional info you sent me along with a second look at
> > 
> > the
> > 
> > > > > > error I can fairly confidently say I know what the issue is.
> > > > > > 
> > > > > > Python, like some other languages (ruby, go...) will attempt to
> > > > > > download dependencies/requirements if they are not present. This
> > > > > > is
> > > > > > done "outside" of the bitbake system and thus will ignore
> > > > > > BB_NO_NETWORK and is generally a bad thing. It isn't quite host
> > > > > > contamination but it is very similar. What we do with our python
> > > > > > recipes in bitbake is review a python package's source setup.py,
> > > > > > requirements.txt...files in order to determine what other python
> > > > > > packages are needed, add them as RDEPENDS or similar in order to
> > 
> > avoid
> > 
> > > > > > the python attempting to complete a download such as this.
> > > > > > 
> > > > > > In this case python-twisted 'requires' python-incremental but the
> > > > > > Rocko version of the python-twisted recipe lacks the needed
> > 
> > assignment
> > 
> > > > > > to ensure this is available in the recipe sysroot and thus the
> > > > > > attempted download.
> > > > > > 
> > > > > > Cherry pick commit b08b570c8624303acbb6bb064a7bda466a679df4
> > > > > > [python-twisted: avoid downloading build dependencies] to Rocko
> > > > > > and
> > > > > > you will be good to go. You should also follow up this thread with
> > 
> > a
> > 
> > > > > > request to have this commit put onto Rocko to avoid others hitting
> > 
> > the
> > 
> > > > > > same issue.
> > > > > > 
> > > > > > Mark
> > > > > > 
> > > > > > >> ............
> > > > > > >> 
> > > > > > >> distutils.errors.DistutilsError : Could not find suitable
> > > > 
> > > > distribution
> > > > 
> > > > > > for
> > > > > > 
> > > > > > >> Requirement.parse(‘incremental>=16.10.1’)”
> > > > > > >> 
> > > > > > >> First of all I’m not connected to internet, so I’ve
> > 
> > pre-downloaded
> > 
> > > > all
> > > > 
> > > > > > the
> > > > > > 
> > > > > > >> required packages (twisted-17.9.0.tar.bz2 &
> > > > 
> > > > incremental-17.5.0.tar.gz
> > > > 
> > > > > > are
> > > > > > 
> > > > > > >> present in my build/downloads folder)
> > > > > > >> 
> > > > > > >> It’s the first time I have some “downloading issues” and I’m
> > 
> > stuck
> > 
> > > > on
> > > > 
> > > > > > >> it
> > > > > > >> for a few hours now..
> > > > > > >> 
> > > > > > >> Any tips for me ?
> > > > > > > 
> > > > > > > Check all aspects of what you have manually downloaded and
> > 
> > populated
> > 
> > > > > > > in your downloads. My guess is that a checksum or some other
> > 
> > detail
> > 
> > > > > > > isn't matching and it is rejecting what you have and thus
> > 
> > attempting
> > 
> > > > > > > to re-download the file.
> > > > > > > 
> > > > > > > Mark
> > > > > > > 
> > > > > > >> Thanks in advance !
> > > > > > >> --
> > > > > > >> _______________________________________________
> > > > > > >> Openembedded-devel mailing list
> > > > > > >> Openembedded-devel@lists.openembedded.org
> > 
> > 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

(No subject)

[S. Lockwood-Childs]

On Tue, Jul 31, 2018 at 10:30:02AM -0400, Mark Asselstine wrote:
> On Tuesday, July 31, 2018 7:54:22 AM EDT William Delacre wrote:
> > Le ven. 27 juil. 2018 à 18:40, S. Lockwood-Childs <sjl@vctlabs.com> a
> > 
> > écrit :
> > > It depends on the role of the particular dependency:
> > > 
> > > * tool you need to run during build             <-- native dependency
> > > * library you need to link against during build <-- target dependency
> > 
> > Thanks for the precision :-)
> > 
> > My question may seem a bit stupid but how do you know which is which ?
> > Let’s say I want to write a recipe to install any specific software on my
> > target, how do I choose the dependencies ?
> > I have to refer to the software Makefile/CMakeList ?
> 
> It is not always easy to see via code inspection. I would suggest keep a 
> second build for a different arch than your build host, possibly ARM. Start by 
> using the non-native DEPENDS and only if there is an issue with the ARM build 
> look at using -native for a DEPENDS.
> 
> To be honest I haven't had to worry about this too much as it is rare to run 
> into issues.

Yes target build dependencies are more common, so this approach of defaulting
to target rather than native does make sense.

My other advice is to start out by reviewing the build instructions in the
README / INSTALL docs for the software package; if that package requires some
non-standard external build tool ("non-standard" meaning other than 
autotools / make etc) that would need to be listed as native dependency, 
that tool really should be mentioned in the build instructions.

--SJLC

(No subject)

[William Delacre]

Le mar. 31 juil. 2018 à 20:42, S. Lockwood-Childs <sjl@vctlabs.com> a
écrit :

> On Tue, Jul 31, 2018 at 10:30:02AM -0400, Mark Asselstine wrote:
> > On Tuesday, July 31, 2018 7:54:22 AM EDT William Delacre wrote:
> > > Le ven. 27 juil. 2018 à 18:40, S. Lockwood-Childs <sjl@vctlabs.com> a
> > >
> > > écrit :
> > > > It depends on the role of the particular dependency:
> > > >
> > > > * tool you need to run during build             <-- native dependency
> > > > * library you need to link against during build <-- target dependency
> > >
> > > Thanks for the precision :-)
> > >
> > > My question may seem a bit stupid but how do you know which is which ?
> > > Let’s say I want to write a recipe to install any specific software on
> my
> > > target, how do I choose the dependencies ?
> > > I have to refer to the software Makefile/CMakeList ?
> >
> > It is not always easy to see via code inspection. I would suggest keep a
> > second build for a different arch than your build host, possibly ARM.
> Start by
> > using the non-native DEPENDS and only if there is an issue with the ARM
> build
> > look at using -native for a DEPENDS.
> >
> > To be honest I haven't had to worry about this too much as it is rare to
> run
> > into issues.
>
> Yes target build dependencies are more common, so this approach of
> defaulting
> to target rather than native does make sense.
>
> My other advice is to start out by reviewing the build instructions in the
> README / INSTALL docs for the software package; if that package requires
> some
> non-standard external build tool ("non-standard" meaning other than
> autotools / make etc) that would need to be listed as native dependency,
> that tool really should be mentioned in the build instructions.
>
> --SJLC


This is exactly what I needed to know ! Thanks you all a lot !

>
>

(No subject)

[Ankit Navik]

[-- Attachment #1: Type: text/plain, Size: 260 bytes --]

Hello,

I am facing an issue for my recipe during compilation.
Error:
|   The C compiler
|
|     "/usr/bin/clang-4.0"
|
|   is not able to compile a simple test program.

log file is attached.
I would appreciate any suggestions.

Regards,
Ankit

[-- Attachment #2: log.do_compile.5550 --]
[-- Type: application/octet-stream, Size: 12101 bytes --]

DEBUG: Executing shell function do_compile
NOTE: make -j 8 package
[  0%] Built target igdrcl_lib_release_sharings_enable
[  1%] Built target elflib
[  1%] Built target gmock-gtest
[  1%] Performing configure step for 'cclang'
[  1%] Built target biksim
[  2%] Built target igfx_gmmumd_dll
[  3%] Built target gmm_umd
[  5%] Built target igfx_gmmumd_excite
CMake Deprecation Warning at CMakeLists.txt:15 (cmake_policy):
  The OLD behavior for policy CMP0051 will be removed from a future version
  of CMake.

  The cmake-policies(7) manual explains that the OLD behaviors of all
  policies are deprecated and that a policy should be set to OLD only under
  specific short-term circumstances.  Projects should be ported to the NEW
  behavior and not rely on setting a policy to OLD.


[  6%] Built target igfxgmmumd
[  6%] Built target LLVMDemangle
[  6%] Built target LLVMTableGen
[  6%] Built target check_headers
[  6%] Building custom target for Metadata Framework
[  6%] Built target MDAutogen
[  6%] Tablegenning GenISAIntrinsics.
[  7%] Built target obj.llvm-tblgen
[  7%] Built target GenISAIntrinsicsTablegen
[ 11%] Built target LLVMSupport
[ 12%] Built target GEDLibrary
[ 13%] Built target IGA_OLIB
[ 13%] Built target builtins_sources
[ 13%] Built target LLVMMCParser
[ 13%] Built target igdrcl_lib_mockable_sharings_enable
[ 16%] Built target SPIRV-Tools
[ 18%] Built target LLVMMC
[ 18%] Built target igdrcl_libult_cs
[ 20%] Built target igdrcl_libult
[ 20%] Built target test_dynamic_lib
[ 20%] Built target elflib_tests
[ 20%] Built target mock_gmm
[ 20%] Built target cloc_segfault_test
[ 20%] Built target cloc
[ 20%] Built target igdrcl_mocks
[ 20%] Built target igdrcl_libult_env
[ 20%] Built target LocalScheduler
[ 21%] Built target GMMULT
[ 21%] Built target IGA_SLIB
[ 21%] Built target IGA_DLL
Running cloc_segfault_test
[ 22%] Built target IGA_ENC_LIB
[ 23%] Built target cloc_tests
/bin/sh: /home/ank/open-source-yocto/poky/build/tmp/work/corei7-64-poky-linux/compute-runtime/git-r0/build/bin/cloc_segfault_test: No such file or directory
make[2]: *** [run_cloc_segfault_test] Error 127
make[1]: *** [unit_tests/offline_compiler/segfault_test/CMakeFiles/run_cloc_segfault_test.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
Scanning dependencies of target Run_ULT
running ULTs
Scanning dependencies of target llvm-tblgen
[ 23%] Linking CXX executable ../../bin/llvm-tblgen
/bin/sh: ../../../../bin/GMMULT: No such file or directory
make[2]: *** [Run_ULT] Error 127
make[1]: *** [gmmlib/Source/GmmLib/ULT/CMakeFiles/Run_ULT.dir/all] Error 2
[ 31%] Built target igdrcl_lib_mockable
[ 40%] Built target igdrcl_lib_release
Scanning dependencies of target GenX_IR
[ 40%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/BinaryCISAEmission.cpp.o
[ 40%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/BinaryEncoding.cpp.o
[ 40%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/BinaryEncodingIGA.cpp.o
[ 40%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/Common_BinaryEncoding.cpp.o
[ 40%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/BinaryEncodingCNL.cpp.o
[ 40%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/BuildCISAIRImpl.cpp.o
[ 40%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/BuildIRImpl.cpp.o
[ 40%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/ByteCodeReaderNG.cpp.o
-- The C compiler identification is Clang 4.0.1
[ 40%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/DebugInfo.cpp.o
[ 40%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/FlowGraph.cpp.o
-- The CXX compiler identification is Clang 4.0.1
-- The ASM compiler identification is unknown
-- Found assembler: /usr/bin/clang-4.0
[ 40%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/CFGStructurizer.cpp.o
[ 40%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/Gen4_IR.cpp.o
-- Check for working C compiler: /usr/bin/clang-4.0
-- Check for working C compiler: /usr/bin/clang-4.0 -- broken
CMake Error at /home/ank/open-source-yocto/poky/build/tmp/work/corei7-64-poky-linux/compute-runtime/git-r0/recipe-sysroot-native/usr/share/cmake-3.12/Modules/CMakeTestCCompiler.cmake:52 (message):
  The C compiler

    "/usr/bin/clang-4.0"

  is not able to compile a simple test program.

  It fails with the following output:

    Change Dir: /home/ank/open-source-yocto/poky/build/tmp/work/corei7-64-poky-linux/compute-runtime/git-r0/build/igc/IGC/BiFModule/clang_build/src/CMakeFiles/CMakeTmp
    
    Run Build Command:"/home/ank/open-source-yocto/poky/build/tmp/hosttools/make" "cmTC_6d4df/fast"
    make[3]: Entering directory `/home/ank/open-source-yocto/poky/build/tmp/work/corei7-64-poky-linux/compute-runtime/git-r0/build/igc/IGC/BiFModule/clang_build/src/CMakeFiles/CMakeTmp'
    make -f CMakeFiles/cmTC_6d4df.dir/build.make CMakeFiles/cmTC_6d4df.dir/build
    make[4]: Entering directory `/home/ank/open-source-yocto/poky/build/tmp/work/corei7-64-poky-linux/compute-runtime/git-r0/build/igc/IGC/BiFModule/clang_build/src/CMakeFiles/CMakeTmp'
    Building C object CMakeFiles/cmTC_6d4df.dir/testCCompiler.c.o
    /usr/bin/clang-4.0   -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/home/ank/open-source-yocto/poky/build/tmp/work/corei7-64-poky-linux/compute-runtime/git-r0=/usr/src/debug/compute-runtime/git-r0 -fdebug-prefix-map=/home/ank/open-source-yocto/poky/build/tmp/work/corei7-64-poky-linux/compute-runtime/git-r0/recipe-sysroot= -fdebug-prefix-map=/home/ank/open-source-yocto/poky/build/tmp/work/corei7-64-poky-linux/compute-runtime/git-r0/recipe-sysroot-native=   -m64 -march=nehalem -mtune=generic -mfpmath=sse -msse4.2 -fstack-protector-strong  -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security  --sysroot=/home/ank/open-source-yocto/poky/build/tmp/work/corei7-64-poky-linux/compute-runtime/git-r0/recipe-sysroot    -o CMakeFiles/cmTC_6d4df.dir/testCCompiler.c.o   -c /home/ank/open-source-yocto/poky/build/tmp/work/corei7-64-poky-linux/compute-runtime/git-r0/build/igc/IGC/BiFModule/clang_build/src/CMakeFiles/CMakeTmp/testCCompiler.c
    Linking C executable cmTC_6d4df
    /home/ank/open-source-yocto/poky/build/tmp/work/corei7-64-poky-linux/compute-runtime/git-r0/recipe-sysroot-native/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_6d4df.dir/link.txt --verbose=1
    /usr/bin/clang-4.0 -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/home/ank/open-source-yocto/poky/build/tmp/work/corei7-64-poky-linux/compute-runtime/git-r0=/usr/src/debug/compute-runtime/git-r0 -fdebug-prefix-map=/home/ank/open-source-yocto/poky/build/tmp/work/corei7-64-poky-linux/compute-runtime/git-r0/recipe-sysroot= -fdebug-prefix-map=/home/ank/open-source-yocto/poky/build/tmp/work/corei7-64-poky-linux/compute-runtime/git-r0/recipe-sysroot-native=   -m64 -march=nehalem -mtune=generic -mfpmath=sse -msse4.2 -fstack-protector-strong  -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security  --sysroot=/home/ank/open-source-yocto/poky/build/tmp/work/corei7-64-poky-linux/compute-runtime/git-r0/recipe-sysroot   -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -fstack-protector-strong -Wl,-z,relro,-z,now  CMakeFiles/cmTC_6d4df.dir/testCCompiler.c.o  -o cmTC_6d4df 
    /usr/bin/ld: /home/ank/open-source-yocto/poky/build/tmp/work/corei7-64-poky-linux/compute-runtime/git-r0/recipe-sysroot/usr/lib/crt1.o: unrecognized relocation (0x29) in section `.text'
    /usr/bin/ld: final link failed: Bad value
    clang: error: linker command failed with exit code 1 (use -v to see invocation)
    make[4]: *** [cmTC_6d4df] Error 1
    make[4]: Leaving directory `/home/ank/open-source-yocto/poky/build/tmp/work/corei7-64-poky-linux/compute-runtime/git-r0/build/igc/IGC/BiFModule/clang_build/src/CMakeFiles/CMakeTmp'
    make[3]: *** [cmTC_6d4df/fast] Error 2
    make[3]: Leaving directory `/home/ank/open-source-yocto/poky/build/tmp/work/corei7-64-poky-linux/compute-runtime/git-r0/build/igc/IGC/BiFModule/clang_build/src/CMakeFiles/CMakeTmp'
    

  

  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  CMakeLists.txt:47 (project)


-- Configuring incomplete, errors occurred!
See also "/home/ank/open-source-yocto/poky/build/tmp/work/corei7-64-poky-linux/compute-runtime/git-r0/build/igc/IGC/BiFModule/clang_build/src/CMakeFiles/CMakeOutput.log".
See also "/home/ank/open-source-yocto/poky/build/tmp/work/corei7-64-poky-linux/compute-runtime/git-r0/build/igc/IGC/BiFModule/clang_build/src/CMakeFiles/CMakeError.log".
make[2]: *** [igc/IGC/BiFModule/clang_build/src/src/cclang-stamp/cclang-configure] Error 1
make[1]: *** [igc/IGC/BiFModule/clang_build/CMakeFiles/cclang.dir/all] Error 2
[ 40%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/GraphColor.cpp.o
[ 40%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/HWConformity.cpp.o
[ 40%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/SendFusion.cpp.o
[ 40%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/LocalDataflow.cpp.o
[ 40%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/LocalRA.cpp.o
[ 40%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/Lowered_IR.cpp.o
[ 40%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/main.cpp.o
[ 40%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/Optimizer.cpp.o
[ 40%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/PhyRegCompute.cpp.o
[ 40%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/PhyRegUsage.cpp.o
[ 40%] Built target llvm-tblgen
[ 40%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/ReduceExecSize.cpp.o
[ 40%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/RegAlloc.cpp.o
[ 41%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/SpillCode.cpp.o
[ 41%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/SpillManagerGMRF.cpp.o
[ 41%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/TranslationInterface.cpp.o
[ 41%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/VISAKernelImpl.cpp.o
[ 41%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/G4Verifier.cpp.o
[ 41%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/LVN.cpp.o
[ 41%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/ifcvt.cpp.o
[ 41%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/PreDefinedVars.cpp.o
[ 41%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/SpillCleanup.cpp.o
[ 41%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/Rematerialization.cpp.o
[ 41%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/RPE.cpp.o
[ 41%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/Common_ISA_framework.cpp.o
[ 41%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/Common_ISA_util.cpp.o
[ 41%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/IsaDescription.cpp.o
[ 41%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/IsaDisassembly.cpp.o
[ 41%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/IsaVerification.cpp.o
[ 41%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/Common_ISA.cpp.o
[ 41%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/visaBuilder_export.cpp.o
[ 41%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/Arena.cpp.o
[ 41%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/common.cpp.o
[ 41%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/Mem_Manager.cpp.o
[ 41%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/Option.cpp.o
[ 41%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/BitSet.cpp.o
[ 41%] Building CXX object igc/IGC/visa/CMakeFiles/GenX_IR.dir/Timer.cpp.o
[ 41%] Linking CXX static library igfxcmjit64.a
[ 41%] Built target GenX_IR
make: *** [all] Error 2
ERROR: oe_runmake failed
WARNING: /home/ank/open-source-yocto/poky/build/tmp/work/corei7-64-poky-linux/compute-runtime/git-r0/temp/run.do_compile.5550:1 exit 1 from 'exit 1'
ERROR: Function failed: do_compile (log file is located at /home/ank/open-source-yocto/poky/build/tmp/work/corei7-64-poky-linux/compute-runtime/git-r0/temp/log.do_compile.5550)