All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joaquim Duran <joaquinduran@adtelecom.es>
To: Using the OpenEmbedded metadata to build Linux Distributions
	<openembedded-devel@lists.openembedded.org>
Subject: Re: List of dependent packages
Date: Thu, 28 Sep 2006 08:46:10 +0100	[thread overview]
Message-ID: <451B7DC2.5070304@adtelecom.es> (raw)
In-Reply-To: <661829260.20060927221730@gmail.com>

Hello,

Changing the filter I get interesting results:

$bitbake -n -v bootstrap-image|grep "Selecting"

NOTE: Selecting already-staged ipkg-native (0.99.163-r1) to satisfy 
ipkg-native
NOTE: Selecting already-staged pkgconfig-native (0.15.0-r2) to satisfy 
pkgconfig-native
NOTE: Selecting already-staged autoconf-native (2.59-r5) to satisfy 
autoconf-native
NOTE: Selecting already-staged m4-native (1.4.2-r0) to satisfy m4-native
NOTE: Selecting already-staged gnu-config-native (0.1+cvs20050701-r4) to 
satisfy gnu-config-native
NOTE: Selecting already-staged automake-native (1.9.3-r5) to satisfy 
automake-native
NOTE: Selecting already-staged libtool-native (1.5.10-r4) to satisfy 
libtool-native
[...]

It displays the list of packages selected with its version.


$bitbake -n -v bootstrap-image|grep "[Ss]electing"

NOTE: Selecting already-staged file-native (4.16-r1) to satisfy file-native
NOTE: Selecting already-staged gcc-cross (3.3.2-r1) to satisfy 
virtual/arm-linux-gcc
NOTE: selecting gcc-cross to satisfy virtual/arm-linux-gcc due to 
PREFERRED_PROVIDERS
NOTE: Selecting already-staged binutils-cross (2.14.90.driscoll-r0) to 
satisfy virtual/arm-linux-binutils
NOTE: selecting binutils-cross to satisfy virtual/arm-linux-binutils due 
to PREFERRED_PROVIDERS

It displays the list of packages selected with its version and indicates 
which packages has been selected by configuration settings.


Thanks for your comment.


Thanks and Best Regards,
Joaquim Duran



En/na Paul Sokolovsky ha escrit:
> Hello Joaquim,
> 
> Wednesday, September 27, 2006, 10:36:10 AM, you wrote:
> 
>> Hello,
> 
>> As I've the impression that Bitbake is very related to OE. I post the 
>> bug here.
> 
>> I execute: bitbake -g boostrap-image.
> 
>   Have to say I didn't try -g myself yet. --dry-run --verbose what I
> usually use, as was suggested on this last before. And I just tried
> that it actuially works without any packages built. Specifically:
> 
> bitbake --dry-run --verbose gpe-image|grep "current path"
> 
> NOTE: current path: gpe-image (gpe-image)
> NOTE: current path: gpe-image (gpe-image) -> ipkg-native (ipkg-native)
> NOTE: current path: gpe-image (gpe-image) -> ipkg-native (ipkg-native) -> pkgconfig-native (pkgconfig-native)
> NOTE: current path: gpe-image (gpe-image) -> ipkg-native (ipkg-native) -> pkgconfig-native (pkgconfig-native) -> autoconf-nati
> NOTE: current path: gpe-image (gpe-image) -> ipkg-native (ipkg-native) -> pkgconfig-native (pkgconfig-native) -> autoconf-nati
> NOTE: current path: gpe-image (gpe-image) -> ipkg-native (ipkg-native) -> pkgconfig-native (pkgconfig-native) -> autoconf-nati
> NOTE: current path: gpe-image (gpe-image) -> ipkg-native (ipkg-native) -> pkgconfig-native (pkgconfig-native) -> autoconf-nati
> NOTE: current path: gpe-image (gpe-image) -> ipkg-native (ipkg-native) -> pkgconfig-native (pkgconfig-native) -> automake-nati
> NOTE: current path: gpe-image (gpe-image) -> ipkg-native (ipkg-native) -> pkgconfig-native (pkgconfig-native) -> libtool-nativ
> NOTE: current path: gpe-image (gpe-image) -> ipkg-utils-native (ipkg-utils-native)
> NOTE: current path: gpe-image (gpe-image) -> fakeroot-native (fakeroot-native)
> NOTE: current path: gpe-image (gpe-image) -> file-native (file-native)
> 
> Just in case, I'm using bitbake 1.6.1 (from SVN).
> 
> 
>> Output:
> 
>> NOTE: Parsing finished. 3962 cached, 0 parsed, 139 skipped, 27 masked.
> 
>> Traceback (most recent call last):
>>    File "/home/qduran/oe/bitbake/bin/bitbake", line 1161, in ?
>>      main()
>>    File "/home/qduran/oe/bitbake/bin/bitbake", line 1156, in main
>>      cooker.cook( BBConfiguration( options ), args[1:] )
>>    File "/home/qduran/oe/bitbake/bin/bitbake", line 962, in cook
>>      self.generateDotGraph( pkgs_to_build, 
>> self.configuration.ignored_dot_deps )
>>    File "/home/qduran/oe/bitbake/bin/bitbake", line 544, in generateDotGraph
>>      add_depends( pkgs_to_build )
>>    File "/home/qduran/oe/bitbake/bin/bitbake", line 467, in add_depends
>>      fn = myFilterProvider(providers, package)[0]
>>    File "/home/qduran/oe/bitbake/bin/bitbake", line 413, in myFilterProvider
>>      preferred_versions[pn] = bb.providers.findBestProvider(pn, pkg_pn)[2:4]
>> TypeError: findBestProvider() takes at least 3 arguments (2 given)
> 
>   Needs to be fixed, sure. Worth a bugreport at
> http://bugs.openembedded.org .

Done

>> Hope this helps.
> 
> 
> 




      reply	other threads:[~2006-09-28  6:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-26 11:22 List of dependent packages Joaquim Duran
2006-09-26 10:58 ` Christopher Lang
2006-09-26 12:36   ` Joaquim Duran
2006-09-26 12:01 ` Paul Sokolovsky
2006-09-26 13:47   ` Richard Purdie
2006-09-26 15:35   ` Joaquim Duran
2006-09-26 14:57     ` pHilipp Zabel
2006-09-26 15:26       ` Richard Purdie
2006-09-26 16:01       ` Joaquim Duran
2006-09-27  7:36     ` Joaquim Duran
2006-09-27 13:45       ` Ray Lehtiniemi
2006-09-27 13:53         ` Ray Lehtiniemi
2006-09-27 19:17       ` Paul Sokolovsky
2006-09-28  7:46         ` Joaquim Duran [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=451B7DC2.5070304@adtelecom.es \
    --to=joaquinduran@adtelecom.es \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.