From: Mike Crowe <mac@mcrowe.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] kernel.bbclass: Add dependency on binutils
Date: Mon, 20 May 2013 21:29:32 +0100 [thread overview]
Message-ID: <20130520202932.GA25090@mcrowe.com> (raw)
In-Reply-To: <B646CCF4-2E7C-4135-AD1D-D72E0827C779@gmail.com>
On Mon, May 20, 2013 at 10:37:08AM -0700, Khem Raj wrote:
>
> On May 20, 2013, at 5:22 AM, Mike Crowe <mac@mcrowe.com> wrote:
>
> > Compiling the Linux kernel requires binutils; kernel.bbclass uses
> > INHIBIT_DEFAULT_DEPS so it had better depend on binutils explicitly.
> >
> > (The lack of this dependency isn't always a problem because binutils
> > is required to build gcc-cross but if gcc-cross is reconstructed from
> > the sstate cache then gcc-cross's dependency on binutils-cross is
> > ignored due to being in the safe dependency list in
> > setscene_depvalid.)
>
> what good is cross-gcc without cross-binutils. Could it be fixed in gcc recipes instead so
> it pulls binutils-cross
Perhaps it could do when considering requiring binutils to be an
implementation detail of gcc. Unfortunately sstate.bbclass doesn't honour
the dependency (presumably because other recipes that depend on binutils
directly don't wish to bring in all the binutils build dependencies
unnecessarily.) What is the best way to avoid this?
But, kernel compilation also requires the ability to call binutils directly
so it doesn't feel completely wrong for the kernel class to depend on
binutils directly too.
Mike.
next prev parent reply other threads:[~2013-05-20 20:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 12:22 [PATCH] kernel.bbclass: Add dependency on binutils Mike Crowe
2013-05-20 17:37 ` Khem Raj
2013-05-20 20:29 ` Mike Crowe [this message]
2013-05-20 22:25 ` Richard Purdie
2013-05-21 8:41 ` Mike Crowe
2013-06-13 14:06 ` [PATCH] sstate.bbclass: binutils-cross is not a safe dependency Mike Crowe
2013-06-13 15:00 ` Richard Purdie
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=20130520202932.GA25090@mcrowe.com \
--to=mac@mcrowe.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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