All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Esquivel <benjamin.esquivel@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>, Saul Wold <sgw@linux.intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] glibc: 'yes' within the path sets wrong variables
Date: Wed, 25 Feb 2015 12:14:35 -0600	[thread overview]
Message-ID: <1424888075.6730.19.camel@besquive-mobl.amr.corp.intel.com> (raw)
In-Reply-To: <CAJTo0LYsD6SZO71Q6BBnX0td8LZWBeRGWXJ-Ga2LbuWMYN6OHw@mail.gmail.com>

On Wed, 2015-02-25 at 12:23 +0000, Burton, Ross wrote:
> 
> On 24 February 2015 at 22:17, Benjamin Esquivel
> <benjamin.esquivel@linux.intel.com> wrote:
>         > So the configure file does not get regenerated as part of
>         the standard
>         > auto-reconf?
>         >
>         No, if the fix is only applied at the configure.ac file the
>         unwanted
>         behavior still shows up from the configure file.
> 
> Yeah, gcc isn't reconfigured.  Presumably there's a good reason for
> this. :)

Saul, is there a specific part of the glibc's run.do_configure that
should re-conf?

> 
> Ross




  reply	other threads:[~2015-02-25 18:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-23  9:54 [PATCH] glibc: 'yes' within the path sets wrong variables Benjamin Esquivel
2015-02-24 19:40 ` Saul Wold
2015-02-24 22:17   ` Benjamin Esquivel
2015-02-25 12:23     ` Burton, Ross
2015-02-25 18:14       ` Benjamin Esquivel [this message]
2015-02-26 12:22         ` Burton, Ross
2015-02-26 16:17           ` Khem Raj
2015-03-02 16:02             ` [meta-oe][PATCH v2] " Benjamin Esquivel
2015-03-05  8:17               ` [PATCH v3] " Benjamin Esquivel
2015-03-02 16:09             ` [PATCH] " Benjamin Esquivel
2015-02-26 16:18 ` Khem Raj
2015-03-02 16:10   ` Benjamin Esquivel

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=1424888075.6730.19.camel@besquive-mobl.amr.corp.intel.com \
    --to=benjamin.esquivel@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    --cc=sgw@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.