All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: meta-freescale@yoctoproject.org
Subject: Re: [meta-fsl-arm-extra] errors while building boundary kernel 3.14.28
Date: Mon, 19 Oct 2015 14:12:20 -0600	[thread overview]
Message-ID: <56254EA4.3060500@mlbassoc.com> (raw)
In-Reply-To: <56254D6E.4070409@pseudoterminal.org>

On 2015-10-19 14:07, Carlos Rafael Giani wrote:
> Hm, this doesn't fix it :(

What rev of meta-fsl-arm-extra are you using?
Ian posted some updates to this recipe recently - perhaps you could try them?

>
> Am 2015-10-19 um 21:46 schrieb Otavio Salvador:
>> On Mon, Oct 19, 2015 at 5:26 PM, Carlos Rafael Giani
>> <dv@pseudoterminal.org> wrote:
>>> I tried to build an image for a nitrogen6x, using the newest master version
>>> of Poky, meta-openembedded, and meta-fsl-arm & meta-fsl-arm-extra. However,
>>> the kernel doesn't compile. I get lots of errors like:
>>>
>>> | arch/arm/mm/cache-l2x0.o: In function `nop_flush_kern_cache_louis':
>>> | cache-l2x0.c:(.text+0xa38): multiple definition of
>>> `nop_flush_kern_cache_louis'
>>> | arch/arm/mm/dma-mapping.o:dma-mapping.c:(.text+0x1438): first defined here
>>> | arch/arm/mm/cache-l2x0.o: In function `nop_flush_user_cache_all':
>>> | cache-l2x0.c:(.text+0xa48): multiple definition of
>>> `nop_flush_user_cache_all'
>>> | arch/arm/mm/dma-mapping.o:dma-mapping.c:(.text+0x1448): first defined here
>>> | arch/arm/mm/cache-l2x0.o: In function `nop_flush_user_cache_range':
>>> | cache-l2x0.c:(.text+0xa58): multiple definition of
>>> `nop_flush_user_cache_range'
>>> | arch/arm/mm/dma-mapping.o:dma-mapping.c:(.text+0x1458): first defined here
>>>
>>> At least one other person apparently had the same problem, since I found
>>> this log paste: http://pastebin.com/rwu5a6ru
>>>
>>> Any ideas what's the cause?
>> Yes; it needs:
>>
>> https://github.com/Freescale/linux-fslc/commit/22f692548037e39809c32759b5600ee066ef59e9.patch
>>
>

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


  reply	other threads:[~2015-10-19 20:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-19 19:26 [meta-fsl-arm-extra] errors while building boundary kernel 3.14.28 Carlos Rafael Giani
2015-10-19 19:46 ` Otavio Salvador
2015-10-19 20:07   ` Carlos Rafael Giani
2015-10-19 20:12     ` Gary Thomas [this message]
2015-10-19 20:33       ` Carlos Rafael Giani
2015-10-20 11:21     ` Otavio Salvador
2015-10-21  7:29       ` Carlos Rafael Giani
2015-10-21  7:30         ` Carlos Rafael Giani
2015-10-21 12:31         ` Otavio Salvador
2015-10-21 17:59           ` Carlos Rafael Giani
2015-10-21 18:01             ` Otavio Salvador
2015-10-21 18:02             ` Sundararaj Prabhu
2015-10-21 18:11               ` Carlos Rafael Giani
2015-10-21 18:21                 ` Otavio Salvador
2015-10-21 18:25                   ` Carlos Rafael Giani

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=56254EA4.3060500@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=meta-freescale@yoctoproject.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.