<![CDATA[Topics tagged with slackware]]>https://bbs.spacc.eu.org/new/tags/slackwareRSS for NodeSun, 08 Nov 2026 17:25:56 GMTInvalid Date60<![CDATA[Building Chromium for Slackware (contd.)]]>Building Chromium for Slackware (contd.)

It's been 'fun' compiling the newest Cheomium 143 sources... as usual when Google updates the major version number. Again, it is momentarily not possible to compile the Chromium sources using Slackware's own compilers. I get a Rust error "error: extern blocks must be unsafe" in compiling 'liballoc_error_handler_impl_ffi.rlib'. which I have been unable to fix...

https://blog.slackware.nl/building-chromium-for-slackware-contd/

]]>https://bbs.spacc.eu.org/new/topic/dfdc4567-1e11-47bf-8ac1-a3630b6f9acb/building-chromium-for-slackware-contd.https://bbs.spacc.eu.org/new/topic/dfdc4567-1e11-47bf-8ac1-a3630b6f9acb/building-chromium-for-slackware-contd.Invalid Date<![CDATA[Building Chromium for Slackware]]>Building Chromium for Slackware

I thought it would be helpful, and in any case insightful, to describe how I build the Chromium (also -ungoogled) packages for Slackware. It is not a trivial task but a necessary one I believe. Slackware users should have a choice of browsers - some prefer Mozilla Firefox, others Google Chrome, and then there's LibreWolf and Chromium that are built on the same code base as respectively Firefox and Chrome.

https://blog.slackware.nl/building-chromium-for-slackware/

]]>https://bbs.spacc.eu.org/new/topic/37cb5d40-57ce-4177-a25d-8ee6245bfb5f/building-chromium-for-slackwarehttps://bbs.spacc.eu.org/new/topic/37cb5d40-57ce-4177-a25d-8ee6245bfb5f/building-chromium-for-slackwareInvalid Date<![CDATA[My own little corner of the #fediverse is officially live!]]>#fediverse is officially live! I just migrated my old user @9tom@mastodon.social to my own instance @thoe@snac.9space.no and it went surprisingly smooth. Now I just have to keep the old server humming!
]]>https://bbs.spacc.eu.org/new/topic/6e196844-988b-4ced-919d-1d85892dfa00/my-own-little-corner-of-the-fediverse-is-officially-livehttps://bbs.spacc.eu.org/new/topic/6e196844-988b-4ced-919d-1d85892dfa00/my-own-little-corner-of-the-fediverse-is-officially-liveInvalid Date<![CDATA[New URL: blog.slackware.nl]]>New URL: blog.slackware.nl

Hi all.
It was time to migrate my blog to a new server. The URL ‘alien.slackbook.org/blog/’ has changed to ‘blog.slackware.nl’.

For years, my hosting server has been https://harrier.slackbuilds.org/ – ever since I had to move away from the original host, the slackware.com server (Pat does not trust PHP code).

https://blog.slackware.nl/new-url-blog-slackware-nl/

]]>https://bbs.spacc.eu.org/new/topic/5cac5fd1-cc24-471a-a5ed-d13bfe8c78d2/new-url-blog.slackware.nlhttps://bbs.spacc.eu.org/new/topic/5cac5fd1-cc24-471a-a5ed-d13bfe8c78d2/new-url-blog.slackware.nlInvalid Date<![CDATA[RFC: How to build my Wine package]]>RFC: How to build my Wine package

I have a question for you - hence the "Request For Comment" in this post's title. I have been compiling a Slackware package for the Wine emulator for a long time now. The 64bit wine package contains both the 64bit and the 32bit Wine binaries and libraries.  It therefore also requires that you made your 64bit Slackware into a multilib system.

https://alien.slackbook.org/blog/rfc-how-to-build-my-wine-package/

]]>https://bbs.spacc.eu.org/new/topic/74bf2bf8-67d8-4a2b-8705-be56e87dcbbf/rfc-how-to-build-my-wine-packagehttps://bbs.spacc.eu.org/new/topic/74bf2bf8-67d8-4a2b-8705-be56e87dcbbf/rfc-how-to-build-my-wine-packageInvalid Date