From: Henning Heinold <heinold@inf.fu-berlin.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Dependency tracking - or - how to get rid of kexec-tools
Date: Tue, 3 Mar 2009 10:30:30 +0100 [thread overview]
Message-ID: <20090303093030.GA17676@mi.fu-berlin.de> (raw)
In-Reply-To: <49AB1EB0.5090002@kernelconcepts.de>
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
next prev parent reply other threads:[~2009-03-03 9:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-01 23:48 Dependency tracking - or - how to get rid of kexec-tools Nils Faerber
2009-03-03 9:30 ` Henning Heinold [this message]
2009-03-03 12:37 ` Andrea Adami
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=20090303093030.GA17676@mi.fu-berlin.de \
--to=heinold@inf.fu-berlin.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox