[GH-ISSUE #2135] 可以支持M1芯片的MacBook吗？ #1699

New issue

Closed

opened 2026-05-05 13:05:25 -06:00 by gitea-mirror · 5 comments

gitea-mirror commented

2026-05-05 13:05:25 -06:00

Owner

Originally created by @jimmyqum on GitHub (Dec 6, 2020).
Original GitHub issue: https://github.com/fatedier/frp/issues/2135

macOS ARM64架构

The solution you want

Alternatives considered

How to implement this function

Application scenarios of this function

Originally created by @jimmyqum on GitHub (Dec 6, 2020). Original GitHub issue: https://github.com/fatedier/frp/issues/2135  macOS ARM64架构 **The solution you want**  **Alternatives considered**  **How to implement this function**  **Application scenarios of this function**

gitea-mirror

2026-05-05 13:05:25 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:05:28 -06:00

Author

Owner

@fatedier commented on GitHub (Dec 7, 2020):

It can be supported when go1.16 is released.

@fatedier commented on GitHub (Dec 7, 2020): It can be supported when go1.16 is released.

gitea-mirror commented

2026-05-05 13:05:28 -06:00

Author

Owner

@witer55 commented on GitHub (Dec 9, 2020):

go1.16 would not release until 2021-02.

@witer55 commented on GitHub (Dec 9, 2020): go1.16 would not release until 2021-02.

gitea-mirror commented

2026-05-05 13:05:29 -06:00

Author

Owner

@YUX commented on GitHub (Dec 19, 2020):

Go 1.16 Beta 1 is released with apple m1 supported
https://groups.google.com/g/golang-announce/c/2-Rj3P5uRLs/m/mYxD2RJkAQAJ?pli=1

@YUX commented on GitHub (Dec 19, 2020): Go 1.16 Beta 1 is released with apple m1 supported https://groups.google.com/g/golang-announce/c/2-Rj3P5uRLs/m/mYxD2RJkAQAJ?pli=1

gitea-mirror commented

2026-05-05 13:05:30 -06:00

Author

Owner

@YUX commented on GitHub (Dec 19, 2020):

#2158

@YUX commented on GitHub (Dec 19, 2020): #2158

gitea-mirror commented

2026-05-05 13:05:30 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 3, 2021):

Issues go stale after 45d of inactivity. Stale issues rot after an additional 10d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Feb 3, 2021): Issues go stale after 45d of inactivity. Stale issues rot after an additional 10d of inactivity and eventually close.