SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Thanks. I think it is the instinct of avoiding bloat and keep things simple but functional that motivates me for this project.
Musl devs says that it's advantages over other libc's are "size, correctness, static linking support, and clean code".
Hard to say if it brings some perfomance boost, more likely it saves some ram.
At least it brings independence from glibc, and works surprisingly well.
On my 10 Years old lenovo laptop i compiled qt5 against musl, where it failed for some reasons(ram/swap if i remember correctly)
to compile qt5 with slackware 14.2/glibc.
I also like the attitude of the main developer from musl, here is a comment from him on a vte bugreport regarding musl.
I've added some more packages, http://computer-nr3.de/muskat64-current/ChangeLog.txt
The "rust" package doesn't build yet and is a showstopper, as mozjs78 and others depend on it, on mozjs78 in turn does polkit and others depend on etc.
809 out of 1557 builds are compiled, 748 builds to go.
I've added some more packages, http://computer-nr3.de/muskat64-current/ChangeLog.txt
The "rust" package doesn't build yet and is a showstopper, as mozjs78 and others depend on it, on mozjs78 in turn does polkit and others depend on etc.
809 out of 1557 builds are compiled, 748 builds to go.
Nice... I am myself in the process of moving/adding my system from glibc to musl so might look to you for ideas if necessary.
I am not used to musl whatsoever so will take considerable auditing and patching before I got this sorted no doubt.
rust is an annoyance when it comes to bootstrapping. Are you using mrustc to bootstrap it or? Just doing a static downloaded seed ?
rust is an annoyance when it comes to bootstrapping. Are you using mrustc to bootstrap it or? Just doing a static downloaded seed ?
I didn't knew of mrustc. What didn't work for bootstrapping was manual installation of rust/cargo, as the installed version of rust on the system needs to be max. one version off to version to be build.
What worked here to build rust 1.48.0 was the following(adapted from the slackware buildscripts), download
thats very very nice a port too musl sounds great, what about gcompat package, that would help to run glibc packages in musl.
Thanks for that hint, didn't know about gcompat.
I think about providing an extra repository for packages like that to make it more inviting to try out the port, but the port/packages itself should stay as near as possible to slackware, so no extra packages which aren't absolutely needed there.
Btw., i made some progress, some more packages were added, X is working now. I installed the port a laptop, and i could login into xfce :-)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.