libgles-omap3 fails

libgles-omap3 fails

[Andreas Mueller]

I don't understand what's going on. When building libgles-omap3 I get

[Superandi@localhost gumstix-oe]$ bitbake libgles-omap3
NOTE: Handling BitBake files: | (0091/7118) [ 1 %]NOTE: Angstrom DOES NOT support bluez-utils because bluez-utils 3.x has been replaced by bluez4
NOTE: Handling BitBake files: \ (0405/7118) [ 5 %]WARNING: Deprecated usage of 'patch' url param for '/home/Superandi/data/OpenEmbedded/openpandorra-oe/recipes/pandora-system/pandora-pmenu/0001-Remove-libconfig-from-Makefile.patch', please use 'apply={yes,no}'
NOTE: Handling BitBake files: / (1097/7118) [15 %]NOTE: Angstrom DOES NOT support ipkg because ipkg has been superseded by opkg
NOTE: Handling BitBake files: \ (3545/7118) [49 %]NOTE: Angstrom DOES NOT support libiconv because the glibc builtin iconv replacement is used
NOTE: Handling BitBake files: \ (3690/7118) [51 %]NOTE: Angstrom DOES NOT support bluez-utils because bluez-utils 3.x has been replaced by bluez4
NOTE: Handling BitBake files: / (4132/7118) [58 %]WARNING: Deprecated usage of 'patch' url param for '/home/Superandi/data/OpenEmbedded/openpandorra-oe/recipes/slim/slim/fix-manpage.patch', please use 'apply={yes,no}'
NOTE: Handling BitBake files: \ (5024/7118) [70 %]NOTE: Angstrom DOES NOT support libiconv because the glibc builtin iconv replacement is used
NOTE: Handling BitBake files: / (5112/7118) [71 %]NOTE: Angstrom DOES NOT support bluez-libs because bluez-libs 3.x has been replaced by bluez4
NOTE: Handling BitBake files: - (6053/7118) [85 %]NOTE: Angstrom DOES NOT support bluez-libs because bluez-libs 3.x has been replaced by bluez4
NOTE: Handling BitBake files: \ (6290/7118) [88 %]NOTE: Angstrom DOES NOT support bluez-libs because bluez-libs 3.x has been replaced by bluez4
NOTE: Handling BitBake files: \ (6339/7118) [89 %]NOTE: Angstrom DOES NOT support libiconv because the glibc builtin iconv replacement is used
NOTE: Handling BitBake files: \ (6545/7118) [91 %]NOTE: Angstrom DOES NOT support fso-apm because regular apmd is good enough
NOTE: Handling BitBake files: - (7118/7118) [100 %]
Parsing of 7118 .bb files complete (0 cached, 7118 parsed). 7430 targets, 320 skipped, 2 masked, 0 errors.
ERROR: '['/home/Superandi/data/OpenEmbedded/gumstix-oe/recipes/powervr-drivers/omap3-sgx-modules_1.4.14.2616.bb']' RDEPENDS/RRECOMMENDS or otherwise requires the runtime entity 'kernel-2.6.32' but it wasn't found in any PACKAGE or RPROVIDES variables
ERROR: Required build target 'libgles-omap3' has no buildable providers.
Missing or unbuildable dependency chain was: ['libgles-omap3', 'omap3-sgx-modules', 'kernel-2.6.32']

Build Configuration:
BB_VERSION        = "1.10.2"
METADATA_BRANCH   = "oe.org.openembedded.dev"
METADATA_REVISION = "aa479cd"
TARGET_ARCH       = "arm"
TARGET_OS         = "linux-gnueabi"
MACHINE           = "overo"
DISTRO            = "angstrom"
DISTRO_VERSION    = "2010.7-test-20110130"
TARGET_FPU        = "hard"

NOTE: Resolving any missing task queue dependencies
ERROR: '['/home/Superandi/data/OpenEmbedded/gumstix-oe/recipes/powervr-drivers/omap3-sgx-modules_1.4.14.2616.bb']' RDEPENDS/RRECOMMENDS or otherwise requires the runtime entity 'kernel-2.6.32' but it wasn't found in any PACKAGE or RPROVIDES variables
Unknown Event: <bb.event.NoProvider instance at 0x1280280c>
NOTE: Runtime target 'kernel-2.6.32' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['kernel-2.6.32']
NOTE: Runtime target 'omap3-sgx-modules' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['omap3-sgx-modules', 'kernel-2.6.32']
ERROR: Required build target 'libgles-omap3' has no buildable providers.
Missing or unbuildable dependency chain was: ['libgles-omap3', 'omap3-sgx-modules', 'kernel-2.6.32']
Command execution failed: Traceback (most recent call last):
  File "/home/Superandi/data/OpenEmbedded/bitbake/lib/bb/command.py", line 88, in runAsyncCommand
    commandmethod(self.cmds_async, self, options)
  File "/home/Superandi/data/OpenEmbedded/bitbake/lib/bb/command.py", line 174, in buildTargets
    command.cooker.buildTargets(pkgs_to_build, task)
  File "/home/Superandi/data/OpenEmbedded/bitbake/lib/bb/cooker.py", line 784, in buildTargets
    taskdata.add_unresolved(localdata, self.status)
  File "/home/Superandi/data/OpenEmbedded/bitbake/lib/bb/taskdata.py", line 562, in add_unresolved
    self.remove_runtarget(self.getrun_id(target))
  File "/home/Superandi/data/OpenEmbedded/bitbake/lib/bb/taskdata.py", line 535, in remove_runtarget
    self.fail_fnid(fnid, missing_list)
  File "/home/Superandi/data/OpenEmbedded/bitbake/lib/bb/taskdata.py", line 495, in fail_fnid
    self.remove_runtarget(target, missing_list)
  File "/home/Superandi/data/OpenEmbedded/bitbake/lib/bb/taskdata.py", line 535, in remove_runtarget
    self.fail_fnid(fnid, missing_list)
  File "/home/Superandi/data/OpenEmbedded/bitbake/lib/bb/taskdata.py", line 490, in fail_fnid
    self.remove_buildtarget(target, missing_list)
  File "/home/Superandi/data/OpenEmbedded/bitbake/lib/bb/taskdata.py", line 519, in remove_buildtarget
    raise bb.providers.NoProvider
NoProvider

I don't find affecting changes which could have broken this. Any good ideas?

Andreas

Re: libgles-omap3 fails

[Paul Menzel]

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

Dear Andreas,


Am Montag, den 31.01.2011, 00:12 +0100 schrieb Andreas Mueller:
> I don't understand what's going on. When building libgles-omap3 I get
> 
> [Superandi@localhost gumstix-oe]$ bitbake libgles-omap3

[…]

> Parsing of 7118 .bb files complete (0 cached, 7118 parsed). 7430 targets, 320 skipped, 2 masked, 0 errors.
> ERROR: '['/home/Superandi/data/OpenEmbedded/gumstix-oe/recipes/powervr-drivers/omap3-sgx-modules_1.4.14.2616.bb']' RDEPENDS/RRECOMMENDS or otherwise requires the runtime entity 'kernel-2.6.32' but it wasn't found in any PACKAGE or RPROVIDES variables
> ERROR: Required build target 'libgles-omap3' has no buildable providers.
> Missing or unbuildable dependency chain was: ['libgles-omap3', 'omap3-sgx-modules', 'kernel-2.6.32']
> 
> Build Configuration:
> BB_VERSION        = "1.10.2"
> METADATA_BRANCH   = "oe.org.openembedded.dev"
> METADATA_REVISION = "aa479cd"
> TARGET_ARCH       = "arm"
> TARGET_OS         = "linux-gnueabi"
> MACHINE           = "overo"
> DISTRO            = "angstrom"
> DISTRO_VERSION    = "2010.7-test-20110130"
> TARGET_FPU        = "hard"

[…]

> I don't find affecting changes which could have broken this. Any good ideas?

It looks like the same problem as in [1] and should be fixed by commit
09d0669e [2].


Thanks,

Paul


[1] http://lists.linuxtogo.org/pipermail/openembedded-devel/2011-January/029355.html
[2] http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=09d0669ed914e810bb8bd6ce9275b7a4125bc8a0

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

Re: libgles-omap3 fails

["Andreas Müller"]

-------- Original-Nachricht --------
> Datum: Mon, 31 Jan 2011 09:15:09 +0100
> Von: Paul Menzel <paulepanter@users.sourceforge.net>
> An: openembedded-devel@lists.openembedded.org
> Betreff: Re: [oe] libgles-omap3 fails

> Dear Andreas,
> 
> 
> Am Montag, den 31.01.2011, 00:12 +0100 schrieb Andreas Mueller:
> > I don't understand what's going on. When building libgles-omap3 I get
> > 
> > [Superandi@localhost gumstix-oe]$ bitbake libgles-omap3
> 
> […]
> 
> > Parsing of 7118 .bb files complete (0 cached, 7118 parsed). 7430
> targets, 320 skipped, 2 masked, 0 errors.
> > ERROR:
> '['/home/Superandi/data/OpenEmbedded/gumstix-oe/recipes/powervr-drivers/omap3-sgx-modules_1.4.14.2616.bb']' RDEPENDS/RRECOMMENDS or
> otherwise requires the runtime entity 'kernel-2.6.32' but it wasn't found in any
> PACKAGE or RPROVIDES variables
> > ERROR: Required build target 'libgles-omap3' has no buildable providers.
> > Missing or unbuildable dependency chain was: ['libgles-omap3',
> 'omap3-sgx-modules', 'kernel-2.6.32']
> > 
> > Build Configuration:
> > BB_VERSION        = "1.10.2"
> > METADATA_BRANCH   = "oe.org.openembedded.dev"
> > METADATA_REVISION = "aa479cd"
> > TARGET_ARCH       = "arm"
> > TARGET_OS         = "linux-gnueabi"
> > MACHINE           = "overo"
> > DISTRO            = "angstrom"
> > DISTRO_VERSION    = "2010.7-test-20110130"
> > TARGET_FPU        = "hard"
> 
> […]
> 
> > I don't find affecting changes which could have broken this. Any good
> ideas?
> 
> It looks like the same problem as in [1] and should be fixed by commit
> 09d0669e [2].
> 
> 
> Thanks,
> 
> Paul
> 
> 
> [1]
> http://lists.linuxtogo.org/pipermail/openembedded-devel/2011-January/029355.html
> [2]
> http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=09d0669ed914e810bb8bd6ce9275b7a4125bc8a0

Paul thanks for responding desperate late-night noise :-)

-- 
NEU: FreePhone - kostenlos mobil telefonieren und surfen!			
Jetzt informieren: http://www.gmx.net/de/go/freephone

[meta-oe] need to add some verfication package recipes

[Ahsan, Noor]

Hello,

I need to add some packages in meta-oe which are related to verification and benchmark. The packages are as follows. I just need to know in which directories the recipes of these package should go.

1. lmbench (Tools for performance analysis)
2. netperf (benchmark the performance of different type of networks)
3. iperf (measure maximum TCP and UDP bandwitdth)
4. bonie++ (filesystem benchmark tool)
5. izone3 (filesystem and disk benchmar)
6. dbench (used to stress the filesystem or a server to see which workload it become stuarated)
7. tbench (filesystem benchmark which generates load patterns)
8. toibench (multithreaded I.O benchmark)


Kindly suggest me to which recipes dir the recipes for these package should go thanks.

Regards,
Noor

Re: [meta-oe] need to add some verfication package recipes

[Paul Menzel]

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

Dear Noor,


Am Montag, den 22.08.2011, 09:53 +0200 schrieb Ahsan, Noor:

> I need to add some packages in meta-oe which are related to verification and benchmark. The packages are as follows. I just need to know in which directories the recipes of these package should go.
> 
> 1. lmbench (Tools for performance analysis)
> 2. netperf (benchmark the performance of different type of networks)
> 3. iperf (measure maximum TCP and UDP bandwitdth)
> 4. bonie++ (filesystem benchmark tool)
> 5. izone3 (filesystem and disk benchmar)
> 6. dbench (used to stress the filesystem or a server to see which workload it become stuarated)
> 7. tbench (filesystem benchmark which generates load patterns)
> 8. toibench (multithreaded I.O benchmark)

there are some typos in the names above.

> Kindly suggest me to which recipes dir the recipes for these package should go thanks.

I could not find a category specifically for performance tools. Just put
them into `meta-oe/recipes-support/` and submit the patches. The
developers will tell you then, if they have objections. I think you will
always get more responses when sending in ready-to-be-applied patch.
Although it might be more time for you. :(

It would be nice if the oe-core folks can comment too in case these
recipes should go into oe-core some day.


Thanks,

Paul

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

Re: [meta-oe] need to add some verfication package recipes

[Khem Raj]

On 8/22/2011 12:53 AM, Ahsan, Noor wrote:
> Hello,
>
> I need to add some packages in meta-oe which are related to verification and benchmark. The packages are as follows. I just need to know in which directories the recipes of these package should go.
>
> 1. lmbench (Tools for performance analysis)
> 2. netperf (benchmark the performance of different type of networks)
> 3. iperf (measure maximum TCP and UDP bandwitdth)
> 4. bonie++ (filesystem benchmark tool)
> 5. izone3 (filesystem and disk benchmar)
> 6. dbench (used to stress the filesystem or a server to see which workload it become stuarated)
> 7. tbench (filesystem benchmark which generates load patterns)
> 8. toibench (multithreaded I.O benchmark)
>
>
> Kindly suggest me to which recipes dir the recipes for these package should go thanks.

recipes-benchmarks seems more appropriate here. If the directory does 
not exist create it.

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

Re: [meta-oe] need to add some verfication package recipes

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Op 22-08-11 11:03, Paul Menzel schreef:

> It would be nice if the oe-core folks can comment too in case these recipes should go into oe-core some day.

OE-core needs to get smaller, not bigger.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFOUrSiMkyGM64RGpERAnnMAJ9oyaXwwj7U4BrlxKAvz7Rbfyf7kgCcDv9F
Tp6RxDJrJSLW2OM3rDiZQkM=
=rMpm
-----END PGP SIGNATURE-----

Re: [meta-oe] need to add some verfication package recipes

[Chris Larson]

On Mon, Aug 22, 2011 at 12:57 PM, Koen Kooi <koen@dominion.thruhere.net> wrote:
> Op 22-08-11 11:03, Paul Menzel schreef:
>
>> It would be nice if the oe-core folks can comment too in case these recipes should go into oe-core some day.
>
> OE-core needs to get smaller, not bigger.

Regarding where recipes go, am I the only one that finds the
recipes-*/ directories just annoying for day to day use? The breakdown
might make sense from a categorical viewpoint, but as someone looking
to modify a recipe, it's a crapshoot trying to find anything. I resort
to shell globbing or find commands, every time.
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics

Re: [meta-oe] need to add some verfication package recipes

[Martin Jansa]

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

On Mon, Aug 22, 2011 at 05:59:11PM -0700, Chris Larson wrote:
> On Mon, Aug 22, 2011 at 12:57 PM, Koen Kooi <koen@dominion.thruhere.net> wrote:
> > Op 22-08-11 11:03, Paul Menzel schreef:
> >
> >> It would be nice if the oe-core folks can comment too in case these recipes should go into oe-core some day.
> >
> > OE-core needs to get smaller, not bigger.
> 
> Regarding where recipes go, am I the only one that finds the
> recipes-*/ directories just annoying for day to day use? The breakdown
> might make sense from a categorical viewpoint, but as someone looking
> to modify a recipe, it's a crapshoot trying to find anything. I resort
> to shell globbing or find commands, every time.

Me too, first I try to recipes-* where I guess it should be, then find
it with find somewhere else :/. And the same sometimes twice or more
times when I'm not sure if it's oe-core/meta-oe or even meta-gnome or
whatever :/.

Regards,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]