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

Release statically linked executables on Linux #34

Closed
wants to merge 1 commit into from

Conversation

ddeville
Copy link
Contributor

@ddeville ddeville commented Oct 10, 2024

One of the major benefits of dotslash is to be used to bootstrap other tools on pretty much any system. Unfortunately when it comes to linux the executables included in the release are built on Ubuntu 22.04 which means that they link a fairly modern glibc. Trying to use the executable on an older Ubuntu (or any other flavor of Linux that doesn't use glibc) will fail due to linking errors.

We could instead build the binary on a super old linux version but Github only goes back to 20.04 so instead let's produce a fully static executable that statically links the musl libc.

This is a common pattern that many tools built for linux adopt and it will greatly simplify the adoption on linux distros that don't repackage dotslash.

One of the major benefits of dotslash is to be used to bootstrap other
tools on pretty much any system. Unfortunately when it comes to linux
the executables included in the release are built on Ubuntu 22.04 which
means that they link a fairly modern GLIBC. Trying to use the executable
on an older Ubuntu (or any other flavor of Linux that doesn't use GLIBC)
will fail due to linking errors.

We could instead build the binary on a super old linux version but
Github only goes back to 20.04 so instead let's produce a fully static
executable that statically link the musl libc.

This is a common pattern that many tools built for linux adopt and it
will greatly simplify the adoption on linux distros that don't repackage
dotslash.
@facebook-github-bot
Copy link
Contributor

Hi @ddeville!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

@facebook-github-bot
Copy link
Contributor

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

@bolinfest
Copy link
Contributor

I feel like not including musl was just an oversight in the first place, so hopefully this is not controversial @zertosh?

I see buck2 also does musl releases: https://github.com/facebook/buck2/releases

@zertosh
Copy link
Member

zertosh commented Oct 11, 2024

👍

@facebook-github-bot
Copy link
Contributor

@zertosh has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

@facebook-github-bot
Copy link
Contributor

@zertosh merged this pull request in f32d899.

@ddeville ddeville deleted the dev/damien/linux-musl branch October 14, 2024 01:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants