From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dan.rpsys.net (5751f4a1.skybroadband.com [87.81.244.161]) by mail.openembedded.org (Postfix) with ESMTP id F3B716AC3E for ; Thu, 7 May 2015 10:25:05 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by dan.rpsys.net (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id t47AP4xH030836; Thu, 7 May 2015 11:25:04 +0100 Received: from dan.rpsys.net ([127.0.0.1]) by localhost (dan.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id R7ensKrJqFmC; Thu, 7 May 2015 11:25:03 +0100 (BST) Received: from [192.168.3.10] ([192.168.3.10]) (authenticated bits=0) by dan.rpsys.net (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id t47AOlgU030814 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT); Thu, 7 May 2015 11:24:59 +0100 Message-ID: <1430994286.8074.129.camel@linuxfoundation.org> From: Richard Purdie To: Khem Raj Date: Thu, 07 May 2015 11:24:46 +0100 In-Reply-To: <1FEAAD81-09DB-43E7-B162-2567D3B5DD21@gmail.com> References: <4ffe99f25368e8b65df327fb9120ebca1c29e925.1430895556.git.raj.khem@gmail.com> <1430899916.8074.20.camel@linuxfoundation.org> <000AAC87-CE74-45DC-A006-D4704D8841D8@gmail.com> <1430981590.8074.127.camel@linuxfoundation.org> <1FEAAD81-09DB-43E7-B162-2567D3B5DD21@gmail.com> X-Mailer: Evolution 3.12.10-0ubuntu1~14.10.1 Mime-Version: 1.0 Cc: openembedded-core@lists.openembedded.org Subject: Re: [PATCH 5/6] gcc-cross: Pass EXTRA_OECONF_GCC_FLOAT to configure X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 May 2015 10:25:06 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Thu, 2015-05-07 at 00:17 -0700, Khem Raj wrote: > > On May 6, 2015, at 11:53 PM, Richard Purdie wrote: > > We do ship > > an environment file and in that file we have the options gcc needs to > > work, the sysroot, the other cflags and the float abi. Unless we go back > > to a setup of hardcoding the cflags into gcc and have a gcc per set of > > cflags, this isn't going to work since it solves part of the problem but > > not all of it. > > > > its also how the target libraries are compiled should match the ABI flags for target gcc Agreed, the other option is we have gcc pull the right config from the sysroot in question. > > Our other alternative is to wrap gcc with a script (preferred in PATH) > > which ensures the right cflags are present. I'd obviously prefer not to > > do that but it is an option if we believe people can't cope with the > > environment script. > > > > Would solve the cross compile scenario but on-device scenario I am not sure On device is a completely different story. That gcc is target specific and *should* have the right flags set. That isn't what the patch in this thread is about though. On target gcc has always been target specific and will remain so. Cheers, Richard