Warning: file_exists(): open_basedir restriction in effect. File(/srv/http/vhosts/aur.archlinux.org/public/web/locale//en/LC_MESSAGES/aurweb.mo) is not within the allowed path(s): (/srv/http/vhosts/aur-dev.archlinux.org/:/etc/aurweb/) in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/streams.php on line 90
AUR (en) - lprng

Notice: Undefined variable: name in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/pkgfuncs.inc.php on line 248

Package Details: lprng 3.8.C-9

Git Clone URL: https://aur-dev.archlinux.org/lprng.git (read-only)
Package Base: lprng
Description: An Enhanced Printer Spooler
Upstream URL: http://www.lprng.com
Licenses: custom:Artistic
Conflicts: cups
Submitter: axs
Maintainer: djraymondnm
Last Packager: djraymondnm
Votes: 6
Popularity: 0.000049
First Submitted: 2008-12-01 12:01
Last Updated: 2015-06-22 21:01

Dependencies (7)

Required by (4)

Sources (11)

Latest Comments

« First ‹ Previous 1 2

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:

-Wno-error=unused-result

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 ld.so errors go away with:

cd /usr/lib
sudo ln -s libfakeroot/libfakeroot.so libfakeroot.so

As pointed out by:

https://bugs.archlinux.org/task/6208

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: ld.so: object 'libfakeroot.so' 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 lprng.com, 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 ftp://ftp.lprng.com used as the source for lprng, when the page itself, http://www.lprng.com, points to http://sourceforge.net/projects/lprng?

Problem is that the ftp://ftp.lprng.com 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 ftp://ftp.lprng.com one... Under debian unstable they're using 8.3.A (http://downloads.sourceforge.net/project/lprng/lprng/LPRng-3.8.A/LPRng-3.8.A.tar.gz), 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, http://www.lprng.com/DISTRIB/LPRng/LPRng-3.8.33.tgz, 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...