1. Andrew's Corner :

Compiling the git slrn under Windows 10

I have long been a huge fan of the Usenet client slrn and I have used it under Linux for some years. However even in my early days I was somewhat intrigued by the claim seen on the slrn website that my favourite newsreader would also run under Windows. After a little experimentation with the Windows binaries generously provided by Thomas Wiegner I decided that I would emulate my customary practice under Linux and compile the development version of slrn under the 32 bit versions of first Windows 7, then Windows 8 and now Windows 10, albeit running Windows under Virtualbox. By this I mean compile slrn under a Windows environment rather than cross-compile for Windows from within a Linux environment. I eventually succeeded in an endeavour that many regarded as a little crazy and subsequently decided to write this page so that others might perhaps follow my example.

Contents of this page...

Although best read from top to bottom I have included some navigation for those who would prefer to browse rather than read in detail:

Please feel free to use the email link at the base of this page to pass on any comments, I am always keen to improve on the information presented in this page and also to hear from fellow slrn enthusiasts!

Some required tools...

Windows 10 is a decent operating system but some additions are needed: a decent compiler and some git software. First up a quality, free compiler:


The best choice is MinGW | Minimalist GNU for Windows. Install MinGW's C compiler only (mingw32-base), using the nice automated installer, to C:/MinGW, see some further notes here about MinGW installation in general. Feel free to install more of the MinGW packages but this is all that is required to build S-Lang and slrn itself. You will need to then add MinGW to the Windows $PATH, this has been a little hidden in Windows 10 and can be found by the following route:

Windows Key + X --> System --> Advanced System Settings --> Environment Variables

You should then permanently and cautiously add minGW to the $PATH by following these directions. On my system I add in the following at the end of the System $PATH statement, against the MinGW advice to use the $USER section:


You can also create a new $NNTPSERVER System variable and place your NNTP server details in here, this will make things a little less complex later. Please note that I am using C:/slrn to place user configuration files for slrn, some might like to place these in the appropriate Windows 'User' directory. I shall leave that to you to make the necessary adjustments if you wish to do this. It would be nice if the MinGW installer would take care of some of this!!

Git for Windows...

A git client is also required and in the world of Windows 10 you could do as I have done and download Git For Windows. I personally found the gui more than a little confusing but a commandline is also available with all the familiar commands. To use Git for Windows in this manner simply right click on the desired location, select 'Git Bash' and there will be a familiar command prompt to type all of the usual git commands. If anybody is using a better git client I would love to hear from you and will put the details in here.

Compiling slrn...

Compiling slrn is pretty straightforward with the latest git but before actually coming to grips with slrn we will need to get the S-Lang dependency downloaded, compiled and installed.


We will need to download the required S-Lang library, because of a small compiling issue I have used a development version pre2.3.1-30 which I will swap for the release version 2.3.1 when it is available. I use WinRAR to actually decompress the downloaded archive. Compiling instructions for S-Lang under Windows are quite clear and can be found in the file INSTALL.pc, have a look at the details then open a command window in the opened archive and run the following three commands in sequence:

mingw32-make install

This installs S-Lang to the default C:/MinGW/local and slrn will pick this up when we compile its source code.


slrn benefits from compiling against the external library libiconv and I use the binary, developer and dependency packages from the GnuWin32 project, all of which can simply be decompressed with WinRAR into C:/MinGW/local. This is a slightly older version than is currently available but it works well enough on my system. Some manual tweaking of the slrn code is required to use libiconv and these details are below.


slrn can benefit from compiling against the external library openssl and after some experimentation I am using the binary and developer packages again from the GnuWin32 project. I am not sure if this is the best version to use or if there is an easier way to do this, feel free to suggest any improvements for this teechnique! The openssl archives can simply be decompressed into C:/MinGW/local and then the slrn code will need to be tweaked slightly so that slrn will use these openssl files, details below.


We will use the latest git version of slrn to take advantage of the latest updates so open a command prompt, as detailed above, and type the following:

git clone git://git.jedsoft.org/git/slrn.git

This will give you the latest development version of slrn. Before compiling this we will need to tweak the code a little to use the external libraries libiconv and openssl. Open the file src/win32/makefile.m32in and alter it to reflect the following:

SSL_LIBS =  -lssl -lcrypto -lgdi32
MISCLIBS = $(SSL_LIBS) -lwsock32 -lwinspool -liconv

Then open the file src/slrnconf.h and add the following:

/* Add support for libiconv */
#define HAVE_ICONV 1

Also alter the line in src/slrnconf.h that deals with ssl support by changing the zero value to one:


After this slrn can then be compiled from the root directory with the following three commands in sequence, note that this will now compile and install both slrn and slrnpull:

slsh win32/m32config.sl
mingw32-make install

And thanks to the beautiful build system for this version of slrn that is all that is required, but there is still some more work to do to complete the setup.

Completing the setup...

This page is really aimed at getting the git slrn successfully compiled under Windows 10 rather than giving a general setup guide for slrn,nevertheless there are a few small issues specific to Windows that I thought I would address here if only to remind myself of some of the issues I have sorted out when reloading time comes around!

Sending email...

The ability to send email replies from within slrn is something that should be used rarely but it can be quite handy. My peronal favourite to accomplish this is an Australian application known disarmingly as fake sendmail for windows. Drop this into C:/slrn/sendmail and reference it from slrn.rc as follows:

% Sends mail with 'fake sendmail for windows'.
set sendmail_command "C:/slrn/sendmail/sendmail.exe -t <"

You will need to spend a few minutes editing the file sendmail.ini and then this great little piece of software will not give you any trouble at all. According to the Fake Sendmail website there will no longer be any development of this fine application which is a great pity.

Selecting an editor...

slrn of course does not ship with an editor and I would suggest for a typical Windows 10 user that GVim is a fine choice, I use version 7.3.46 as the newest version had a few syntax changes that I could not work out. It will need a setting something like the following in slrn.rc:

% Set your favourite editor.  Use %s for the file name and %d for the line
% where the cursor should be placed (usually at the beginning of the body).
set editor_command "C:/Vim/vim73/gvim +%d %s"

Note that as usual it is best to install software such as GVim to a location without spaces in the directory names, it just makes life so much easier. Some may be interested in the additions I have made to the default _vimrc file that make the GVim plus slrn experience a little more comfortable:

 " My changes to the default _vimrc that make
 " editing with GVim for slrn a little easier:
set guifont=Consolas:h13 " Looks good on my system, also used for Terminal.
colors darkblue          " Background colour for the Gvim window.
nnoremap Q gq}           " Q command to reformat paragraphs and list.
set nobackup             " No backup files littering the place.
set textwidth=70         " Text width to keep Usenet happy.
set encoding=utf-8       " Required for 'foreign' text.
set fileencoding=utf-8   " Required for 'foreign' text.

I am no GVim master so I would be very happy to hear of any better options that I should be using, but these are working fine for me at the moment.

Setting slrnpull...

To successfully run slrnpull the following settings are required in slrn.rc:

set spool_inn_root   "/MinGW/local/var/spool/news/slrnpull"
set spool_root       "/MinGW/local/var/spool/news/slrnpull/news"
set spool_nov_root   "/MinGW/local/var/spool/news/slrnpull/news"
set read_active      1
set use_slrnpull     1
set post_object      "slrnpull"
set server_object    "spool"

This is the bare minimum to successfully point slrn towards the spool and let me tell you that slrnpull runs very nicely under Windows 10! A final thought is the addition of the following:

Some final slrn.rc settings...

There are a couple of very Windows-specific settings to note and probably a few I have forgotten as well. The following is required to get a decent display of the thread tree on Windows 8's console:

set simulate_graphic_chars 1

The following is required to launch Firefox from URLs within slrn:

set non_Xbrowser "start \"\" \"C:/Program\ Files/Mozilla\ Firefox/firefox.exe\" \"%s\""

This one is not very pretty, although it works well enough, I will keep looking into this one to see if a cleaner method can be used. That should just about do it but I shall add any more Windows-specific requirements as I come across them.

Starting with a batch file...

Thomas Wiegner's Windows binary has a nice batch file, required to start slrn under Windows 10, and I have borrowed liberally from it:

rem This is a batch file for slrn under windows
set SLRNHOME=C:\slrn
set LANG=en_AU.UTF-8
set TMP=c:\WINDOWS\Temp

I would suggest that you run slrnpull directly from the commandline rather than from this batch file, although please feel free to disregard this advice and let me know your preferred way of running both slrnpull and slrn itself. On my own system slrnpull is used directly from the commandline and this suits my own usage just fine.

The final result...

I run the 32 bit Windows 10 as a guest with a Slackware 14.1 host on VirtualBox 4.3.8 and even with this slightly limiting setup the performance of slrn and slrnpull is pretty impressive. The final results from this effort read:

Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\andrew>slrn --version
slrn pre1.0.3-7
        * Note: This version is a developer preview.
S-Lang Library Version: pre2.3.1-31
Compiled on: Nov 13 2015 19:18:18
Operating System: Win32

 Backends: +nntp +slrnpull +spool
 External programs / libs: -canlock -inews +ssl -uudeview +iconv
 Features: +decoding +emphasized_text +end_of_thread +fake_refs +gen_msgid
    -grouplens +msgid_cache +piping +rnlock +spoilers -strict_from
 Using 64 bit integers for article numbers.

 Default server object:     nntp
 Default posting mechanism: nntp


I suspect that perhaps not all that many Windows users will be reading down this far on an admittedly fairly complex page, but in part this page functions as my own backup and a method to organise my own thoughts, in this hopefully it has been a success. I will update the page with any corrections that come in and also endeavour to keep it updated when slrn development moves further onward. It should be fun!

And in conclusion...

I have enjoyed writing this page as it has taken me right out of my comfort zone and forced me to learn a few small and valuable lessons. Please contact me with any errors of fact that you have found, any errors of opinion will probably remain uncorrected. If you are feeling generous perhaps you could also assist me keep this page alive by assisting with the hosting bills for this site, if not please feel free to utilise this page in any way you see fit and remember: "Have Fun!".