All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Poky <poky@lists.pokylinux.org>
Subject: Re: eglibc configurability
Date: Mon, 07 Feb 2011 16:57:43 +0000	[thread overview]
Message-ID: <1297097863.1350.17229.camel@rex> (raw)
In-Reply-To: <4D5023D8.7090106@mlbassoc.com>

On Mon, 2011-02-07 at 09:54 -0700, Gary Thomas wrote:
> On 02/07/2011 09:29 AM, Mark Hatle wrote:
> > Could you find the related init script and point me to the contents.  I don't
> > see any initscripts in the eglibc integration.  The only thing I see is a switch
> > in the locale generation between on target, on host and via QEMU.  I'm wondering
> > if maybe this is being triggered?
> 
> This could be what I'm seeing.  I have ENABLE_BINARY_LOCALE_GENERATION disabled
> in my local.conf (I had troubles with QEMU-ARM on Fedora in the past and this
> was the way around it).  It looks like that may be pushing the locale compilation
> to the target.

Correct. The locales have to be generated somewhere!

You turned them off on the build machine so they run on the target. All
is functioning as it should.

FWIW, cross locale gen doesn't use qemu now and is a lot faster so
perhaps you could turn it back on ;-).

Cheers,

Richard





  reply	other threads:[~2011-02-07 16:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-07 14:44 eglibc configurability Gary Thomas
2011-02-07 15:45 ` Kamble, Nitin A
2011-02-07 15:54   ` Gary Thomas
2011-02-07 16:06 ` Richard Purdie
2011-02-07 16:19   ` Gary Thomas
2011-02-07 16:29     ` Mark Hatle
2011-02-07 16:54       ` Gary Thomas
2011-02-07 16:57         ` Richard Purdie [this message]
2011-02-07 17:04           ` Mark Hatle
2011-02-07 17:57             ` Gary Thomas
2011-02-07 19:09               ` Mark Hatle
2011-02-07 16:55       ` 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=1297097863.1350.17229.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=gary@mlbassoc.com \
    --cc=poky@lists.pokylinux.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 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.