Dependency tracking - or - how to get rid of kexec-tools

Dependency tracking - or - how to get rid of kexec-tools

[Nils Faerber]

Hi!
I just found a little bit of a problem and am now looking for the most
correct solution to it...
I am trying to build x11-image for a mipsel target. I am using the
dev-head and angstrom-2009 or DISTRO_VERSION = "2009.X-test-20090301"
respectively.
The problem is that this constellation includes kexec-tools-static for
something just that kexec-tools-1.101 does not support mipsel.
As far as I have seen it I will not make use of kexec-tools later on. I
just want to build a quite simple X11 image for that device.

So I can do two things:
1. Get rid of the dependency so that it will not be built. How can I
find out which dependency pulls in kexec-tools?

2. Upgrade kexec-tools to the version that is e.g. in Debian, like
kexec-tools_20080324.orig.tar.gz which now include mipsel support.

So, what to do now?
Even if 2. would be the best way to go I would still be interested how
one can trace this kind of dependency - sometimes I would be really
interested why certain packages are built.


PS: I am planning on submitting this mipsel machine support. What would
be the best way? Create a diff against dev-head and post here?

Cheers
  nils faerber

-- 
kernel concepts GbR      Tel: +49-271-771091-12
Sieghuetter Hauptweg 48  Fax: +49-271-771091-19
D-57072 Siegen           Mob: +49-176-21024535
--

Re: Dependency tracking - or - how to get rid of kexec-tools

[Henning Heinold]

On Mon, Mar 02, 2009 at 12:48:00AM +0100, Nils Faerber wrote:
> Hi!
> I just found a little bit of a problem and am now looking for the most
> correct solution to it...
> I am trying to build x11-image for a mipsel target. I am using the
> dev-head and angstrom-2009 or DISTRO_VERSION = "2009.X-test-20090301"
> respectively.
> The problem is that this constellation includes kexec-tools-static for
> something just that kexec-tools-1.101 does not support mipsel.
> As far as I have seen it I will not make use of kexec-tools later on. I
> just want to build a quite simple X11 image for that device.
> 
> So I can do two things:
> 1. Get rid of the dependency so that it will not be built. How can I
> find out which dependency pulls in kexec-tools?
> 

run bitbake -g which gives you 2 files which shows the deps, but
sometimes it doesnt really show why a package was included.

> 2. Upgrade kexec-tools to the version that is e.g. in Debian, like
> kexec-tools_20080324.orig.tar.gz which now include mipsel support.
> 
> So, what to do now?
> Even if 2. would be the best way to go I would still be interested how
> one can trace this kind of dependency - sometimes I would be really
> interested why certain packages are built.
> 
> 
> PS: I am planning on submitting this mipsel machine support. What would
> be the best way? Create a diff against dev-head and post here?
> 

Please post the patch here for review.

> Cheers
>   nils faerber

Bye Henning

Re: Dependency tracking - or - how to get rid of kexec-tools

[Andrea Adami]

>Upgrade kexec-tools
+1

You could also try:

cd ../org.openembedded.dev/conf
grep -r  kexec .

My 2 cents

Andrea