Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/7] ed: Fix EXTRA_OECONF to ensure right compiler is found
Date: Thu, 15 Dec 2011 11:23:25 -0800	[thread overview]
Message-ID: <4EEA492D.9060707@linux.intel.com> (raw)
In-Reply-To: <4EE9B1B6.8050007@linux.intel.com>

On 12/15/2011 12:37 AM, Saul Wold wrote:
> On 12/14/2011 10:56 PM, Khem Raj wrote:
>> On Wed, Dec 14, 2011 at 5:50 PM, Saul Wold<sgw@linux.intel.com> wrote:
>>>
>>> +EXTRA_OECONF = "'CC=${CC}' 'CXX=${CXX}' 'CFLAGS=${CFLAGS}'
>>> 'CXXFLAGS=${CXXFLAGS}' 'CPPFLAGS=${CPPFLAGS}' 'LDFLAGS=${LDFLAGS}'"
>>> +
>>
>> hmm why doesnt it pick it from environment in configure ?
>>
> That's a really good question! But it does not seem to, when I do the
> build with non-gplv3, it gets CC=/usr/bin/gcc! So clearly it's not
> getting the environment, otherwise I would not have made this patch.
>
> This is an old-school configure script.
>
Just a further explanation of this comment, the configure script in ed 
is a very old script, not autotools based at all.  It hard codes the 
CC="" in the script so the environment is not picked up correct, but it 
does read those properly from the command line.

Sau!

> Sau!
>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>



  reply	other threads:[~2011-12-15 19:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-15  1:50 [PATCH 0/7] SSTATE_SCAN_FILES Fix with non-gplv3 and World fixes Saul Wold
2011-12-15  1:50 ` [PATCH 1/7] qt-mobility: Fix QA error for debug files Saul Wold
2011-12-15  1:50 ` [PATCH 2/7] ed: Fix EXTRA_OECONF to ensure right compiler is found Saul Wold
2011-12-15  6:56   ` Khem Raj
2011-12-15  8:37     ` Saul Wold
2011-12-15 19:23       ` Saul Wold [this message]
2011-12-15  1:50 ` [PATCH 3/7] sstate: Add SSTATE_SCAN_FILES Saul Wold
2011-12-15  8:38   ` Saul Wold
2011-12-15 11:12   ` Richard Purdie
2011-12-15  1:50 ` [PATCH 4/7] icu: Add Makefile.inc to SSTATE_SCAN_FILES Saul Wold
2011-12-15  1:50 ` [PATCH 5/7] gmp: Add gmp.h " Saul Wold
2011-12-15  1:50 ` [PATCH 6/7] libtool-cross: Add libtool & libtoolize " Saul Wold
2011-12-15  1:50 ` [PATCH 7/7] perl: add .pl, pm, pod, sh files to SSTATE_SCANE_FILES Saul Wold
2011-12-15 10:26   ` Phil Blundell
2011-12-15 11:14     ` Richard Purdie
2011-12-15 14:46 ` [PATCH 0/7] SSTATE_SCAN_FILES Fix with non-gplv3 and World fixes Richard Purdie

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=4EEA492D.9060707@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox