Go build -buildmode=c-shared . Is regenerating the library everytime (timestamp change is observed) even though there is no change in the source #64832

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.

Sign up for GitHub

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

Jump to bottom

Closed

chendu471 opened this issue Dec 21, 2023 · 1 comment

Labels

chendu471 commented Dec 21, 2023 •

edited

Loading

Using the go version 1.19.10, is there any extra build flags to use to overcome this ?. We are already using the GOCACHE.

chendu471 changed the title ~~Go build -buildmode=c-shared . Is regenerating the library everytime even though there is no change in the source~~ Go build -buildmode=c-shared . Is regenerating the library everytime (timestamp change is observed) even though there is no change in the source

Contributor

thanm commented Dec 21, 2023

Please see #47788 (comment) , which describes why we are not fixing bugs in shared build mode, with its attendant problems.

thanm closed this as completed

golang locked and limited conversation to collaborators

gopherbot added the FrozenDueToAge label

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.