All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Sutter <ed.sutter@alcatel-lucent.com>
To: buildroot@busybox.net
Subject: [Buildroot] command line regular expression substitution fails
Date: Thu, 09 Jan 2014 15:11:51 -0500	[thread overview]
Message-ID: <52CF0287.8010505@alcatel-lucent.com> (raw)
In-Reply-To: <CAOkaJuVGa4_Et8TL80MEsh8sN1mseKvQ4OZ9RzxSouytbZFUFQ@mail.gmail.com>

>
> Ed,
>
> On Wed, Jan 8, 2014 at 5:31 AM, Ed Sutter 
> <ed.sutter at alcatel-lucent.com <mailto:ed.sutter@alcatel-lucent.com>> 
> wrote:
>
>     The iMX6 is a Cortex A9; however, looking at my notes, I see that
>     the instructions
>     I got this from say to use Cortex A8.  When I make that one
>     change, this problem goes away...
>     How is it that changing from A9 (valid for iMX6) to A8 would
>     affect command line regular
>     expression parsing?
>     Ed
>
>
> I wish I had an explanation for you, but I don't. Perhaps someone else 
> on the list can shed some light onto what is happening here.
>
> -Peter
Thanks, the strange thing in my case is the iMX6 is cortex-A9, but I had 
to step back to
cortex-A8 in menuconfig for this to work.
I did notice that when I use A9 vs A8, the floating point settings 
automatically change
in menuconfig.  I *thought* A8 & A9 were the same from that standpoint, 
but not really
sure.  Anyway, I plan to spend at least the next few days looking into 
this, so hopefully I'll
have more information soon.

Ed

  reply	other threads:[~2014-01-09 20:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-07 21:33 [Buildroot] command line regular expression substitution fails Ed Sutter
2014-01-07 22:20 ` Thomas Petazzoni
2014-01-08 12:32   ` Ed Sutter
2014-01-07 23:07 ` Peter Sanford
2014-01-08 13:31   ` Ed Sutter
2014-01-09 17:34     ` Peter Sanford
2014-01-09 20:11       ` Ed Sutter [this message]
2014-01-28 21:10         ` Thomas Petazzoni
2014-01-29  6:49           ` Arnout Vandecappelle
2014-01-29  8:26             ` Thomas Petazzoni

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=52CF0287.8010505@alcatel-lucent.com \
    --to=ed.sutter@alcatel-lucent.com \
    --cc=buildroot@busybox.net \
    /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.