<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div><span><br></span></div><div>unsubscribe</div> <div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt; "> <div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt; "> <div dir="ltr"> <font size="2" face="Arial"> <hr size="1"> <b><span style="font-weight:bold;">From:</span></b> "yocto-request@yoctoproject.org" <yocto-request@yoctoproject.org><br> <b><span style="font-weight: bold;">To:</span></b> yocto@yoctoproject.org <br> <b><span style="font-weight: bold;">Sent:</span></b> Sunday, 16 September 2012, 20:00<br> <b><span style="font-weight: bold;">Subject:</span></b> yocto Digest, Vol 24, Issue 66<br> </font> </div> <br>Send yocto mailing list submissions to<br> <a ymailto="mailto:yocto@yoctoproject.org"
href="mailto:yocto@yoctoproject.org">yocto@yoctoproject.org</a><br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> <a href="https://lists.yoctoproject.org/listinfo/yocto" target="_blank">https://lists.yoctoproject.org/listinfo/yocto</a><br>or, via email, send a message with subject or body 'help' to<br> <a ymailto="mailto:yocto-request@yoctoproject.org" href="mailto:yocto-request@yoctoproject.org">yocto-request@yoctoproject.org</a><br><br>You can reach the person managing the list at<br> <a ymailto="mailto:yocto-owner@yoctoproject.org" href="mailto:yocto-owner@yoctoproject.org">yocto-owner@yoctoproject.org</a><br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of yocto digest..."<br><br><br>Today's Topics:<br><br> 1. Re: Dependency walk for busybox recipe (Khem Raj)<br> 2. Re: Forcing link order for autotools recipe
[SOLVED] (Chris Tapp)<br> 3. Re: Dependency walk for busybox recipe (Elvis Dowson)<br> 4. Re: All kernel modules being built and shipped in<br> images/modules-*.tgz (Elvis Dowson)<br> 5. Re: Dependency walk for busybox recipe (Paul Eggleton)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Sat, 15 Sep 2012 20:54:56 -0700<br>From: Khem Raj <<a ymailto="mailto:raj.khem@gmail.com" href="mailto:raj.khem@gmail.com">raj.khem@gmail.com</a>><br>To: Elvis Dowson <<a ymailto="mailto:elvis.dowson@gmail.com" href="mailto:elvis.dowson@gmail.com">elvis.dowson@gmail.com</a>><br>Cc: Yocto Discussion Mailing List <<a ymailto="mailto:yocto@yoctoproject.org" href="mailto:yocto@yoctoproject.org">yocto@yoctoproject.org</a>><br>Subject: Re: [yocto] Dependency walk for busybox recipe<br>Message-ID:<br> <<a
ymailto="mailto:CAMKF1sr9zgFJMrhBM_xdVPMM_zhnQCzjxYanub6O7NFG4w1Ohg@mail.gmail.com" href="mailto:CAMKF1sr9zgFJMrhBM_xdVPMM_zhnQCzjxYanub6O7NFG4w1Ohg@mail.gmail.com">CAMKF1sr9zgFJMrhBM_xdVPMM_zhnQCzjxYanub6O7NFG4w1Ohg@mail.gmail.com</a>><br>Content-Type: text/plain; charset=UTF-8<br><br>On Sat, Sep 15, 2012 at 10:59 AM, Elvis Dowson <<a ymailto="mailto:elvis.dowson@gmail.com" href="mailto:elvis.dowson@gmail.com">elvis.dowson@gmail.com</a>> wrote:<br>><br>><br>> So I added busybox-1.19.4 recipe back into my poky master branch, and the resulting size of the busybox-1.19.4 /bin/busybox or /bin/sh executable is 604.2 kb.<br><br>make sure that .config of busybox has not changed even if you have<br>same version backported<br><br><br>------------------------------<br><br>Message: 2<br>Date: Sun, 16 Sep 2012 11:08:37 +0100<br>From: Chris Tapp <<a ymailto="mailto:opensource@keylevel.com"
href="mailto:opensource@keylevel.com">opensource@keylevel.com</a>><br>To: "<a ymailto="mailto:yocto@yoctoproject.org" href="mailto:yocto@yoctoproject.org">yocto@yoctoproject.org</a> Project" <<a ymailto="mailto:yocto@yoctoproject.org" href="mailto:yocto@yoctoproject.org">yocto@yoctoproject.org</a>><br>Subject: Re: [yocto] Forcing link order for autotools recipe [SOLVED]<br>Message-ID: <<a ymailto="mailto:B130E0AD-EF24-4774-9671-6EC9C8B03EDE@keylevel.com" href="mailto:B130E0AD-EF24-4774-9671-6EC9C8B03EDE@keylevel.com">B130E0AD-EF24-4774-9671-6EC9C8B03EDE@keylevel.com</a>><br>Content-Type: text/plain; charset=us-ascii<br><br>On 16 Sep 2012, at 00:59, Chris Tapp wrote:<br><br>> I've got a recipe that uses autotools. It builds ok under Poky, but if I try to build it on my host (e.g. when developing) then it fails to build with lots of 'symbol not found' link errors related to libs that are on the system and which are in the gcc lib search
path.<br>> <br>> I've finally tracked this down to link order. The final command is of the form:<br>> <br>> g++ -lGL -lcurl -o binary a.o b.o<br>> <br>> If I change this to:<br>> <br>> g++ -o binary a.o b.o -lGL -lcurl<br>> <br>> then it builds ok.<br>> <br>> Stranger still is the original form works fine on another system (older Ubuntu). The ld versions are different (2.21.53 on the one that fails, 2.20.1 on the one that works).<br>> <br>> Can I get autotools to always link the libraries last?<br><br><br>Turns out there was a problem with one of my makefiles - it was using LDFLAGS to add the libs when it should have used LDADD (which puts them at the end of the command line).<br><br>That'll teach me to blindly copy from else where ;-) Strange it's worked up till now...<br><br>Chris Tapp<br><br><a ymailto="mailto:opensource@keylevel.com"
href="mailto:opensource@keylevel.com">opensource@keylevel.com</a><br>www.keylevel.com<br><br><br><br><br><br>------------------------------<br><br>Message: 3<br>Date: Sun, 16 Sep 2012 20:09:10 +0400<br>From: Elvis Dowson <<a ymailto="mailto:elvis.dowson@gmail.com" href="mailto:elvis.dowson@gmail.com">elvis.dowson@gmail.com</a>><br>To: Khem Raj <<a ymailto="mailto:raj.khem@gmail.com" href="mailto:raj.khem@gmail.com">raj.khem@gmail.com</a>><br>Cc: Yocto Discussion Mailing List <<a ymailto="mailto:yocto@yoctoproject.org" href="mailto:yocto@yoctoproject.org">yocto@yoctoproject.org</a>><br>Subject: Re: [yocto] Dependency walk for busybox recipe<br>Message-ID: <<a ymailto="mailto:5055F9A6.20709@gmail.com" href="mailto:5055F9A6.20709@gmail.com">5055F9A6.20709@gmail.com</a>><br>Content-Type: text/plain; charset="utf-8"; Format="flowed"<br><br>On 09/16/2012 07:54 AM, Khem Raj wrote:<br>> On Sat, Sep 15, 2012 at 10:59 AM, Elvis Dowson
<<a ymailto="mailto:elvis.dowson@gmail.com" href="mailto:elvis.dowson@gmail.com">elvis.dowson@gmail.com</a>> wrote:<br>>> So I added busybox-1.19.4 recipe back into my poky master branch, and the resulting size of the busybox-1.19.4 /bin/busybox or /bin/sh executable is 604.2 kb.<br>> make sure that .config of busybox has not changed even if you have<br>> same version backported<br>I've made sure that the defconfig files used in the recipe are <br>identical. The only addition that I notice now, is that the recent <br>rework done to task-core-boot, resulting in it being renamed as <br>packagegroup-core-boot.bb adds the following extra line:<br><br>${@base_contains("MACHINE_FEATURES", "rtc", "busybox-hwclock", "", d)} \<br><br>My virtex5.conf machine features entry does not specify an rtc,<br><br>MACHINE_FEATURES = "kernel26 apm ext2 ext3 vfat ethernet keyboard screen <br>serial"<br><br>yet the current poky master attempts to pull it
in:<br><br>NOTE: Resolving any missing task queue dependencies<br>ERROR: Nothing RPROVIDES 'busybox-hwclock' (but <br>/tool/yocto/poky/meta/recipes-core/packagegroups/packagegroup-core-boot.bb <br>RDEPENDS on or otherwise requires it)<br>NOTE: Runtime target 'busybox-hwclock' is unbuildable, removing...<br>Missing or unbuildable dependency chain was: ['busybox-hwclock']<br>NOTE: Runtime target 'packagegroup-core-boot' is unbuildable, removing...<br>Missing or unbuildable dependency chain was: ['packagegroup-core-boot', <br>'busybox-hwclock']<br>ERROR: Required build target 'core-image-minimal' has no buildable <br>providers.<br>Missing or unbuildable dependency chain was: ['core-image-minimal', <br>'packagegroup-core-boot', 'busybox-hwclock']<br><br>Summary: There were 2 ERROR messages shown, returning a non-zero exit code.<br><br>Is this a bug? Is the rtc being added from somewhere else? Should this <br>be happening?<br><br>Best regards,<br><br>Elvis
Dowson<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <<a href="http://lists.yoctoproject.org/pipermail/yocto/attachments/20120916/7a6c7236/attachment-0001.html" target="_blank">http://lists.yoctoproject.org/pipermail/yocto/attachments/20120916/7a6c7236/attachment-0001.html</a>><br><br>------------------------------<br><br>Message: 4<br>Date: Sun, 16 Sep 2012 20:49:38 +0400<br>From: Elvis Dowson <<a ymailto="mailto:elvis.dowson@gmail.com" href="mailto:elvis.dowson@gmail.com">elvis.dowson@gmail.com</a>><br>To: Yocto Discussion Mailing List <<a ymailto="mailto:yocto@yoctoproject.org" href="mailto:yocto@yoctoproject.org">yocto@yoctoproject.org</a>><br>Subject: Re: [yocto] All kernel modules being built and shipped in<br> images/modules-*.tgz<br>Message-ID: <<a ymailto="mailto:A158BAD0-6C2D-4724-B13A-AAB54992904C@gmail.com"
href="mailto:A158BAD0-6C2D-4724-B13A-AAB54992904C@gmail.com">A158BAD0-6C2D-4724-B13A-AAB54992904C@gmail.com</a>><br>Content-Type: text/plain; charset=us-ascii<br><br>Hi,<br><br>On Sep 15, 2012, at 7:29 AM, Elvis Dowson wrote:<br><br>> I just noticed that with the recent poky master updates, my images/modules-3.3.1-r00-virtex5.tgz file has grown from 33.1 MB to 668.5MB. When I looked in the package, I saw that the kernel/drivers folder inside that package was nearly 1.5GB uncompressed!!<br>> <br>> My kenel defconfig was tuned so that I only used a bare minimum of kernel modules, and nearly all except for 2 groups (one related to filesystem and the other for networking) was built as a module. The rest were all built into the kernel.<br>> <br>> Isn't this a regression or an error? <br>> <br>> Also my build time has gone up from 40 minutes to 67 minutes, probably as a result of the increased number of kernel modules being built and
shipped.<br><br>Is there any way to prevent all the kernel modules from being built, when 99% of my kernel defconfig settings are set to 'y' and not to build any modules?<br><br>Elvis<br><br>------------------------------<br><br>Message: 5<br>Date: Sun, 16 Sep 2012 19:31:15 +0100<br>From: Paul Eggleton <<a ymailto="mailto:paul.eggleton@linux.intel.com" href="mailto:paul.eggleton@linux.intel.com">paul.eggleton@linux.intel.com</a>><br>To: Elvis Dowson <<a ymailto="mailto:elvis.dowson@gmail.com" href="mailto:elvis.dowson@gmail.com">elvis.dowson@gmail.com</a>><br>Cc: <a ymailto="mailto:yocto@yoctoproject.org" href="mailto:yocto@yoctoproject.org">yocto@yoctoproject.org</a><br>Subject: Re: [yocto] Dependency walk for busybox recipe<br>Message-ID: <2099128.G0xV8XsdZC@helios><br>Content-Type: text/plain; charset="us-ascii"<br><br>On Sunday 16 September 2012 20:09:10 Elvis Dowson wrote:<br>> On 09/16/2012 07:54 AM, Khem Raj wrote:<br>>
> On Sat, Sep 15, 2012 at 10:59 AM, Elvis Dowson <<a ymailto="mailto:elvis.dowson@gmail.com" href="mailto:elvis.dowson@gmail.com">elvis.dowson@gmail.com</a>> <br>wrote:<br>> >> So I added busybox-1.19.4 recipe back into my poky master branch, and the<br>> >> resulting size of the busybox-1.19.4 /bin/busybox or /bin/sh executable<br>> >> is 604.2 kb.> <br>> > make sure that .config of busybox has not changed even if you have<br>> > same version backported<br>> <br>> I've made sure that the defconfig files used in the recipe are<br>> identical. The only addition that I notice now, is that the recent<br>> rework done to task-core-boot, resulting in it being renamed as<br>> packagegroup-core-boot.bb adds the following extra line:<br>> <br>> ${@base_contains("MACHINE_FEATURES", "rtc", "busybox-hwclock", "", d)} \<br>> <br>> My virtex5.conf machine features entry does not specify an
rtc,<br>> <br>> MACHINE_FEATURES = "kernel26 apm ext2 ext3 vfat ethernet keyboard screen<br>> serial"<br>> <br>> yet the current poky master attempts to pull it in:<br>> <br>> NOTE: Resolving any missing task queue dependencies<br>> ERROR: Nothing RPROVIDES 'busybox-hwclock' (but<br>> /tool/yocto/poky/meta/recipes-core/packagegroups/packagegroup-core-boot.bb<br>> RDEPENDS on or otherwise requires it)<br>> NOTE: Runtime target 'busybox-hwclock' is unbuildable, removing...<br>> Missing or unbuildable dependency chain was: ['busybox-hwclock']<br>> NOTE: Runtime target 'packagegroup-core-boot' is unbuildable, removing...<br>> Missing or unbuildable dependency chain was: ['packagegroup-core-boot',<br>> 'busybox-hwclock']<br>> ERROR: Required build target 'core-image-minimal' has no buildable<br>> providers.<br>> Missing or unbuildable dependency chain was: ['core-image-minimal',<br>>
'packagegroup-core-boot', 'busybox-hwclock']<br>> <br>> Summary: There were 2 ERROR messages shown, returning a non-zero exit code.<br>> <br>> Is this a bug? Is the rtc being added from somewhere else? Should this<br>> be happening?<br><br>It's not a bug, this is meant to happen. This is a result of <br>MACHINE_FEATURES_BACKFILL, which is intended to ensure that we can introduce <br>new items to MACHINE_FEATURES controlling existing functionality without <br>breaking existing machine configurations by disabling the existing <br>functionality because the configuration doesn't include it. (In older versions <br>of busybox the hwclock feature was on by default - an hwclock item was added <br>at the MACHINE_FEATURES level to be able to control it).<br><br>To fix this, just add hwclock to MACHINE_FEATURES_BACKFILL_CONSIDERED in your <br>machine configuration.<br><br>Cheers,<br>Paul<br><br><br>-- <br><br>Paul Eggleton<br>Intel Open Source
Technology Centre<br><br><br>------------------------------<br><br>_______________________________________________<br>yocto mailing list<br><a ymailto="mailto:yocto@yoctoproject.org" href="mailto:yocto@yoctoproject.org">yocto@yoctoproject.org</a><br><a href="https://lists.yoctoproject.org/listinfo/yocto" target="_blank">https://lists.yoctoproject.org/listinfo/yocto</a><br><br><br>End of yocto Digest, Vol 24, Issue 66<br>*************************************<br><br><br> </div> </div> </div></body></html>