From: "Jérémy Rosen" <jeremy.rosen@smile.fr>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/8] [autotools] export CCLD_FOR_BUILD
Date: Thu, 25 Aug 2016 14:40:34 +0200 [thread overview]
Message-ID: <cd135782-5368-e383-1e13-7763c3075a4b@smile.fr> (raw)
In-Reply-To: <CAJTo0LZ_44oh+u0Muv=qu7Qj4eUfHBvoS4pVrND8bZqY0EZPhg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1331 bytes --]
On 24/08/2016 21:56, Burton, Ross wrote:
>
> On 24 August 2016 at 12:28, Jérémy Rosen <jeremy.rosen@smile.fr
> <mailto:jeremy.rosen@smile.fr>> wrote:
>
> ok, so CC_FOR_BUILD seems to be a common convention and
> CCLD_FOR_BUILD seems only used by our patch for pcre. Fixing it to
> use CC_FOR_BUILD for linking is trivial
>
> but the patch is marked as submitted upstream, so Fahad... what is
> the status ? how can we do that ?
>
> I can also set CCLD_FOR_BUILD in ther .bb file instead of
> autotools.bbclass, that's trivial... the question is whether we
> should fix the patch or not...
>
>
> CC_FOR_BUILD and CPP_FOR_BUILD are de facto standards by virtue of
> being part of autoconf-archive:
> https://www.gnu.org/software/autoconf-archive/ax_prog_cc_for_build.html
>
> Looking at the patch wouldn't it be possible to avoid the entire .c ->
> .o -> binary process and just go from .c -> binary via CC_FOR_BUILD?
Probably, but again the patch has been pushed upstream by someone else
and I need to contact that person first to see how to handle it.
I can avoid that by defining CCLD_FOR_BUILD in the recipe, but since I
need to wait for glibc for v2 anyway, I'm not in a rush...
if I have no news, I'll do that for V2
Regards
Jeremy
>
> Ross
[-- Attachment #2: Type: text/html, Size: 2983 bytes --]
next prev parent reply other threads:[~2016-08-25 12:40 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 7:25 [PATCH 0/8] Fix BUILD_* family of variables Jérémy Rosen
2016-08-23 7:25 ` [PATCH 1/8] [autotools] export CCLD_FOR_BUILD Jérémy Rosen
2016-08-24 0:50 ` Khem Raj
2016-08-24 11:05 ` Jérémy Rosen
2016-08-24 11:28 ` Jérémy Rosen
2016-08-24 19:56 ` Burton, Ross
2016-08-25 12:40 ` Jérémy Rosen [this message]
2016-08-25 13:27 ` Burton, Ross
2016-08-23 7:25 ` [PATCH 2/8] [cross] export CC family from BUILD_* for cross compilers Jérémy Rosen
2016-08-23 13:34 ` Peter Kjellerstedt
2016-08-23 14:46 ` Burton, Ross
2016-08-23 14:49 ` Jérémy Rosen
2016-08-23 7:25 ` [PATCH 3/8] [rpm] force a configure before make distclean Jérémy Rosen
2016-08-23 16:54 ` Burton, Ross
2016-08-23 17:16 ` Mark Hatle
2016-08-24 7:44 ` Jérémy Rosen
2016-08-24 14:13 ` Mark Hatle
2016-08-24 14:17 ` Jérémy Rosen
2016-08-24 14:42 ` Mark Hatle
2016-08-23 7:25 ` [PATCH 4/8] [linux-yocto] allow overriding compiler name in KConfig Jérémy Rosen
2016-08-23 13:36 ` Bruce Ashfield
2016-08-23 13:41 ` Bruce Ashfield
2016-08-23 13:48 ` Jérémy Rosen
2016-08-23 13:43 ` Jérémy Rosen
2016-08-23 7:25 ` [PATCH 5/8] [linux-libc-headers] " Jérémy Rosen
2016-08-23 13:39 ` Bruce Ashfield
2016-08-24 1:06 ` Khem Raj
2016-08-24 7:45 ` Jérémy Rosen
2016-08-23 7:25 ` [PATCH 6/8] [busybox] " Jérémy Rosen
2016-08-23 7:25 ` [PATCH 7/8] [sanity] fix hardcoded references to gcc Jérémy Rosen
2016-08-23 14:53 ` Burton, Ross
2016-08-23 15:11 ` Burton, Ross
2016-08-23 15:40 ` Jérémy Rosen
2016-08-24 7:47 ` Jérémy Rosen
2016-08-23 7:25 ` [PATCH 8/8] [glibc] remove hard-coded reference to gcc -E Jérémy Rosen
2016-08-23 14:03 ` Burton, Ross
2016-08-23 14:04 ` Jérémy Rosen
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=cd135782-5368-e383-1e13-7763c3075a4b@smile.fr \
--to=jeremy.rosen@smile.fr \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox