From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/freerdp: do not use Neon extensions when not available
Date: Sun, 28 Dec 2014 12:33:56 +0100 [thread overview]
Message-ID: <20141228113356.GA4254@free.fr> (raw)
In-Reply-To: <8761cwdn90.fsf@dell.be.48ers.dk>
Peter, All,
On 2014-12-28 12:31 +0100, Peter Korsgaard spake thusly:
> >>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
>
> > FreeRDP mis-detects the CPU, and may enable Neon extensions when it
> > should not. Not all ARM processors have Neon extensions.
>
> > Heck, what's more, none non-ARM processor has Neon extensions!
> > The regexp to detect the CPU is borked: 'arm*' will also match 'arc'
> > as well as 'arm'.
>
> Huh, how does arm* march arc?
Already answered on IRC, but for the records: this is not a glob, this
is a regexp.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2014-12-28 11:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-27 18:16 [Buildroot] [PATCH 0/2] FreeRDP: misc arch-related fixes (branch yem/fixes) Yann E. MORIN
2014-12-27 18:16 ` [Buildroot] [PATCH 1/2] package/freerdp: do not use Neon extensions when not available Yann E. MORIN
2014-12-28 11:31 ` Peter Korsgaard
2014-12-28 11:33 ` Yann E. MORIN [this message]
2014-12-28 11:37 ` Peter Korsgaard
2014-12-27 18:16 ` [Buildroot] [PATCH 2/2] package/freerdp: do not use SSE2 " Yann E. MORIN
2014-12-27 19:00 ` [Buildroot] [PATCH 0/2] FreeRDP: misc arch-related fixes (branch yem/fixes) 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=20141228113356.GA4254@free.fr \
--to=yann.morin.1998@free.fr \
--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.