From: adr <adr@SDF.ORG>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Aarch64 on labs|9legacy?jj
Date: Sat, 21 May 2022 17:53:19 +0000 (UTC) [thread overview]
Message-ID: <f61fc561-dbeb-1724-fce0-dbbb0f280c0@SDF.ORG> (raw)
In-Reply-To: <7397b2cb-f34c-2616-885d-7a311432b103@fjrhome.net>
On Sat, 21 May 2022, Frank D. Engel, Jr. wrote:
> The compiler appears to be called 7c.
>
> adr, looking at the original email on this thread, it is not very clear what
> you are trying to ask?
There is no 7c on labs' , there is no patch for aarch64, arm64 or
whatever you want to call it in 9legacy. There is no kernel for
any aarch64 machine on labs/legacy. Seriously, what is so hard to
understand in this frase:
has someone done something with aarch64 on labs|9legacy?
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T7409a8df6326c959-Me5fa713e684fc24bd81b552f
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2022-05-21 17:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 19:35 [9fans] Aarch64 on labs|9legacy? adr
2022-05-20 20:34 ` Charles Forsyth
2022-05-20 21:25 ` adr
2022-05-21 16:13 ` Aram Hăvărneanu
2022-05-21 16:39 ` ori
2022-05-21 17:06 ` Frank D. Engel, Jr.
2022-05-21 17:53 ` adr [this message]
2022-05-21 18:00 ` [9fans] Aarch64 on labs|9legacy?jj Aram Hăvărneanu
2022-05-21 17:15 ` [9fans] Aarch64 on labs|9legacy? adr
2022-05-21 17:11 ` adr
2022-05-21 17:38 ` Aram Hăvărneanu
2022-05-21 18:01 ` adr
2022-05-21 18:04 ` Aram Hăvărneanu
2022-05-22 0:05 ` Dan Cross
2022-05-22 0:26 ` adr
2022-05-22 14:36 ` hiro
2022-05-22 14:43 ` Dan Cross
2022-05-22 16:29 ` hiro
2022-05-21 17:43 ` Thaddeus Woskowiak
2022-05-22 18:18 ` Charles Forsyth
2022-05-22 20:15 ` adr
2022-05-22 20:33 ` Dan Cross
2022-05-22 22:16 ` hiro
2022-05-23 14:41 ` Charles Forsyth
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=f61fc561-dbeb-1724-fce0-dbbb0f280c0@SDF.ORG \
--to=adr@sdf.org \
--cc=9fans@9fans.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).