FreeBSD unmaintained ports which are currently marked broken
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as broken in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common problem is that recent versions of -CURRENT include gcc4.2, which is much stricter than older versions. The next most common problem is that compiles succeed on the i386 architecture (e.g. the common Intel PC), but fail on one or more of the other architectures due to assumptions about things such as size of various types, byte-alignment issues, and so forth. In occasional cases we see that the same port may have different errors in different build environments. The script that runs on the build cluster uses heuristics to try to 'guess' the error type to help you isolate problems, but it is only a rough guide. One more note: on occasion, there are transient build errors seen on the build farm. Unfortunately, there is not yet any way for this algorithm to tell the difference (humans are much, much better at this kind of thing.) The errors are listed below. In the case where the same problem exists on more than one build environment, the URL points to the latest errorlog for that type. (By 'build environment' here we mean 'combination of 7.x/8.x/9.x/-current with target architecture'.) (Note: the dates are included to help you to gauge whether or not the error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: audio/libnjb broken because: incomplete plist build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=libnjb portname: audio/teamspeak_client broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=teamspeak_client portname: chinese/big5con broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=big5con portname: chinese/bitchx broken because: does not patch build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.7.20121001063541/zh-BitchX-1.2_5.log (_Oct__2_08:24:08_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=bitchx portname: chinese/hztty broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=hztty portname: databases/adstudio broken because: incomplete plist build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=adstudio portname: databases/grass broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=grass portname: databases/msql broken because: Broken on FreeBSD 9+ build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=msql portname: databases/xapian-bindings10 broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=xapian-bindings10 portname: deskutils/simpleagenda broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=deskutilsportname=simpleagenda portname: devel/dsss broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=dsss portname: devel/fnccheck broken because: does not link build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.9.20121013092108/fnccheck-3.2.0.log (_Oct_15_19:14:08_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=fnccheck portname: devel/gauche-gaunit broken because: does not package build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=gauche-gaunit portname: devel/gcvs broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=gcvs portname: devel/linux-js broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-js portname: devel/linuxthreads broken because: does not build build errors: none. overview:
FreeBSD ports which are currently marked broken
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as broken in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common problem is that recent versions of -CURRENT include gcc4.2, which is much stricter than older versions. The next most common problem is that compiles succeed on the i386 architecture (e.g. the common Intel PC), but fail on one or more of the other architectures due to assumptions about things such as size of various types, byte-alignment issues, and so forth. In occasional cases we see that the same port may have different errors in different build environments. The script that runs on the build cluster uses heuristics to try to 'guess' the error type to help you isolate problems, but it is only a rough guide. One more note: on occasion, there are transient build errors seen on the build farm. Unfortunately, there is not yet any way for this algorithm to tell the difference (humans are much, much better at this kind of thing.) The errors are listed below. In the case where the same problem exists on more than one build environment, the URL points to the latest errorlog for that type. (By 'build environment' here we mean 'combination of 7.x/8.x/9.x/-current with target architecture'.) (Note: the dates are included to help you to gauge whether or not the error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: accessibility/yasr broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=accessibilityportname=yasr portname: audio/gdam broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=gdam portname: audio/hydrogen broken because: does not install build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=hydrogen portname: audio/libnjb broken because: incomplete plist build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=libnjb portname: audio/sphinx3 broken because: does not compile build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.7.20121001063541/sphinx3-0.7.log (_Sep_25_17:40:18_UTC_2012) http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.8.20120903060906/sphinx3-0.7.log (_Sep_10_18:56:45_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=sphinx3 portname: audio/teamspeak_client broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=teamspeak_client portname: benchmarks/polygraph31 broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=benchmarksportname=polygraph31 portname: cad/brlcad broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=cadportname=brlcad portname: cad/meshlab broken because: does not build build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.10.20120628171716/meshlab-1.2.3_2.log (_Jul_16_09:33:26_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=cadportname=meshlab portname: cad/salome-gui broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=cadportname=salome-gui portname: chinese/big5con broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=big5con portname: chinese/bitchx broken because: does not patch build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.7.20121001063541/zh-BitchX-1.2_5.log (_Oct__2_08:24:08_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=bitchx portname: chinese/cxterm broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=cxterm portname: chinese/hztty broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=hztty portname: comms/hso-kmod broken because: does not build with USB2, please try comms/uhso-kmod
FreeBSD unmaintained ports which are currently scheduled for deletion
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: archivers/bsdar description:BSD-licensed replacement of the ar utility maintainer: po...@freebsd.org status: IGNORE deprecated because: part of the base system expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=bsdar portname: audio/gogo description:Very fast MP3 encoder using recent x86 processors' features maintainer: po...@freebsd.org deprecated because: No more public distfiles expiration date:2012-10-20 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=gogo portname: audio/linux-alsa-lib description:The Advanced Linux Sound Architecture libraries maintainer: po...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-alsa-lib portname: audio/linux-arts description:Audio system for the KDE integrated X11 desktop (Linux version) maintainer: po...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-arts portname: audio/linux-freealut description:A free implementation of OpenAL's ALUT standard (Linux version) maintainer: po...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-freealut portname: audio/linux-libmad description:Libmad library (part of MAD project) maintainer: po...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-libmad portname: audio/linux-libogg description:Ogg bitstream library (Linux version) maintainer: po...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-libogg portname: audio/linux-libvorbis description:Audio compression codec library (Linux version) maintainer: po...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-libvorbis portname: audio/linux-openal description:A 3D positional spatialized sound library (Linux version) maintainer: po...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-openal portname: biology/dna-qc description:A quality control algorithm for DNA sequencing projects maintainer: po...@freebsd.org deprecated because: No more public distfiles expiration date:2012-10-20 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=biologyportname=dna-qc portname: cad/admesh description:Program for processing STL triangulated solid meshes maintainer: po...@freebsd.org deprecated because: No more public distfiles expiration date:2012-10-20 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=cadportname=admesh portname: chinese/dfsongsd description:Chinese (HKSCS-2001 + CJK A) TrueType fonts maintainer: po...@freebsd.org status: IGNORE deprecated because: No more public distfiles expiration date:2012-10-20 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=dfsongsd portname: chinese/mingunittf description:Chinese Big5HKSCS TrueType fonts maintainer:
FreeBSD ports which are currently marked forbidden
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as forbidden in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-tiff portname: lang/eperl forbidden because: Vulnerable since 2001-06-21, http://portaudit.freebsd.org/73efb1b7-07ec-11e2-a391-000c29033c32.html build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.7.20101015091133/eperl-2.2.14_3.log.bz2 (_Jul_31_06:17:35_UTC_2010) overview: http://portsmon.FreeBSD.org/portoverview.py?category=langportname=eperl portname: security/sudosh3 forbidden because: Secunia Advisory SA38292, ISS X-Force sudosh-replay-bo (55903), replay() function buffer overflow. build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=securityportname=sudosh3 portname: shells/rssh forbidden because: http://www.vuxml.org/freebsd/65b25acc-e63b-11e1-b81c-001b77d09812.html (vulnerability) build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=shellsportname=rssh portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkitsportname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [HEADSUP] current switched by default to pkgng
On 19.10.2012 23:19, Matthew Seaman wrote: skipped . https://github.com/pkgng/pkgng/commit/8e4cc67cffe8f0afd5c0e25651bd367e12196bbd BIG thanks! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Snag in upgrading p5-XML-SAX and p5-XML-SAX-Base
No -- you only ever need to run pkg2ng once. /usr/bin/pkg will invoke /usr/local/bin/pkg automatically if /usr/local/bin/pkg is installed -- /usr/bin/pkg is a shim that exists to facilitate the installation of the actual /usr/local/bin/pkg binary. That's all normal. Now, the real problem: not seeing the contents of the local package database. Can you check a few things: 1) That PKG_DBDIR isn't defined in your environment or in /usr/local/etc/pkg.conf (or if it is, it is set to an appropriate directory.) 2) That /var/db/pkg/local.sqlite exists and has these permissions and ownership: % ls -l /var/db/pkg/local.sqlite -rw-r--r-- 1 root wheel 4041728 Oct 14 17:52 /var/db/pkg/local.sqlite (The size will be different depending on what packages are installed) 3) Try opening the local.sqlite database and investigating the contents of one or more of the tables. Like so: # pkg shell SQLite version 3.7.14.1 2012-10-04 19:37:12 Enter .help for instructions Enter SQL statements terminated with a ; sqlite select count(*) from packages ; 47 sqlite .quit If that returns zero then something has wiped your package DB. You may be able to recover from a backup copy of local.sqlite that the daily periodic jobs creates in /var/backups/pkgng.db -- just copy that back to /var/db/pkg/local.sqlite and try again. 4) If there is content in local.sqlite, then try using 'pkg info' to query the contents. This should print out just about everything pkgng knows about what is installed on your system: % pkg info -fa Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey Actually, I find pkg in sbin directory as opposed to bin: /usr/sbin/pkg and /usr/local/sbin/pkg . I followed your steps 1 to 4, found 638 packages, found the correct permissions, and pkg info seemed to work correctly. Now I wonder if the problem is fixed. Tom ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: freebsd-ports Digest, Vol 491, Issue 8
On Sun, 21 Oct 2012 08:30:05 + freebsd-ports-requ...@freebsd.org wrote: FreeBSD unmaintained ports which are currently scheduled for deletion portname: games/fretsonfire broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=gamesportname=fretsonfire Hello This Port Frets on Fire works here good, please look and apply patch ports/171408: [PATCH] games/fretsonfire: Makefile changed, now find numpy, OptionsNG http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/171408 Regards, nemysis ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Snag in upgrading p5-XML-SAX and p5-XML-SAX-Base
On 21/10/2012 10:57, Thomas Mueller wrote: Actually, I find pkg in sbin directory as opposed to bin: /usr/sbin/pkg and /usr/local/sbin/pkg . You're quire right. pkg lives in .../sbin. Sorry about that. I followed your steps 1 to 4, found 638 packages, found the correct permissions, and pkg info seemed to work correctly. Now I wonder if the problem is fixed. Well, the tests show that the problem is not a completely hosed package database, which is good. So, the problem is confined to the p5-XML-SAX and p5-XML-SAX-Base ports. You're trying to follow the instructions in the 20120512 entry in UPDATING? And the initial 'pkg delete' of p5-XML-SAX is showing the errors? You can check eg. what XML related packages are installed by: pkg info -x XML If it doesn't show p5-XML-SAX then I'd say you're good to go, and can just reinstall p5-XML-SAX and p5-XML-SAX-Base and everything should be fine. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
FreeBSD Port: sysutils/wait_on
wait_on does not scan for changes in sub-directories. Could a new switch be added have it scan for changes in sub-directories? Currently I am unable to make wait_on accept a variable as an input which contains quotes (single or double) without an error. Thank You ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
python binding of spatialite (GIS)
Hello, Can someone help me to create the ports of pyspatialite pypi.python.org/pypi/pyspatialite/3.0.1 ? I managed to create the makefile to download the source but my knowledge of python does not allow me to make the port correctly. This binding is need by some extensions in Qgis and maybe other. Thanks. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [HEADS UP] pav@ steps down from portmgr@
On 10/19/12 11:25 AM, Thomas Abthorpe wrote: Pav Lucistnik, aka pav@, recently stepped down from his roll on the FreeBSD Ports Management team. Pav started on portmgr back in November 2006, he was the one responsible for many of the -exp runs over the years. His most dubious claim to fame was talking over the responsibility of krismails. We all looked forwward to our pavmails, right? On behalf of the Ports Management team, we want to thank Pav for his years of service, he will be missed. Indeed. Thanks, pav for all your hard work. You had a great impact on a lot of large ports things. What's next for you? Joe -- PGP Key : http://www.marcuscom.com/pgp.asc ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Snag in upgrading p5-XML-SAX and p5-XML-SAX-Base
On 21/10/2012 10:57, Thomas Mueller wrote: Actually, I find pkg in sbin directory as opposed to bin: /usr/sbin/pkg and /usr/local/sbin/pkg . You're quire right. pkg lives in .../sbin. Sorry about that. I followed your steps 1 to 4, found 638 packages, found the correct permissions, and pkg info seemed to work correctly. Now I wonder if the problem is fixed. Well, the tests show that the problem is not a completely hosed package database, which is good. So, the problem is confined to the p5-XML-SAX and p5-XML-SAX-Base ports. You're trying to follow the instructions in the 20120512 entry in UPDATING? And the initial 'pkg delete' of p5-XML-SAX is showing the errors? You can check eg. what XML related packages are installed by: pkg info -x XML If it doesn't show p5-XML-SAX then I'd say you're good to go, and can just reinstall p5-XML-SAX and p5-XML-SAX-Base and everything should be fine. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. I followed the instructions in the 20120512 entry in UPDATING, and was successful. Now the problem is x11-toolkits/open-motif and lang/tcl85 allegedly trying to install files to the same location, meaning a conflict, and that has me stopped, Error 70. Is there any command under pkg that would help? Now I wonder where error codes are documented. I see Error 1 and 2 most frequently, but where do I find what Error 1, 2, 3, 4, 5 etc mean? Tom ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Building PAPI port on FreeBSD 10
--- configure.orig 2012-10-21 21:46:34.996150862 -0700
+++ configure 2012-10-21 21:40:23.478149927 -0700
@@ -5800,7 +5800,7 @@
MAKEVER=freebsd
LDFLAGS=-lpmc
# HWPMC driver is available for FreeBSD = 6
-FREEBSD_VERSION=`uname -r | cut -c 1`
+FREEBSD_VERSION=`uname -r | cut -d'.' -f1`
if test ${FREEBSD_VERSION} -lt 6 ; then
as_fn_error PAPI requires FreeBSD 6 or greater $LINENO 5
fi
Without this change, make install fails as it cannot grep correct major
os revision number.
Let me know if this change looks fine.
Thanks,
Hiren
P.S: I am not subscribed to this list so please keep me in the loop.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Snag in upgrading p5-XML-SAX and p5-XML-SAX-Base
On 21/10/2012 22:44, Thomas Mueller wrote: Now the problem is x11-toolkits/open-motif and lang/tcl85 allegedly trying to install files to the same location, meaning a conflict, and that has me stopped, Error 70. Is there any command under pkg that would help? That's a problem with the underlying ports, and should be reported as a bug to their maintainers. pkgng is stricter about such things than pkg_tools, hence a number of cases coming to light as pkgng usage starts to ramp up. Now I wonder where error codes are documented. I see Error 1 and 2 most frequently, but where do I find what Error 1, 2, 3, 4, 5 etc mean? pkgng uses sysexits.h for almost all of its error codes. 70 is EX_SOFTWARE. See sysexits(3). Unfortunately, the error descriptions in that manual page are so generic it doesn't really tell you anything much about what actually went wrong. There should be some sort of error message though. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. I can find the port maintainers in the respective Makefiles. I sent a message on that subject two days ago, no response so far. Maybe the maintainers are off for the weekend; otherwise I can send another message, with CC to the port maintainers, Tuesday morning, giving time for a Monday response. I looked in man sysexits and in the referenced file, /usr/include/sysexits.h : showed error codes 64 to 78. Where do I find documentation for other error codes? Tom ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Snag in upgrading p5-XML-SAX and p5-XML-SAX-Base
On 22/10/2012 06:47, Thomas Mueller wrote: I looked in man sysexits and in the referenced file, /usr/include/sysexits.h : showed error codes 64 to 78. Where do I find documentation for other error codes? If it's not described in the program's man page, then I'm afraid you'll probably have to resort to reading the source code. Usually though the only real significance is between the program returning 0 everything is OK and non-zero something wrong, and there will be some other mechanism to tell you about what went wrong. Some programs have been known to use a count of the number of errors encountered as the exit code. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
