From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-fx0-f47.google.com ([209.85.161.47]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1QorVH-0003FH-Mz for openembedded-devel@lists.openembedded.org; Thu, 04 Aug 2011 08:34:01 +0200 Received: by fxg11 with SMTP id 11so482214fxg.6 for ; Wed, 03 Aug 2011 23:29:36 -0700 (PDT) Received: by 10.204.152.205 with SMTP id h13mr116821bkw.314.1312439374114; Wed, 03 Aug 2011 23:29:34 -0700 (PDT) Received: from fensuse.internal.dresearch-fe.de (pd95cb174.dip0.t-ipconnect.de [217.92.177.116]) by mx.google.com with ESMTPS id g11sm431139bku.49.2011.08.03.23.29.32 (version=SSLv3 cipher=OTHER); Wed, 03 Aug 2011 23:29:33 -0700 (PDT) Message-ID: <4E3A3C4B.8040208@dresearch-fe.de> Date: Thu, 04 Aug 2011 08:29:31 +0200 From: Steffen Sledz User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20110624 Thunderbird/5.0 MIME-Version: 1.0 To: openembedded-devel X-Enigmail-Version: 1.2 Subject: [2011.03-maintenance] unsatisfied dependencies to libgcc X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: openembedded-devel@lists.openembedded.org List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Aug 2011 06:34:01 -0000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit In the last days we switched our local development from an older oe-dev master to 2011.03-maintenance branch and hit an annoying problem. The test builds on various developer machines were successful but the build on our continuous integration server (with exactly the same scripting) ended up with a lot of | * satisfy_dependencies_for: Cannot satisfy the following dependencies for lighttpd: | * libstdc++6 (>= 4.3.3) * libgcc1 (>= 4.3.3) * libgcc1 (>= 4.3.3) * | * opkg_install_cmd: Cannot install package lighttpd. errors. After some searching we found that there was no libgcc1_4.3.3-r24.2.6_armv5te.ipk in the deploy area. I'm not sure which package should produce this but i guess it should come from gcc-cross-4.3.3 (because its recipe version is r24.2.6 in opposite to gcc-4.3.3 r24.1.6). Looking into the log i hit the fact that the do_rootfs stage for the image was started *before* the do_package_stage of gcc-cross_4.3.3.bb was succeeded. Any ideas? PS: Bitbaking gcc-cross explicitly before bitbaking the image wors as a workaround for us at the moment. -- DResearch Fahrzeugelektronik GmbH Otto-Schmirgal-Str. 3, 10319 Berlin, Germany Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de Fax: +49 30 515932-299 Geschäftsführer: Dr. Michael Weber, Werner Mögle; Amtsgericht Berlin Charlottenburg; HRB 130120 B; Ust.-IDNr. DE273952058