From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id E6157E0049B; Mon, 19 Oct 2015 13:07:16 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -0.0 SPF_HELO_PASS SPF: HELO matches SPF record * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from ptmx.org (ptmx.org [178.63.28.110]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 994FEE00343 for ; Mon, 19 Oct 2015 13:07:12 -0700 (PDT) Received: from [192.168.178.14] (chello062178118086.5.14.vie.surfer.at [62.178.118.86]) by ptmx.org (Postfix) with ESMTPSA id 7F5F42318B; Mon, 19 Oct 2015 22:07:11 +0200 (CEST) To: Otavio Salvador , Ian Coolidge References: <562543CC.5040705@pseudoterminal.org> From: Carlos Rafael Giani Message-ID: <56254D6E.4070409@pseudoterminal.org> Date: Mon, 19 Oct 2015 22:07:10 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: Cc: "meta-freescale@yoctoproject.org" Subject: Re: [meta-fsl-arm-extra] errors while building boundary kernel 3.14.28 X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Oct 2015 20:07:17 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hm, this doesn't fix it :( Am 2015-10-19 um 21:46 schrieb Otavio Salvador: > On Mon, Oct 19, 2015 at 5:26 PM, Carlos Rafael Giani > 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 >