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

Adding support for Linux + musl #322

Open
aschmahmann opened this issue Oct 23, 2020 · 4 comments
Open

Adding support for Linux + musl #322

aschmahmann opened this issue Oct 23, 2020 · 4 comments
Labels
dif/medium effort/hours Estimated to take one or several hours help wanted Seeking public contribution on this issue kind/enhancement A net-new feature or improvement to an existing feature P3 Low: Not priority right now status/ready Ready to be worked

Comments

@aschmahmann
Copy link
Contributor

aschmahmann commented Oct 23, 2020

As noted in ipfs/fs-repo-migrations#111 we very briefly supported building for musl libc alternative to the more common glibc in 2017 and then stopped.

If it's not too painful to support it'd be nice if we could build with support for musl as well as glibc. Note: we need to support building with CGO enabled for things like plugins or OS specific optimizations so just ignoring libc entirely isn't really an option.

It looks like we used to only support x64 linux + musl back in 2017. I suspect that's enough for the most common use case (alpine linux in docker images), but we could potentially build more as well.

@aschmahmann aschmahmann added the need/triage Needs initial labeling and prioritization label Oct 23, 2020
@ipfs ipfs deleted a comment from welcome bot Oct 26, 2020
@jessicaschilling
Copy link
Contributor

@aschmahmann I'm afraid there isn't bandwidth on the GUI team right now to tackle this -- if it's something you or @olizilla might be willing to look into, though, that would be great.

@jessicaschilling jessicaschilling added dif/medium effort/hours Estimated to take one or several hours help wanted Seeking public contribution on this issue kind/enhancement A net-new feature or improvement to an existing feature P3 Low: Not priority right now status/ready Ready to be worked and removed need/triage Needs initial labeling and prioritization labels Oct 26, 2020
@jessicaschilling
Copy link
Contributor

@aschmahmann Alternately -- if you think this is a potential good bounty fit, do you mind writing up bounty specs and we'll get it on the board?

@TheDiscordian
Copy link
Member

TheDiscordian commented May 6, 2021

This feature was asked about in the #ipfs chat room today (here). So others may be interested in this as well, is the bounty live?

@Stebalien
Copy link
Member

There is no bounty at the moment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dif/medium effort/hours Estimated to take one or several hours help wanted Seeking public contribution on this issue kind/enhancement A net-new feature or improvement to an existing feature P3 Low: Not priority right now status/ready Ready to be worked
Projects
None yet
Development

No branches or pull requests

4 participants