[GH-ISSUE #2517] 2003 系统下 32位 无法运行frpc #1998

Closed
opened 2026-05-05 13:17:28 -06:00 by gitea-mirror · 7 comments
Owner

Originally created by @bot0577 on GitHub (Aug 6, 2021).
Original GitHub issue: https://github.com/fatedier/frp/issues/2517

2003 系统下 32位 无法运行frpc

Originally created by @bot0577 on GitHub (Aug 6, 2021). Original GitHub issue: https://github.com/fatedier/frp/issues/2517 2003 系统下 32位 无法运行frpc
gitea-mirror 2026-05-05 13:17:28 -06:00
Author
Owner

@blizard863 commented on GitHub (Aug 7, 2021):

提供日志。

<!-- gh-comment-id:894664531 --> @blizard863 commented on GitHub (Aug 7, 2021): 提供日志。
Author
Owner

@fakeboboliu commented on GitHub (Aug 8, 2021):

ws2003 其实是 WinXP,已被抛弃

<!-- gh-comment-id:894754413 --> @fakeboboliu commented on GitHub (Aug 8, 2021): ws2003 其实是 WinXP,已被抛弃
Author
Owner

@luyaotang commented on GitHub (Aug 10, 2021):

可以的。但要降级go版本。目前我会用
go version go1.11 linux/amd64 + frp 0.22来构建一个xp的版本

<!-- gh-comment-id:895676179 --> @luyaotang commented on GitHub (Aug 10, 2021): 可以的。但要降级go版本。目前我会用 go version go1.11 linux/amd64 + frp 0.22来构建一个xp的版本
Author
Owner

@luyaotang commented on GitHub (Aug 14, 2021):

还是要用XP最后一个兼容的版本go1.10.8 linux/amd64才行。go 1.11还是会有些问题

<!-- gh-comment-id:898872377 --> @luyaotang commented on GitHub (Aug 14, 2021): 还是要用XP最后一个兼容的版本go1.10.8 linux/amd64才行。go 1.11还是会有些问题
Author
Owner

@bot0577 commented on GitHub (Aug 14, 2021):

还是要用XP最后一个兼容的版本go1.10.8 linux/amd64才行。go 1.11还是会有些问题

是的啊 找了一个老版本 目前可以用的

<!-- gh-comment-id:898872575 --> @bot0577 commented on GitHub (Aug 14, 2021): > 还是要用XP最后一个兼容的版本go1.10.8 linux/amd64才行。go 1.11还是会有些问题 是的啊 找了一个老版本 目前可以用的
Author
Owner

@gainskills commented on GitHub (Sep 5, 2021):

@bot0577 请问 你用的哪个版本呀? 谢谢

<!-- gh-comment-id:913068535 --> @gainskills commented on GitHub (Sep 5, 2021): @bot0577 请问 你用的哪个版本呀? 谢谢
Author
Owner

@github-actions[bot] commented on GitHub (Oct 6, 2021):

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

<!-- gh-comment-id:935149342 --> @github-actions[bot] commented on GitHub (Oct 6, 2021): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/frp#1998
No description provided.