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

Link statically against musl libc #24

Closed
tailhook opened this issue Apr 21, 2015 · 5 comments
Closed

Link statically against musl libc #24

tailhook opened this issue Apr 21, 2015 · 5 comments

Comments

@tailhook
Copy link
Owner

Currently we kinda rely on unsupported and buggy feature of linking against glibc. Should instead link against musl libc

Some info: https://gist.github.com/cl91/bb927df2525738502131#file-static-linking-against-musl-md

@bstrie
Copy link

bstrie commented May 5, 2015

This is now supported in the nightly version of the Rust compiler, on an experimental basis:

rust-lang/rust#24777

@aidanhs
Copy link

aidanhs commented May 10, 2015

I'm curious - why do you say this is buggy?

@tailhook
Copy link
Owner Author

I'm curious - why do you say this is buggy?

  1. Some functions are two order of magnitude slower (e.g. clock_gettime)
  2. glibc still tries to use *.so plugins even if statically built. When they are absent on system (e.g. in container), it's ok (except some function don't work). But on host system when .so plugins files are not ABI-compatible with glibc compiled into vagga, it just crashes with segmentation fault.

To name a few, just from the top of my head.

@aidanhs
Copy link

aidanhs commented May 12, 2015

Gotcha, was aware of these, just wanted to check there are no others. Thanks :)

@tailhook
Copy link
Owner Author

It's done in master. Will do some testing before the release though.

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

3 participants