You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Generally SlackBuild scripts will contain lines like the following after the
executables and dynamic libraries are compiled. The go source however
already contains some executables, so if only the newly generated files
were to be stripped, I might modify the build adding code to strip those
files in bin and libstd.so.
Do the Go developers have an opinion on stripping binaries and libraries?
http://nurmi-labs.blogspot.com/2017/08/bootstrapping-go.html
Generally SlackBuild scripts will contain lines like the following after the
executables and dynamic libraries are compiled. The go source however
already contains some executables, so if only the newly generated files
were to be stripped, I might modify the build adding code to strip those
files in bin and libstd.so.
find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared object" |
grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true
NB: This question is intended to pertain solely to source downloads.
The text was updated successfully, but these errors were encountered: