From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 411CBE0092E; Tue, 31 Mar 2015 08:40:56 -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=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-HAM-Report: * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (picmaster[at]mail.bg) * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [193.201.172.118 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature Received: from mx2.mail.bg (mx2.mail.bg [193.201.172.118]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id E8635E00837 for ; Tue, 31 Mar 2015 08:40:49 -0700 (PDT) Received: from [192.168.0.59] (unknown [93.152.143.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx2.mail.bg (Postfix) with ESMTPSA id 18CC86007635; Tue, 31 Mar 2015 18:40:48 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mail.bg; s=default; t=1427816448; bh=rsCugkj3aProZKMiUt3XYh8/kd19rNe3bE/qLBptl+8=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=/Py6YFQyv15WHIw7U0TMEvT+1KkM29D/DVAn5c27twFKkiFnYcgWrXcIojNip+rT+ N+qxfqd8V3QVelFSV92Sbf0Ro2e3wLznuHT39QUMke9S8wgPRh5T+Asw+ja/pjLBtx 6uFDk+WyyAcSN1yRZDhZnYMHgBqkQRWY29cb+Noc= Message-ID: <551ABFFF.5050508@mail.bg> Date: Tue, 31 Mar 2015 18:40:47 +0300 From: Nikolay Dimitrov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.5.0 MIME-Version: 1.0 To: Matt Madison References: <1427804374.4556.6.camel@workhorse.madison.systems> In-Reply-To: Cc: meta-freescale@yoctoproject.org, ad me Subject: Re: Yocto dizzy version 1.7.1 cross compiling meta-toolchain BROKEN for weeks now! 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: Tue, 31 Mar 2015 15:40:56 -0000 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Hi Matt, others, On 03/31/2015 05:46 PM, Matt Madison wrote: > On Tue, Mar 31, 2015 at 7:26 AM, ad me wrote: >> >> On Mar 31, 2015 5:19 AM, "Matt Madison" wrote: > [...] >>> You probably aren't invoking the compiler with the set of command-line >>> options you need to get the desired output. See the definition of the >>> CC environment variable in the environment-setup script in the SDK, and >>> make sure you use the same set of flags to invoke gcc. >>> >>> -Matt >> >> Please see the step by step in the document attached/linked. >> The same one you highlighted on. >> >> I source this script just before invoking the compiler. Which means the CC >> parameters are passed in as shown. >> >> Unless if you are suggesting that doing a "source" of the environment script >> is not enough? >> >> If so, then I would not be able to invoke the correct compiler as the PATH >> to it is setup by the same environment script I source. > > > Sourcing the environment script is not enough; as I said, you have to > run the compiler with the right set of options. > > So instead of: > > arm-poky-linux-gnueabi-gcc hello_arm_world.c > > You could do: > > $CC hello_arm_world.c > > to use the CC environment variable directly to invoke the compiler > with the options you need. > > -Matt That was a good remark. I just checked a Makefile I've written for a customer project, here's how I use gcc for the cross-compiled recipe: CC=$(CROSS_COMPILE)gcc This works for me both in Yocto builds and during stand-alone development with "whatever cross-toolchain is around". Regards, Nikolay