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.
Well, it _should_ work. Not using huge+initrd, correct?
Anyway, as far as changing crc32c from built-in to a module, I'm inclined to go WONTFIX on that because it complicates things needlessly. Here's a reference to what went on in Fedora:
Have you actually tested building crc32c as a module and found that it solved the issue? If it's working built-in in Fedora, I'd be surprised if changing crc32c to a module would fix things here. They do build libcrc32c as a module, but the btrfs documentation says that it can also be built into the kernel. If that were not already working, I don't think btrfs would function at all.
I searched for benchmarks on how much hardware accelerated crc32c support would help btrfs, and the closest thing I could find was someone saying any performance gain would be "slight".
Well, it _should_ work. Not using huge+initrd, correct?
I don't even have huge installed.
Quote:
Originally Posted by volkerdi
Have you actually tested building crc32c as a module and found that it solved the issue?
I am not going to build a kernel with many unnecessary options on, it will takes lots of time, and
as stated before the it works on fedora so the problem may come from CONFIG_LIBCRC32C.
Quote:
Originally Posted by volkerdi
They do build libcrc32c as a module, but the btrfs documentation says that it can also be built into the kernel. If that were not already working, I don't think btrfs would function at all.
But it works on Arch, Debian and Fedora.
Quote:
Originally Posted by volkerdi
I searched for benchmarks on how much hardware accelerated crc32c support would help btrfs, and the closest thing I could find was someone saying any performance gain would be "slight".
Any thoughts on making the GCC libraries their own package? I have some software that links against libatomic which is forcing me to install the entire GCC compiler on a server, which is unwanted.
Slackware doesn't split packages like any other Linux distribution. You will get a single package consisting all files, including main program, documentations, and libraries.
Slackware doesn't split packages like any other Linux distribution. You will get a single package consisting all files, including main program, documentations, and libraries.
I totally understand that, I've been using slackware for more than 15 years, but.... Slackware does split off openssl-solibs, glibc-solibs, and seamonkey-solibs. So gcc-solibs isn't unreasonable if software needs those libraries but you don't want the entire gcc suite.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.