Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: package runtime/trace is not in GOROOT #1997

Closed
omar391 opened this issue Jul 12, 2021 · 3 comments
Closed

Bug: package runtime/trace is not in GOROOT #1997

omar391 opened this issue Jul 12, 2021 · 3 comments

Comments

@omar391
Copy link

omar391 commented Jul 12, 2021

I am having this issue while trying to compile my program to -target wasm:

tinygo build -o ./nodejs/lib-tiny.wasm -target wasm ./main.go

It throws this error:
C:\Users\**\go\pkg\mod\[email protected]\trace\trace_go11.go:21:2: package runtime/trace is not in GOROOT (C:\Users\**\AppData\Local\tinygo\goroot-go1.16.5-b6761f345c63a2cb198265aef5bcc7da1c2af2c14394faa25cfb608af5b42a9c\src\runtime\trace)

Is there a way to print more build error stack trace info and any solution for the package runtime/trace issue?

Tinygo env:
image

Similar issues in another repo: benthosdev/benthos-lab#22
Best.

@wolverian
Copy link

wolverian commented Dec 9, 2021

This also breaks OpenTelemetry unfortunately:

/Users/ii/go/pkg/mod/go.opentelemetry.io/otel/[email protected]/trace/span.go:22:2:
  package runtime/trace is not in GOROOT (/Users/ii/Library/Caches/tinygo/goroot-go1.17.3-0235e5915a10fdaa87b6f2130d112a9a9ae3c9c24c9419c23e81c7c218fa6161-syscall/src/runtime/trace)

@dgryski
Copy link
Member

dgryski commented Dec 9, 2021

I don't think it would be difficult to build a tinygo-specific runtime/trace package that exports the same API, but obviously the functionality would be minimal as the tinygo runtime doesn't actually support the required tracing features. That would allow these packages to build, but not run with the identical feature set.

@joeshaw
Copy link
Contributor

joeshaw commented Sep 8, 2022

This is fixed by #3117 but I don't have perms to close this ticket.

@dgryski dgryski added the next-release Will be part of next release label Sep 8, 2022
@omar391 omar391 closed this as completed Sep 12, 2022
@deadprogram deadprogram removed the next-release Will be part of next release label Sep 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants