golang/go

x/sys/plan9: function Exit causes build failure

Open

#78,506 opened on 2026年4月2日

GitHub で見る
 (6 comments) (0 reactions) (0 assignees)Go (133,883 stars) (19,008 forks)batch import
BugReportNeedsInvestigationOS-Plan9help wanted

説明

package main

import "golang.org/x/sys/plan9"

func main() { plan9.Exit(0) }

This doesn't build

$ GOARCH=amd64 GOOS=plan9 go build
# test
golang.org/x/sys/plan9.exit: relocation target syscall.exit not defined

plan9.Exit calls plan9.exit, which is an assembly stub that jumps to syscall.exit. But there is no syscall.exit in the syscall package on Plan 9.

If the function is not needed (as it clearly doesn't work so nobody is using it), we probably can delete it. If it is needed for some reason, it could just call syscall.Exit, in Go code, not assembly.

cc @golang/plan9

コントリビューターガイド

技術スタック
go
領域
backend
Issue 種別
bug
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
2
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
under 1 hour
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
fresh
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
Go programming knowledgebasic understanding of syscalls
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
75
調査方針
The issue is a build failure in the plan9.Exit function. The function currently calls an assembly stub that jumps to syscall.exit, which doesn't exist on Plan 9. Two solutions are proposed: delete the function entirely or rewrite it to call syscall.Exit directly in Go code. To implement, locate the file containing the plan9.Exit function in the golang.org/x/sys/plan9 package. The assembly stub for exit may be in a .s file. The fix is straightforward: either remove the exit function and its assembly stub, or replace the assembly implementation with a Go function that calls syscall.Exit. No linked PRs or maintainer questions in the comments.