[yocto] help

Jam1e Harr1s jam1eharr1s at yahoo.co.uk
Sun Sep 16 12:10:28 PDT 2012 


unsubscribe

________________________________
 From: "yocto-request at yoctoproject.org" <yocto-request at yoctoproject.org>
To: yocto at yoctoproject.org 
Sent: Sunday, 16 September 2012, 20:00
Subject: yocto Digest, Vol 24, Issue 66
 
Send yocto mailing list submissions to
    yocto at yoctoproject.org

To subscribe or unsubscribe via the World Wide Web, visit
    https://lists.yoctoproject.org/listinfo/yocto
or, via email, send a message with subject or body 'help' to
    yocto-request at yoctoproject.org

You can reach the person managing the list at
    yocto-owner at yoctoproject.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of yocto digest..."


Today's Topics:

   1. Re: Dependency walk for busybox recipe (Khem Raj)
   2. Re: Forcing link order for autotools recipe [SOLVED] (Chris Tapp)
   3. Re: Dependency walk for busybox recipe (Elvis Dowson)
   4. Re: All kernel modules being built and shipped in
      images/modules-*.tgz (Elvis Dowson)
   5. Re: Dependency walk for busybox recipe (Paul Eggleton)


----------------------------------------------------------------------

Message: 1
Date: Sat, 15 Sep 2012 20:54:56 -0700
From: Khem Raj <raj.khem at gmail.com>
To: Elvis Dowson <elvis.dowson at gmail.com>
Cc: Yocto Discussion Mailing List <yocto at yoctoproject.org>
Subject: Re: [yocto] Dependency walk for busybox recipe
Message-ID:
    <CAMKF1sr9zgFJMrhBM_xdVPMM_zhnQCzjxYanub6O7NFG4w1Ohg at mail.gmail.com>
Content-Type: text/plain; charset=UTF-8

On Sat, Sep 15, 2012 at 10:59 AM, Elvis Dowson <elvis.dowson at gmail.com> wrote:
>
>
> 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.

make sure that .config of busybox has not changed even if you have
same version backported


------------------------------

Message: 2
Date: Sun, 16 Sep 2012 11:08:37 +0100
From: Chris Tapp <opensource at keylevel.com>
To: "yocto at yoctoproject.org Project" <yocto at yoctoproject.org>
Subject: Re: [yocto] Forcing link order for autotools recipe [SOLVED]
Message-ID: <B130E0AD-EF24-4774-9671-6EC9C8B03EDE at keylevel.com>
Content-Type: text/plain; charset=us-ascii

On 16 Sep 2012, at 00:59, Chris Tapp wrote:

> 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.
> 
> I've finally tracked this down to link order. The final command is of the form:
> 
> g++ -lGL -lcurl -o binary a.o b.o
> 
> If I change this to:
> 
> g++ -o binary a.o b.o -lGL -lcurl
> 
> then it builds ok.
> 
> 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).
> 
> Can I get autotools to always link the libraries last?


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).

That'll teach me to blindly copy from else where ;-) Strange it's worked up till now...

Chris Tapp

opensource at keylevel.com
www.keylevel.com





------------------------------

Message: 3
Date: Sun, 16 Sep 2012 20:09:10 +0400
From: Elvis Dowson <elvis.dowson at gmail.com>
To: Khem Raj <raj.khem at gmail.com>
Cc: Yocto Discussion Mailing List <yocto at yoctoproject.org>
Subject: Re: [yocto] Dependency walk for busybox recipe
Message-ID: <5055F9A6.20709 at gmail.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"

On 09/16/2012 07:54 AM, Khem Raj wrote:
> On Sat, Sep 15, 2012 at 10:59 AM, Elvis Dowson <elvis.dowson at gmail.com> wrote:
>> 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.
> make sure that .config of busybox has not changed even if you have
> same version backported
I've made sure that the defconfig files used in the recipe are 
identical. The only addition that I notice now, is that the recent 
rework done to task-core-boot, resulting in it being renamed as 
packagegroup-core-boot.bb adds the following extra line:

${@base_contains("MACHINE_FEATURES", "rtc", "busybox-hwclock", "", d)} \

My virtex5.conf machine features entry does not specify an rtc,

MACHINE_FEATURES = "kernel26 apm ext2 ext3 vfat ethernet keyboard screen 
serial"

yet the current poky master attempts to pull it in:

NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'busybox-hwclock' (but 
/tool/yocto/poky/meta/recipes-core/packagegroups/packagegroup-core-boot.bb 
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'busybox-hwclock' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['busybox-hwclock']
NOTE: Runtime target 'packagegroup-core-boot' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['packagegroup-core-boot', 
'busybox-hwclock']
ERROR: Required build target 'core-image-minimal' has no buildable 
providers.
Missing or unbuildable dependency chain was: ['core-image-minimal', 
'packagegroup-core-boot', 'busybox-hwclock']

Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

Is this a bug? Is the rtc being added from somewhere else? Should this 
be happening?

Best regards,

Elvis Dowson
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20120916/7a6c7236/attachment-0001.html>

------------------------------

Message: 4
Date: Sun, 16 Sep 2012 20:49:38 +0400
From: Elvis Dowson <elvis.dowson at gmail.com>
To: Yocto Discussion Mailing List <yocto at yoctoproject.org>
Subject: Re: [yocto] All kernel modules being built and shipped in
    images/modules-*.tgz
Message-ID: <A158BAD0-6C2D-4724-B13A-AAB54992904C at gmail.com>
Content-Type: text/plain; charset=us-ascii

Hi,

On Sep 15, 2012, at 7:29 AM, Elvis Dowson wrote:

> 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!!
> 
> 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.
> 
> Isn't this a regression or an error? 
> 
> 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.

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?

Elvis

------------------------------

Message: 5
Date: Sun, 16 Sep 2012 19:31:15 +0100
From: Paul Eggleton <paul.eggleton at linux.intel.com>
To: Elvis Dowson <elvis.dowson at gmail.com>
Cc: yocto at yoctoproject.org
Subject: Re: [yocto] Dependency walk for busybox recipe
Message-ID: <2099128.G0xV8XsdZC at helios>
Content-Type: text/plain; charset="us-ascii"

On Sunday 16 September 2012 20:09:10 Elvis Dowson wrote:
> On 09/16/2012 07:54 AM, Khem Raj wrote:
> > On Sat, Sep 15, 2012 at 10:59 AM, Elvis Dowson <elvis.dowson at gmail.com> 
wrote:
> >> 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.> 
> > make sure that .config of busybox has not changed even if you have
> > same version backported
> 
> I've made sure that the defconfig files used in the recipe are
> identical. The only addition that I notice now, is that the recent
> rework done to task-core-boot, resulting in it being renamed as
> packagegroup-core-boot.bb adds the following extra line:
> 
> ${@base_contains("MACHINE_FEATURES", "rtc", "busybox-hwclock", "", d)} \
> 
> My virtex5.conf machine features entry does not specify an rtc,
> 
> MACHINE_FEATURES = "kernel26 apm ext2 ext3 vfat ethernet keyboard screen
> serial"
> 
> yet the current poky master attempts to pull it in:
> 
> NOTE: Resolving any missing task queue dependencies
> ERROR: Nothing RPROVIDES 'busybox-hwclock' (but
> /tool/yocto/poky/meta/recipes-core/packagegroups/packagegroup-core-boot.bb
> RDEPENDS on or otherwise requires it)
> NOTE: Runtime target 'busybox-hwclock' is unbuildable, removing...
> Missing or unbuildable dependency chain was: ['busybox-hwclock']
> NOTE: Runtime target 'packagegroup-core-boot' is unbuildable, removing...
> Missing or unbuildable dependency chain was: ['packagegroup-core-boot',
> 'busybox-hwclock']
> ERROR: Required build target 'core-image-minimal' has no buildable
> providers.
> Missing or unbuildable dependency chain was: ['core-image-minimal',
> 'packagegroup-core-boot', 'busybox-hwclock']
> 
> Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
> 
> Is this a bug? Is the rtc being added from somewhere else? Should this
> be happening?

It's not a bug, this is meant to happen. This is a result of 
MACHINE_FEATURES_BACKFILL, which is intended to ensure that we can introduce 
new items to MACHINE_FEATURES controlling existing functionality without 
breaking existing machine configurations by disabling the existing 
functionality because the configuration doesn't include it. (In older versions 
of busybox the hwclock feature was on by default - an hwclock item was added 
at the MACHINE_FEATURES level to be able to control it).

To fix this, just add hwclock to MACHINE_FEATURES_BACKFILL_CONSIDERED in your 
machine configuration.

Cheers,
Paul


-- 

Paul Eggleton
Intel Open Source Technology Centre


------------------------------

_______________________________________________
yocto mailing list
yocto at yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


End of yocto Digest, Vol 24, Issue 66
*************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20120916/0ac3a3ba/attachment.html>

More information about the yocto mailing list