From: Denys Dmytriyenko <denys@ti.com>
To: Jack Mitchell <ml@communistcode.co.uk>
Cc: meta-ti@yoctoproject.org
Subject: Re: New KERNEL_CCSUFFIX
Date: Mon, 21 Jan 2013 13:30:20 -0500 [thread overview]
Message-ID: <20130121183020.GA15396@edge> (raw)
In-Reply-To: <50FD1AC4.1050506@communistcode.co.uk>
On Mon, Jan 21, 2013 at 10:39:00AM +0000, Jack Mitchell wrote:
> Morning all,
>
> With Khems recent 'kernel.bbclass, module-base.bbclass: Use CC to
> form KERNEL_CC' patch, it seems the kernel compile in meta-ti is now
> knackered.
>
> I get the error message:
>
> ERROR: Nothing PROVIDES
> 'virtual/arm-oecore-linux-gnueabi-gcc${KERNEL_CCSUFFIX}'
>
> Which I guess is related to line 120 in multi-kernel.inc - I have
> tried to understand what the changes that Khem made are but it goes
> a bit above my comprehension level unfortunately. So I was wondering
> if anyone has a patch or any suggestions on how to get this going
> again?
Jack,
Thanks. I'm already looking into multi-kernel.inc due to other issues, so I'll
try to fix this one as well. No ETA though... :)
--
Denys
prev parent reply other threads:[~2013-01-21 18:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 10:39 New KERNEL_CCSUFFIX Jack Mitchell
2013-01-21 18:30 ` Denys Dmytriyenko [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=20130121183020.GA15396@edge \
--to=denys@ti.com \
--cc=meta-ti@yoctoproject.org \
--cc=ml@communistcode.co.uk \
/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.