From: "Rebecca Cran" <rebecca@bluestop.org>
To: Laszlo Ersek <lersek@redhat.com>,
devel@edk2.groups.io, philmd@redhat.com,
Liming Gao <liming.gao@intel.com>,
Yonghong Zhu <yonghong.zhu@intel.com>
Subject: Re: [edk2-devel] [PATCH] BaseTools: support arm64 as a platform name in addition to aarch64
Date: Thu, 11 Apr 2019 13:38:55 -0600 [thread overview]
Message-ID: <9f91a70c-bb96-fdcc-1e08-09e3f3f2d511@bluestop.org> (raw)
In-Reply-To: <19000479-83f6-49fb-7a68-e09b31cd0a0e@redhat.com>
On 2019-04-11 11:52, Laszlo Ersek wrote:
> On 04/11/19 16:23, Philippe Mathieu-Daudé wrote:
>> On 4/11/19 5:16 AM, Rebecca Cran via Groups.Io wrote:
>>> Some systems such as FreeBSD identify the platform as 'arm64'
>>> and not 'aarch64' as Linux does.
>> Per https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220297
>> this seems to be a FreeBSD bug.
> You are correct, but that issue was filed on 2017-06-26. I don't think
> we should hold our breaths, as long as the workaround is simple. And, it
> does look simple. (We've worked around worse.)
>
> I do suggest an addition to the patch, however: Rebecca, please add the
> link discovered by Phil near the "arm64" matches, in a comment.
> Something like:
>
> # work around <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220297>
Thanks, I'll do that. I don't think there's anything to fix, because
"uname -m" returns "arm64" and "uname -p" "aarch64". The EDK2 Makefiles
use "uname -m" which I don't think anybody has complained about, but
which return different values on Linux and FreeBSD.
--
Rebecca Cran
next prev parent reply other threads:[~2019-04-11 19:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 3:16 [PATCH] BaseTools: support arm64 as a platform name in addition to aarch64 Rebecca Cran
2019-04-11 13:44 ` [edk2-devel] " Liming Gao
2019-04-11 14:23 ` Philippe Mathieu-Daudé
2019-04-11 17:52 ` Laszlo Ersek
2019-04-11 19:38 ` Rebecca Cran [this message]
2019-04-11 19:55 ` Philippe Mathieu-Daudé
2019-04-11 19:58 ` rebecca
2019-04-11 20:11 ` Philippe Mathieu-Daudé
2019-04-12 7:54 ` Laszlo Ersek
2019-05-02 21:15 ` rebecca
2019-05-03 9:17 ` Laszlo Ersek
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-list 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=9f91a70c-bb96-fdcc-1e08-09e3f3f2d511@bluestop.org \
--to=devel@edk2.groups.io \
/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