From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-ew0-f47.google.com ([209.85.215.47]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1Qqibt-00083k-0z for openembedded-devel@lists.openembedded.org; Tue, 09 Aug 2011 11:28:29 +0200 Received: by ewy5 with SMTP id 5so1097192ewy.6 for ; Tue, 09 Aug 2011 02:24:00 -0700 (PDT) Received: by 10.213.102.72 with SMTP id f8mr1388226ebo.32.1312881836786; Tue, 09 Aug 2011 02:23:56 -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 e9sm2910596eeb.54.2011.08.09.02.23.55 (version=SSLv3 cipher=OTHER); Tue, 09 Aug 2011 02:23:55 -0700 (PDT) Message-ID: <4E40FCA9.7060204@dresearch-fe.de> Date: Tue, 09 Aug 2011 11:23:53 +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@lists.openembedded.org References: <4E3A3C4B.8040208@dresearch-fe.de> <4E3B9812.9010002@dresearch-fe.de> <4E3ECD6E.7000201@dresearch-fe.de> In-Reply-To: X-Enigmail-Version: 1.2 Subject: Re: [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: Tue, 09 Aug 2011 09:28:29 -0000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit On 07.08.2011 22:46, Tom Rini wrote: > On Sun, Aug 7, 2011 at 10:37 AM, Steffen Sledz wrote: >> Am 05.08.2011 09:13, schrieb Steffen Sledz: >>> On 04.08.2011 08:29, Steffen Sledz wrote: >>>> 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. >>> >>> I made some research in this and there is something i do not understand. >>> >>> The task-depends.dot generated by bitbake -g (says >>> >>> "console-image.do_rootfs" [label="console-image do_rootfs\n0:1.0-r0\n/home/sledz/work/angstrom-setup-scripts/sources/openembedded/recipes/images/console-image.bb"] >>> "console-image.do_rootfs" -> "lzo-native.do_populate_sysroot" >>> "console-image.do_rootfs" -> "bluez4.do_populate_sysroot" >>> ... >>> >>> So do_rootfs depends only on do_populate_sysroot stages. But the do_rootfs stage itself uses opkg to install the packages into the image. >>> >>> In my understanding this means that all the ipk files need to be available. But this is not guaranteed by the reported dependencies. >>> >>> A misunderstanding of mine? Or a bug? >> >> Ping! >> >> Did everyone read my message? >> >> If it really is a misunderstanding of mine, please let me know. But if i'm right this seems to be a critical problem. > > It sounds both strange and a correct reading of the task lists, iirc. > Did we fix this in oe.dev perhaps and just need to pull a change over? The mentioned dependency problem was a misinterpretation of the task-depends.dot. Aside from the do_populate_sysroot there are the following additional dependencies: "console-image.do_rootfs" -> "console-image.do_package_update_index_ipk" ... "console-image.do_package_update_index_ipk" -> "gcc-cross.do_package_write_ipk" ... "gcc-cross.do_package_write_ipk" -> "gcc-cross.do_package" The problem seems to be located more likely somewhere inside the gcc-4.3.3-r24.1/gcc-cross-4.3.3-r24.2 recipes. There seems to be a confusion between those which leads to undetermined results. E.g. the content of tmp.6/work/armv5te-angstrom-linux-gnueabi/gcc-cross-4.3.3-r24.2/temp/log.do_package_write_ipk.22477 is: ------------------------>snip<------------------------ Packaged contents of libstdc++-dev into /home/sledz/work/HydraIP/OE/tmp.6/deploy/glibc/ipk/armv5te/libstdc++-dev_4.3.3-r24.1.6_armv5te.ipk Packaged contents of libgcc-dev into /home/sledz/work/HydraIP/OE/tmp.6/deploy/glibc/ipk/armv5te/libgcc-dev_4.3.3-r24.1.6_armv5te.ipk ------------------------>snip<------------------------ The do_package_write_ipk generates ipk-file with *r24.1.6* (which is the PR of gcc) and not *r24.2.6* (which is the PR of gcc). BTW: Which of the two recipes (gcc/gcc-cross) should provide the libgcc ipk (in my case none of it did)? Steffen -- 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