Package Details: lprng 3.8.C-10

Git Clone URL: (read-only)
Package Base: lprng
Description: An Enhanced Printer Spooler
Upstream URL:
Licenses: custom:Artistic
Conflicts: cups
Submitter: axs
Maintainer: djraymondnm
Last Packager: djraymondnm
Votes: 6
Popularity: 0.000000
First Submitted: 2008-12-01 12:01
Last Updated: 2017-10-28 18:49

Latest Comments

djraymondnm commented on 2017-10-28 18:56

I have turned off openssl in version 10 as configuration now fails (why???)
and ssl doesn't seem to be needed for common usage. (I tried it on our
network, printing remotely from a cups client.) Works out of the box now.

02m commented on 2017-10-26 16:14

Got the same error as killajoe while installing.

killajoe commented on 2017-10-04 08:28

checking if ssl authentication is disabled... enabled
checking openssl/ssl.h usability... yes
checking openssl/ssl.h presence... yes
checking for openssl/ssl.h... yes
checking for RC4_set_key in -lcrypto... yes
checking for SSL_load_error_strings in -lssl... no
configure: error: Unable to use OpenSSL


someone have builded this one actually?

asveikau commented on 2017-06-05 18:31


Wanted to note a few things.

1. PKGBUILD says it supports i686 and x86_64 but for a few years now I am running it on a raspberry pi without issue (armv6h).

2. Recently this package seems to have linker issues with libssl for me (openssl 1.1.0.f-1). I manually removed --enable-ssl as a workaround since I'm not using it on my LAN, didn't care to dig any further than that.

djraymondnm commented on 2016-04-05 23:54

This package was flagged out of date on 1 Jan 2016 because version 3.8.35 has become available on the original lprng website. The version used here is based on 3.8.32 and appears to have been forked by Debian people. I have tried to compile 3.8.35 from the original website with no success. Further examination suggests that Debian has put in a heroic amount of effort to make lprng compile and run. Furthermore, according to the change log in 3.8.35, no changes significant to Linux were made between 32 and 35. I therefore consider the current version 3.8.C up to date and I am removing the out of date flag.

djraymondnm commented on 2015-02-20 20:28

Regarding the comment by Grymer about the installation of lprng failing because /usr/sbin exists, I have solved this problem by forcing the installation of all binary files for lprng directly into /usr/bin. So, lprng installs cleanly now. Also, a filter that uses foomatic-rip has been added, so that the whole .ppd filter system can be used. This requires the installation of foomatic-filters-lprng from the AUR. Finally, a Wiki page now exists for lprng.

djraymondnm commented on 2015-01-18 23:09

Well, I'm stumped! I uninstalled lprng on my laptop and reinstalled it and I had no problem. Quite a few lprng programs get installed in /usr/sbin, but this should work with the link unless /usr/bin has some executables the clash with lprng executables. (This among other reasons is why cups conflicts with lprng.) I also have /usr/sbin as a symbolic link to /usr/bin (as it is supposed to be).

Glad you found a way to install.

grymer commented on 2015-01-17 23:46

It's definitely a symbolic link, and I'm using a fresh system installed from the '2015.01.01' ISO. Not sure why pacman complained.

djraymondnm commented on 2015-01-15 16:52

Hmmm... I haven't seen this. Are you sure that your '/usr/sbin' really is a link to '/usr/bin' at this point? If there is stuff in /usr/sbin when the filesystem upgrade is done, this upgrade might fail. If that is true, then you can just move stuff in sbin to bin and manually make /usr/sbin a symbolic link.

grymer commented on 2015-01-15 11:59

Compiled great, but Pacman install failed first time with message 'lprng: /usr/sbin exists in filesystem'. It installed okay by using the '--force' option. I guess this is because the filesystem package provides a symlink '/usr/sbin -> /usr/bin' ('/usr/sbin' now being deprecated).

acampbell commented on 2014-08-23 14:52

Tnanks: this now compiles without problems.

djraymondnm commented on 2014-04-12 23:53

Corrected a problem with gsfilter in version 5.

djraymondnm commented on 2014-02-21 16:20

I just uploaded a much cleaner version of the lprng package (-3), including a link to the reference manual on my website, as the original documentation website has just disappeared.

djraymondnm commented on 2014-02-04 02:24

I just uploaded a new version of lprng which is based on
code at sourceforge. It works for me on an up to date
Arch system.

acampbell commented on 2013-06-02 17:21

I'm new to Arch and this is my first attempt at compiling on AUR. I've been using lprng for years on Debian and was keen to have it in Arch.

Unfortunately I didn't succeed. I made the changes mentioned below by jevv but although the numerous errors went away during the compile the eventual message was "failed to build".

I really don't like CUPS but it looks as if there isn't any alternative.

helasz commented on 2013-04-09 11:41

Revisiting the comments of jevv from 2010-05-04 and having found the lprng package updated (2012-12-28) to "3.8.C" on sourceforge I did prepare (based on the actual above files) the PKGBUILD file for that version on an updated 32bit Arch Linux system.
I am not sure how to submit it in a comment .
Furhtermore I needed (due to sourceforge's naming schema) to "hardcode" the download location, I would appreciate if anybody could come up with a better solution.

Anonymous comment on 2011-10-10 02:27

Wow, now lprng build is missing flags (though not sure which). To make the thing compile I had to edit makepkg.conf, and add in the 3 compilation flags (CFLAGS, CXXFLAGS and LDFLAGS) the following:


With this the errors due to warnings indicating result values are unused, get ignored, and thus, the error is prevented. Finally lprng compiles...

Anonymous comment on 2011-10-10 01:38

New building failure on x86_64:

/bin/sh ../libtool --mode=compile gcc -I.. -I. -I./include -I./common -D_FILE_OFFSET_BITS=64 -I/usr/include -g -W -Wall -Werror -Wno-unused -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -g -W -Wall -Werror -Wno-unused -DHAVE_CONFIG_H -c ./common/getqueue.c
libtool: compile: gcc -I.. -I. -I./include -I./common -D_FILE_OFFSET_BITS=64 -I/usr/include -g -W -Wall -Werror -Wno-unused -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -g -W -Wall -Werror -Wno-unused -DHAVE_CONFIG_H -c ./common/getqueue.c -o getqueue.o
./common/getqueue.c: In function ‘Trim_status_file’:
./common/getqueue.c:1700:13: error: ignoring return value of ‘ftruncate’, declared with attribute warn_unused_result [-Werror=unused-result]
cc1: all warnings being treated as errors

make[1]: *** [getqueue.lo] Error 1
make[1]: Leaving directory `/tmp/yaourt-tmp-vasqueja/aur-lprng/src/LPRng-3.8.35/src'
make: *** [src] Error 2

Any idea?

Anonymous comment on 2011-10-10 01:36

The errors go away with:

cd /usr/lib
sudo ln -s libfakeroot/

As pointed out by:

However there's another building problem to solve. I'll talk to it in next comment...

Anonymous comment on 2011-09-05 11:45

I'm trying to build the LPRng package using makepkg. When makepkg runs, it outputs dozens and dozens of lines which state:

ERROR: object '' from LD_PRELOAD cannot be preloaded: ignored.

Eventually, makepkg finishes with " ==> ERROR: A failure occurred in build(). Aborting..."

My Arch system is fully up-to-date as of last week (2nd September 2011). What do I need to do to build this package successfully?

axs commented on 2011-01-04 23:26

Ugh, never have any problem with, ftp or http, and they list FTP as the main source. The site doesn't have any SF links on download page, and looks like they didn't update their SF page in a while. Changed ftp link to http though, agreed, it should be easier for most people to use http.

Arch being rolling release system and all, I guess there is a reason to keep the "current" version in this package, and maybe create another one for (apparently stable) 3.8.A.

And hm, it really doesn't require any patches.

The package itself is larger because of the docs — and again, looks like they have no source-only package on the main site.

Anonymous comment on 2010-05-04 03:19

This was an old comment I had... Why is the used as the source for lprng, when the page itself,, points to

Problem is that the sources are not able to be downloaded most of the time. This hurts the package, which by the way keeps being my preferred spooler...

Only caveat with the sourceforge repositories, is that the version conventin doesn't follow the one... Under debian unstable they're using 8.3.A (, and they're around the 3rd version of this source...

If we use the sourceforge source, as debian is doing, the bonus is that there are no patches needed, and I haven't found the source I pointed out, unavailable.

Another approach is to use the http source,, but it doens't work all the time, but at least it improves over the ftp source, which is pretty much dow most of the time...

One noticeable difference is that the sourceforge source is 958K long, while the http lprng one is 12M, not sure why the increase in size, niether why 3.8.33 was not uploaded into sourceforge, if sourceforge is actually pointed out by the original web page...