FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ databases/unixODBC | 2.3.1 | 2.3.2 +-+ devel/czmq | 1.4.1 | 2.0.2 +-+ devel/ocaml-lacaml | 7.0.7 | 7.0.11 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt If wish to stop receiving portscout reminders, please contact portsc...@freebsd.org 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: Undelivered Mail: ho...@freebsd.org
On Tue, 8 Oct 2013 21:01:06 -0400 Sahil Tandon articulated: Did you, by chance, report this to postmas...@freebsd.org? We'll look into it. No I didn't because: A) I was not sure if it was a local problem; ie, only me B) Who to actually report it to Since it is not a local problem, I am glad that you are looking into it. -- Carmel ✌ carmel...@hotmail.com ___ 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
10.0-hosted tinderbox: 8.4 builds broken?
Hi there, I've started to observe the following error when trying to tinderbuild (freshly cvs up'ed from marcuscom.com) a port for -b 8.4: ... add_pkg pkg-1.1.4_7.tbz adding dependencies pkg_add pkg-1.1.4_7.tbz The package management tool is not yet installed on your system. Do you want to fetch and install it now? [y/N]: tar: Error opening archive: Failed to open 'pkg-1.1.4_7.tbz' /buildscript: ./pkg-static: not found error in dependency pkg-1.1.4_7.tbz, exiting In fact, pkg-1.1.4_7.txz *is* generated for 8.4, but extensions are different (.txz vs. .tbz). Why does it happen? I was under impression that 8.x will never switch to pkgng. Am I doing something wrong, or need to configure my tindy somehow? ./danfe ___ 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
[math/scilab] configuration failure by error in version check of hdf5
Hi, Re: math/scilab (Revision 327746) I have failed to configure this port in compilation stage these days. It is caused by an error in version check code for hdf5. Because the code writen in Java uses String.compareTo() for numeric comparision, 1.8.10 is not recognized as a newer one than 1.8.4. Could somebody correct this easy bug? Cheers -- - Mamoru Iwaki Japan ___ 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
poudriere: ELF binary type 0 not known.
I'm seeing this on the console: load: 2.53 cmd: cc1 48388 [running] 2.92r 2.66u 0.04s 24% 35192k sleep: about 1 second(s) left out of the original 2 [ia64-default] [parallel_build:] [00/30] Built: 0 Failed: 0 Ignored: 0 Skipped: 0 [01]: devel/qt4-corelibbuild (00:03:31) [02]: lang/gcc build (00:03:31) Logs: /pdr/data/logs/bulk/ia64-default/2013-10-09_14h59m33s WWW: http://eis.bris.ac.uk/~mexas/poudriere/bulk/ia64-default/2013-10-09_14h59m33s [01] Finished build of devel/qt4-corelib: Success [01] Starting build of x11-toolkits/qt4-gui ELF binary type 0 not known. ELF binary type 0 not known. ELF binary type 0 not known. ELF binary type 0 not known. ELF binary type 0 not known. Are the ELF error/warning messages being emitted by the build failures? Or are these issued by the poudriere itself? # uname -a FreeBSD mech-as28.men.bris.ac.uk 10.0-CURRENT FreeBSD 10.0-CURRENT #6 r255488: Wed Oct 9 12:33:28 BST 2013 r...@mech-as28.men.bris.ac.uk:/usr/obj/usr/src/sys/ZEEV ia64 # pkg info -xo poudriere poudriere-devel-3.0.99.20131005 ports-mgmt/poudriere-devel # poudriere jails -l JAILNAME VERSION ARCHMETHOD PATH ia64 10.0-ALPHA4 r255986 ia64svn+https /pdr/jails/ia64 # Thanks Anton ___ 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: poudriere: ELF binary type 0 not known.
On Wed, Oct 09, 2013 at 04:06:42PM +0100, Anton Shterenlikht wrote: I'm seeing this on the console: load: 2.53 cmd: cc1 48388 [running] 2.92r 2.66u 0.04s 24% 35192k sleep: about 1 second(s) left out of the original 2 [ia64-default] [parallel_build:] [00/30] Built: 0 Failed: 0 Ignored: 0 Skipped: 0 [01]: devel/qt4-corelibbuild (00:03:31) [02]: lang/gcc build (00:03:31) Logs: /pdr/data/logs/bulk/ia64-default/2013-10-09_14h59m33s WWW: http://eis.bris.ac.uk/~mexas/poudriere/bulk/ia64-default/2013-10-09_14h59m33s [01] Finished build of devel/qt4-corelib: Success [01] Starting build of x11-toolkits/qt4-gui ELF binary type 0 not known. ELF binary type 0 not known. ELF binary type 0 not known. ELF binary type 0 not known. ELF binary type 0 not known. Are the ELF error/warning messages being emitted by the build failures? Or are these issued by the poudriere itself? It is not issued by poudriere itself but by some failure, I have already seen a couple of them but I have never been able to figure out where they are from, neither what impact it has, as it is not related to a failed port :(. regards, Bapt pgp4q4g6U9mKh.pgp Description: PGP signature
Re: poudriere: ELF binary type 0 not known.
From baptiste.darous...@gmail.com Wed Oct 9 16:42:02 2013 On Wed, Oct 09, 2013 at 04:06:42PM +0100, Anton Shterenlikht wrote: I'm seeing this on the console: =20 load: 2.53 cmd: cc1 48388 [running] 2.92r 2.66u 0.04s 24% 35192k sleep: about 1 second(s) left out of the original 2 [ia64-default] [parallel_build:] [00/30] Built: 0 Failed: 0 Ignored: 0= Skipped: 0 =20 [01]: devel/qt4-corelibbuild (00:03:31) [02]: lang/gcc build (00:03:31) =3D=3D=3D=3D Logs: /pdr/data/logs/bulk/ia64-default/2013-10-09_14h59m33s =3D=3D=3D=3D WWW: http://eis.bris.ac.uk/~mexas/poudriere/bulk/ia64-defa= ult/2013-10-09_14h59m33s =3D=3D=3D=3D [01] Finished build of devel/qt4-corelib: Success =3D=3D=3D=3D [01] Starting build of x11-toolkits/qt4-gui ELF binary type 0 not known. ELF binary type 0 not known. ELF binary type 0 not known. ELF binary type 0 not known. ELF binary type 0 not known. =20 Are the ELF error/warning messages being emitted by the build failures? Or are these issued by the poudriere itself? It is not issued by poudriere itself but by some failure, I have already se= en a couple of them but I have never been able to figure out where they are from, neither what impact it has, as it is not related to a failed port :(. ok, thanks. I was just thinking that all port build output (stdout and stderr) are redirected to files, so I shouldn't see anything at all related to port build output on console. Therefore this must be something else... Thanks Anton ___ 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: poudriere: ELF binary type 0 not known.
On Wed, Oct 09, 2013 at 04:48:19PM +0100, Anton Shterenlikht wrote: From baptiste.darous...@gmail.com Wed Oct 9 16:42:02 2013 On Wed, Oct 09, 2013 at 04:06:42PM +0100, Anton Shterenlikht wrote: I'm seeing this on the console: =20 load: 2.53 cmd: cc1 48388 [running] 2.92r 2.66u 0.04s 24% 35192k sleep: about 1 second(s) left out of the original 2 [ia64-default] [parallel_build:] [00/30] Built: 0 Failed: 0 Ignored: 0= Skipped: 0 =20 [01]: devel/qt4-corelibbuild (00:03:31) [02]: lang/gcc build (00:03:31) =3D=3D=3D=3D Logs: /pdr/data/logs/bulk/ia64-default/2013-10-09_14h59m33s =3D=3D=3D=3D WWW: http://eis.bris.ac.uk/~mexas/poudriere/bulk/ia64-defa= ult/2013-10-09_14h59m33s =3D=3D=3D=3D [01] Finished build of devel/qt4-corelib: Success =3D=3D=3D=3D [01] Starting build of x11-toolkits/qt4-gui ELF binary type 0 not known. ELF binary type 0 not known. ELF binary type 0 not known. ELF binary type 0 not known. ELF binary type 0 not known. =20 Are the ELF error/warning messages being emitted by the build failures? Or are these issued by the poudriere itself? It is not issued by poudriere itself but by some failure, I have already se= en a couple of them but I have never been able to figure out where they are from, neither what impact it has, as it is not related to a failed port :(. ok, thanks. I was just thinking that all port build output (stdout and stderr) are redirected to files, so I shouldn't see anything at all related to port build output on console. Therefore this must be something else... All I know is that this problem should come because something is trying a linux binary which is not properly brandelfed or something like this. regards, Bapt pgpzapneY1b1A.pgp Description: PGP signature
Re: 10.0-hosted tinderbox: 8.4 builds broken?
On Wed, Oct 09, 2013 at 06:09:55PM +0700, Alexey Dokuchaev wrote: Hi there, I've started to observe the following error when trying to tinderbuild (freshly cvs up'ed from marcuscom.com) a port for -b 8.4: ... add_pkg pkg-1.1.4_7.tbz adding dependencies pkg_add pkg-1.1.4_7.tbz The package management tool is not yet installed on your system. Do you want to fetch and install it now? [y/N]: tar: Error opening archive: Failed to open 'pkg-1.1.4_7.tbz' /buildscript: ./pkg-static: not found error in dependency pkg-1.1.4_7.tbz, exiting In fact, pkg-1.1.4_7.txz *is* generated for 8.4, but extensions are different (.txz vs. .tbz). Why does it happen? I was under impression that 8.x will never switch to pkgng. Am I doing something wrong, or need to configure my tindy somehow? 1/ yes 8.x will one day switch to pkgng :) but that is not the case yet. 2/ this is one of the design bugs of tinderbox. The very recent update of tinderbox might have fixed that one. regards, Bapt pgp1q96JjjKMw.pgp Description: PGP signature
FreeBSD Port: lang/sbcl
Hi, After upgrading sbcl to 1.1.12, stumpwm no longer compiles. I'm compiling stumpwm from the git repository, which hasn't changed in quite awhile. If there is anything I can test or any other information I can provide, please let me know. Joseph % gmake /usr/local/bin/sbcl --load ./make-image.lisp This is SBCL 1.1.12, an implementation of ANSI Common Lisp. More information about SBCL is available at http://www.sbcl.org/. SBCL is free software, provided as is, with absolutely no warranty. It is mostly in the public domain; some portions are provided under BSD-style licenses. See the CREDITS and COPYING files in the distribution for more information. WARNING: compiling #STATIC-FILE sb-bsd-sockets NEWS completed without its input file #P/usr/local/lib/sbcl/sb-bsd-sockets/NEWS WARNING: loading #STATIC-FILE sb-bsd-sockets NEWS completed without its input file #P/usr/local/lib/sbcl/sb-bsd-sockets/NEWS WARNING: compiling #STATIC-FILE sb-bsd-sockets TODO completed without its input file #P/usr/local/lib/sbcl/sb-bsd-sockets/TODO WARNING: loading #STATIC-FILE sb-bsd-sockets TODO completed without its input file #P/usr/local/lib/sbcl/sb-bsd-sockets/TODO debugger invoked on a ASDF/FIND-SYSTEM:MISSING-COMPONENT: Component STUMPWM not found Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [RETRY ] Retry EVAL of current toplevel form. 1: [CONTINUE] Ignore error and continue loading file /usr/home/jrm/scm/stumpwm.git/./make-image.lisp. 2: [ABORT ] Abort loading file /usr/home/jrm/scm/stumpwm.git/./make-image.lisp. 3:Ignore runtime option --load ./make-image.lisp. 4:Skip rest of --eval and --load options. 5:Skip to toplevel READ/EVAL/PRINT loop. 6: [EXIT] Exit SBCL (calling #'EXIT, killing the process). ((:METHOD ASDF/OPERATE:OPERATE (SYMBOL T)) ASDF/LISP-ACTION:LOAD-OP STUMPWM) [fast-method] 0] ___ 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
[news/rawdog] update to 2.18
[ I used send-pr for this about an hour ago, yet I can't see any traces of it ] Hi, attached a patch to update rawdog to the latest stable version: * feedparser isn't bundled anymore, add RUN_DEPENDS accordingly * add LICENSE info * switch from NOPORTDOCS to commonly used OPTIONS_DEFINE=DOCS Thanks, Andre rawdog.patch Description: Binary data ___ 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: 10.0-hosted tinderbox: 8.4 builds broken?
On Wed, Oct 09, 2013 at 05:59:50PM +0200, Baptiste Daroussin wrote: On Wed, Oct 09, 2013 at 06:09:55PM +0700, Alexey Dokuchaev wrote: Why does it happen? I was under impression that 8.x will never switch to pkgng. Am I doing something wrong, or need to configure my tindy somehow? 1/ yes 8.x will one day switch to pkgng :) but that is not the case yet. 2/ this is one of the design bugs of tinderbox. The very recent update of tinderbox might have fixed that one. It looks more like some recent update of tinderbox actually broke it: now, regardless of -b switch of tinderbuild command, building for: line in the logs always says 10.0-ALPHA4 i386, which is just another jail of mine. I will try to track it down and report of the results later. ./danfe ___ 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
do redports support STAGE yet?
Do redports.org understand STAGE? Anton ___ 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: 10.0-hosted tinderbox: 8.4 builds broken?
On 2013-10-09 19:59, Alexey Dokuchaev wrote: On Wed, Oct 09, 2013 at 05:59:50PM +0200, Baptiste Daroussin wrote: On Wed, Oct 09, 2013 at 06:09:55PM +0700, Alexey Dokuchaev wrote: Why does it happen? I was under impression that 8.x will never switch to pkgng. Am I doing something wrong, or need to configure my tindy somehow? 1/ yes 8.x will one day switch to pkgng :) but that is not the case yet. 2/ this is one of the design bugs of tinderbox. The very recent update of tinderbox might have fixed that one. It looks more like some recent update of tinderbox actually broke it: now, regardless of -b switch of tinderbuild command, building for: line in the logs always says 10.0-ALPHA4 i386, which is just another jail of mine. I will try to track it down and report of the results later. Please CC me in replies. I can't reproduce myself, but I can try to look tomorrow or Friday. Chris -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ 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
archivers/p5-Archive-Zip
Hello all. I try to build mailscanner, but it fails at archivers/p5-Archive-Zip This is on FreeBSD 9.2 on vmware It seems stuck root@host4:/usr/ports/archivers/p5-Archive-Zip # make install clean === Fetching all distfiles required by p5-Archive-Zip-1.30_1 for building === Extracting for p5-Archive-Zip-1.30_1 = SHA256 Checksum OK for Archive-Zip-1.30.tar.gz. rm: /usr/ports/archivers/p5-Archive-Zip/work/stage/usr/local/share/nls/en_GB.ISO8859-15: Directory not empty rm: /usr/ports/archivers/p5-Archive-Zip/work/stage/usr/local/share/nls: Directory not empty rm: /usr/ports/archivers/p5-Archive-Zip/work/stage/usr/local/share: Directory not empty rm: /usr/ports/archivers/p5-Archive-Zip/work/stage/usr/local: Directory not empty rm: /usr/ports/archivers/p5-Archive-Zip/work/stage/usr: Directory not empty rm: /usr/ports/archivers/p5-Archive-Zip/work/stage: Directory not empty rm: /usr/ports/archivers/p5-Archive-Zip/work: Directory not empty *** [do-extract] Error code 1 Stop in /usr/ports/archivers/p5-Archive-Zip. A make clean does not work. So i thought to remove the work dir by hand, but even that is not allowed?? root@host4:/usr/ports/archivers/p5-Archive-Zip # rm -rf work rm: work/stage/usr/local/share/nls/en_GB.ISO8859-15: Directory not empty rm: work/stage/usr/local/share/nls: Directory not empty rm: work/stage/usr/local/share: Directory not empty rm: work/stage/usr/local: Directory not empty rm: work/stage/usr: Directory not empty rm: work/stage: Directory not empty rm: work: Directory not empty Can somebody shed a light on this? thanks regards Johan ___ 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
STAGE: explain man pages
I'm getting: # make stage === Staging for urlview-0.9_7 === Generating temporary packing list /bin/sh ./mkinstalldirs /usr/ports/textproc/urlview/work/stage/usr/local/bin install -s -o root -g wheel -m 555 urlview /usr/ports/textproc/urlview/work/stage/usr/local/bin/urlview install -o root -g wheel -m 444 urlview.man /usr/local/man/man1/urlview.1 install -o root -g wheel -m 444 /usr/ports/textproc/urlview/work/urlview-0.9/sample.urlview /usr/ports/textproc/urlview/work/stage/usr/local/etc/urlview.conf.sample Compressing man pages # Note that the man page is not installed on stage. The Makefile has: PLIST_FILES=bin/urlview \ etc/urlview.conf.sample \ urlview.1 The last file is the man page. What am I doing wrong? Anton ___ 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: do redports support STAGE yet?
Am 09.10.2013 21:19 schrieb Anton Shterenlikht me...@bris.ac.uk: Do redports.org understand STAGE? Anton I did not verify myself but I was told that tinderbox and poudriere should support staging out of the box. Redports is using tinderbox so yes it should just work. ___ 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: 10.0-hosted tinderbox: 8.4 builds broken?
Am 09.10.2013 13:10 schrieb Alexey Dokuchaev da...@nsu.ru: Hi there, I've started to observe the following error when trying to tinderbuild (freshly cvs up'ed from marcuscom.com) a port for -b 8.4: ... add_pkg pkg-1.1.4_7.tbz adding dependencies pkg_add pkg-1.1.4_7.tbz The package management tool is not yet installed on your system. Do you want to fetch and install it now? [y/N]: tar: Error opening archive: Failed to open 'pkg-1.1.4_7.tbz' /buildscript: ./pkg-static: not found error in dependency pkg-1.1.4_7.tbz, exiting In fact, pkg-1.1.4_7.txz *is* generated for 8.4, but extensions are different (.txz vs. .tbz). Why does it happen? I was under impression that 8.x will never switch to pkgng. Am I doing something wrong, or need to configure my tindy somehow? I have seen the same on redports today. It did work fine with crees chroot patch r7 but seems to be broken with what has landed it the ports tree. ___ 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: STAGE: explain man pages
--On October 9, 2013 8:44:55 PM +0100 Anton Shterenlikht me...@bris.ac.uk wrote: I'm getting: # make stage === Staging for urlview-0.9_7 === Generating temporary packing list /bin/sh ./mkinstalldirs /usr/ports/textproc/urlview/work/stage/usr/local/bin install -s -o root -g wheel -m 555 urlview /usr/ports/textproc/urlview/work/stage/usr/local/bin/urlview install -o root -g wheel -m 444 urlview.man /usr/local/man/man1/urlview.1 install -o root -g wheel -m 444 /usr/ports/textproc/urlview/work/urlview-0.9/sample.urlview /usr/ports/textproc/urlview/work/stage/usr/local/etc/urlview.conf.sample Compressing man pages # Note that the man page is not installed on stage. The Makefile has: PLIST_FILES=bin/urlview \ etc/urlview.conf.sample \ urlview.1 The last file is the man page. What am I doing wrong? You don't need to install or uninstall man pages. They're done automatically. In the Makefile, use MANx= name of man pages e.g MAN1= urlview.1 Remove the manpage from the pkg-plist file. Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson There are some ideas so wrong that only a very intelligent person could believe in them. George Orwell ___ 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: 10.0-hosted tinderbox: 8.4 builds broken?
That's really annoying... I'll have to track it down Friday I'm afraid. Alexey, if you're interested, the patch hitting CVS is at: http://www.bayofrum.net/~crees/patches/tinderbox-calculate-deps-in-chroot-9.diff And http://www.bayofrum.net/~crees/patches/tinderbox-addPort-a.diff The patch Bernhard reports didn't have this problem is: http://www.bayofrum.net/~crees/patches/tinderbox-calculate-deps-in-chroot-7.diff Chris Sent from my android device. -Original Message- From: Bernhard Fröhlich de...@bluelife.at To: Alexey Dokuchaev da...@nsu.ru Cc: po...@freebsd.org Ports po...@freebsd.org, Chris Rees cr...@bayofrum.net Sent: Wed, 09 Oct 2013 20:52 Subject: Re: 10.0-hosted tinderbox: 8.4 builds broken? Am 09.10.2013 13:10 schrieb Alexey Dokuchaev da...@nsu.ru: Hi there, I've started to observe the following error when trying to tinderbuild (freshly cvs up'ed from marcuscom.com) a port for -b 8.4: ... add_pkg pkg-1.1.4_7.tbz adding dependencies pkg_add pkg-1.1.4_7.tbz The package management tool is not yet installed on your system. Do you want to fetch and install it now? [y/N]: tar: Error opening archive: Failed to open 'pkg-1.1.4_7.tbz' /buildscript: ./pkg-static: not found error in dependency pkg-1.1.4_7.tbz, exiting In fact, pkg-1.1.4_7.txz *is* generated for 8.4, but extensions are different (.txz vs. .tbz). Why does it happen? I was under impression that 8.x will never switch to pkgng. Am I doing something wrong, or need to configure my tindy somehow? I have seen the same on redports today. It did work fine with crees chroot patch r7 but seems to be broken with what has landed it the ports tree. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ 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: STAGE: explain man pages
On Wed, Oct 09, 2013 at 03:00:33PM -0500, Paul Schmehl wrote: --On October 9, 2013 8:44:55 PM +0100 Anton Shterenlikht me...@bris.ac.uk wrote: I'm getting: # make stage === Staging for urlview-0.9_7 === Generating temporary packing list /bin/sh ./mkinstalldirs /usr/ports/textproc/urlview/work/stage/usr/local/bin install -s -o root -g wheel -m 555 urlview /usr/ports/textproc/urlview/work/stage/usr/local/bin/urlview install -o root -g wheel -m 444 urlview.man /usr/local/man/man1/urlview.1 This is buggy ^^ you probably want to patch the upstream Makefile to respect DESTDIR as it does for all other files it installs. What you want is to change line 321 of Makefile.in to add $(DESTDIR) yes with parenthesis before $(mandir) as they already do in install-binPROGRAMS And upstream will also want that patch as that makes their installation system consistent -o root -g wheel -m 444 /usr/ports/textproc/urlview/work/urlview-0.9/sample.urlview /usr/ports/textproc/urlview/work/stage/usr/local/etc/urlview.conf.sample Compressing man pages # Note that the man page is not installed on stage. The Makefile has: PLIST_FILES=bin/urlview \ etc/urlview.conf.sample \ urlview.1 The last file is the man page. What am I doing wrong? You don't need to install or uninstall man pages. They're done automatically. In the Makefile, use MANx=name of man pages e.g MAN1= urlview.1 Remove the manpage from the pkg-plist file. Wrong. Not with stage, see: https://wiki.freebsd.org/ports/StageDir and http://blogs.freebsdish.org/portmgr/2013/10/03/staging/ the MANx macros never took care of installing the manpages btw. regards, Bapt pgp5vZoqMXIVG.pgp Description: PGP signature
Re: do redports support STAGE yet?
El 09/10/2013 21:19, Anton Shterenlikht me...@bris.ac.uk escribió: Do redports.org understand STAGE? I think it does. One of my ports was failing but after updating it with the instructions in the wiki it compiles fine. Anton ___ 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 ___ 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: STAGE: explain man pages
From pschmehl_li...@tx.rr.com Wed Oct 9 21:14:48 2013
--On October 9, 2013 8:44:55 PM +0100 Anton Shterenlikht me...@bris.ac.uk
wrote:
I'm getting:
# make stage
=== Staging for urlview-0.9_7
=== Generating temporary packing list
/bin/sh ./mkinstalldirs
/usr/ports/textproc/urlview/work/stage/usr/local/bin install -s -o
root -g wheel -m 555 urlview
/usr/ports/textproc/urlview/work/stage/usr/local/bin/urlview install -o
root -g wheel -m 444 urlview.man /usr/local/man/man1/urlview.1 install
-o root -g wheel -m 444
/usr/ports/textproc/urlview/work/urlview-0.9/sample.urlview
/usr/ports/textproc/urlview/work/stage/usr/local/etc/urlview.conf.sample
Compressing man pages
#
Note that the man page is not installed on stage.
The Makefile has:
PLIST_FILES=bin/urlview \
etc/urlview.conf.sample \
urlview.1
The last file is the man page.
What am I doing wrong?
You don't need to install or uninstall man pages. They're done
automatically.
In the Makefile, use MANx= name of man pages
e.g MAN1= urlview.1
Remove the manpage from the pkg-plist file.
No, doesn't work:
# make stage
=== Staging for urlview-0.9_7
=== Generating temporary packing list
/bin/sh ./mkinstalldirs /usr/ports/textproc/urlview/work/stage/usr/local/bin
install -s -o root -g wheel -m 555 urlview
/usr/ports/textproc/urlview/work/stage/usr/local/bin/urlview
install -o root -g wheel -m 444 urlview.man /usr/local/man/man1/urlview.1
install -o root -g wheel -m 444
/usr/ports/textproc/urlview/work/urlview-0.9/sample.urlview
/usr/ports/textproc/urlview/work/stage/usr/local/etc/urlview.conf.sample
Compressing man pages
#
To be clear, here's the complete Makefile (very simple):
# cat Makefile
# Created by: Josh Gilliam j...@quick.net
# $FreeBSD: head/textproc/urlview/Makefile 327773 2013-09-20 23:17:30Z bapt $
PORTNAME= urlview
PORTVERSION=0.9
PORTREVISION= 7
CATEGORIES= textproc www
MASTER_SITES= ftp://ftp.mutt.org/mutt/contrib/ \
ftp://ftp.cs.tu-berlin.de/pub/net/mail/mutt/contrib/ \
ftp://ftp.fu-berlin.de/pub/unix/mail/mutt/contrib/ \
ftp://ftp.gbnet.net/pub/mutt-international/contrib/ \
ftp://ftp.gwdg.de/pub/unix/mail/mutt/international/contrib/ \
http://seis.bris.ac.uk/~mexas/
MAINTAINER= me...@bris.ac.uk
COMMENT=URL extractor/launcher
GNU_CONFIGURE= yes
PLIST_FILES=bin/urlview \
etc/urlview.conf.sample
MAN1= urlview.1
CFLAGS+=-I${LOCALBASE}/include
LDFLAGS+= -L${LOCALBASE}/lib -lpcreposix -lpcre
post-patch:
@${REINPLACE_CMD} -e 's,/etc,${STAGEDIR}${PREFIX},' \
-e 's/url_handler.sh/firefox/' \
${WRKSRC}/*
post-install:
${INSTALL_DATA} ${WRKSRC}/sample.urlview \
${STAGEDIR}${PREFIX}/etc/urlview.conf.sample
.include bsd.port.mk
#
Anton
___
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: 10.0-hosted tinderbox: 8.4 builds broken?
On Wed, Oct 09, 2013 at 09:11:10PM +0100, Chris Rees wrote:
That's really annoying... I'll have to track it down Friday I'm afraid.
cvs up'ing back to sources as of Oct 6 (before your recent commits) seems
to restore correct behavior for me. Now -b 8.4 builds do not try to find
or install pkgng, and building for: line correctly depends on -b switch
as it should.
Alexey, if you're interested, the patch hitting CVS is at:
http://www.bayofrum.net/~crees/patches/tinderbox-calculate-deps-in-chroot-9.diff
I'll try to play with it to see if I can fix the problem without reverting
the repo back to Oct 6th state, thanks!
BTW, is createJail command working properly now for both old and new style
releases? I've been using the following patch for a while now, not sure
if it is still relevant though:
@@ -107,7 +107,7 @@ generateUpdateCode () {
fetchRc=0
tested=0
while [ 1 -eq 1 ]; do
-${fetchCmd} -s ${fetchUrl}/${fetchSets%%*}${fetchSufx} /dev/null 21
+${fetchCmd} -s ${fetchUrl}/${fetchSets%%*}${fetchSufx} | grep -qv
Unknown
./danfe
___
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: STAGE: explain man pages
From baptiste.darous...@gmail.com Wed Oct 9 21:14:50 2013 On Wed, Oct 09, 2013 at 03:00:33PM -0500, Paul Schmehl wrote: --On October 9, 2013 8:44:55 PM +0100 Anton Shterenlikht me...@bris.ac.u= k=20 wrote: =20 I'm getting: # make stage =3D=3D=3D Staging for urlview-0.9_7 =3D=3D=3D Generating temporary packing list /bin/sh ./mkinstalldirs /usr/ports/textproc/urlview/work/stage/usr/local/bin install -s -o root -g wheel -m 555 urlview /usr/ports/textproc/urlview/work/stage/usr/local/bin/urlview install -o root -g wheel -m 444 urlview.man /usr/local/man/man1/urlview.1 This is buggy ^^ you probably want to patch the upstream Makefile to respect DESTDIR as it does for all other files it installs. What you want is to change line 321 of Makefile.in to add $(DESTDIR) yes wi= th parenthesis before $(mandir) as they already do in install-binPROGRAMS And upstream will also want that patch as that makes their installation sys= tem consistent ok, cool! So now I get: === Staging for urlview-0.9_7 === Generating temporary packing list /bin/sh ./mkinstalldirs /usr/ports/textproc/urlview/work/stage/usr/local/bin install -s -o root -g wheel -m 555 urlview /usr/ports/textproc/urlview/work/stage/usr/local/bin/urlview install -o root -g wheel -m 444 urlview.man /usr/ports/textproc/urlview/work/stage/usr/local/man/man1/urlview.1 install -o root -g wheel -m 444 /usr/ports/textproc/urlview/work/urlview-0.9/sample.urlview /usr/ports/textproc/urlview/work/stage/usr/local/etc/urlview.conf.sample Compressing man pages # But then: # make makeplist bin/urlview etc/urlview.conf.sample man/man1/urlview.1.gz # make check-orphans man/man1/urlview.1.gz # make package === Building package for urlview-0.9_7 pkg-static: lstat(/usr/ports/textproc/urlview/work/stage/usr/local/urlview.1): No such file or directory *** Error code 1 Stop. make: stopped in /usr/ports/textproc/urlview # What is wrong here? Many thanks Anton ___ 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: STAGE: explain man pages
From mexas Wed Oct 9 21:32:05 2013 To: b...@freebsd.org, pschmehl_li...@tx.rr.com Subject: Re: STAGE: explain man pages Cc: freebsd-ports@freebsd.org, me...@bris.ac.uk Reply-To: me...@bris.ac.uk In-Reply-To: 20131009201145.gd95...@ithaqua.etoilebsd.net From baptiste.darous...@gmail.com Wed Oct 9 21:14:50 2013 On Wed, Oct 09, 2013 at 03:00:33PM -0500, Paul Schmehl wrote: --On October 9, 2013 8:44:55 PM +0100 Anton Shterenlikht me...@bris.ac.u= k=20 wrote: =20 I'm getting: # make stage =3D=3D=3D Staging for urlview-0.9_7 =3D=3D=3D Generating temporary packing list /bin/sh ./mkinstalldirs /usr/ports/textproc/urlview/work/stage/usr/local/bin install -s -o root -g wheel -m 555 urlview /usr/ports/textproc/urlview/work/stage/usr/local/bin/urlview install -o root -g wheel -m 444 urlview.man /usr/local/man/man1/urlview.1 This is buggy ^^ you probably want to patch the upstream Makefile to respect DESTDIR as it does for all other files it installs. What you want is to change line 321 of Makefile.in to add $(DESTDIR) yes wi= th parenthesis before $(mandir) as they already do in install-binPROGRAMS And upstream will also want that patch as that makes their installation sys= tem consistent ok, cool! So now I get: === Staging for urlview-0.9_7 === Generating temporary packing list /bin/sh ./mkinstalldirs /usr/ports/textproc/urlview/work/stage/usr/local/bin install -s -o root -g wheel -m 555 urlview /usr/ports/textproc/urlview/work/stage/usr/local/bin/urlview install -o root -g wheel -m 444 urlview.man /usr/ports/textproc/urlview/work/stage/usr/local/man/man1/urlview.1 install -o root -g wheel -m 444 /usr/ports/textproc/urlview/work/urlview-0.9/sample.urlview /usr/ports/textproc/urlview/work/stage/usr/local/etc/urlview.conf.sample Compressing man pages # But then: # make makeplist bin/urlview etc/urlview.conf.sample man/man1/urlview.1.gz # make check-orphans man/man1/urlview.1.gz # make package === Building package for urlview-0.9_7 pkg-static: lstat(/usr/ports/textproc/urlview/work/stage/usr/local/urlview.1): No such file or directory *** Error code 1 Stop. make: stopped in /usr/ports/textproc/urlview # What is wrong here? I think I got it: I need to give the full name of the man page, as it appears in makeplist output: PLIST_FILES=bin/urlview \ etc/urlview.conf.sample \ man/man1/urlview.1.gz Then: === Staging for urlview-0.9_7 === Generating temporary packing list /bin/sh ./mkinstalldirs /usr/ports/textproc/urlview/work/stage/usr/local/bin install -s -o root -g wheel -m 555 urlview /usr/ports/textproc/urlview/work/stage/usr/local/bin/urlview install -o root -g wheel -m 444 urlview.man /usr/ports/textproc/urlview/work/stage/usr/local/man/man1/urlview.1 install -o root -g wheel -m 444 /usr/ports/textproc/urlview/work/urlview-0.9/sample.urlview /usr/ports/textproc/urlview/work/stage/usr/local/etc/urlview.conf.sample Compressing man pages # make makeplist bin/urlview etc/urlview.conf.sample man/man1/urlview.1.gz # make check-orphans # make package === Building package for urlview-0.9_7 Service unavailable# Ok, that is good. And what does Service unavailable mean? Thanks Anton ___ 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: STAGE: explain man pages
On Wed, Oct 09, 2013 at 09:32:05PM +0100, Anton Shterenlikht wrote: From baptiste.darous...@gmail.com Wed Oct 9 21:14:50 2013 On Wed, Oct 09, 2013 at 03:00:33PM -0500, Paul Schmehl wrote: --On October 9, 2013 8:44:55 PM +0100 Anton Shterenlikht me...@bris.ac.u= k=20 wrote: =20 I'm getting: # make stage =3D=3D=3D Staging for urlview-0.9_7 =3D=3D=3D Generating temporary packing list /bin/sh ./mkinstalldirs /usr/ports/textproc/urlview/work/stage/usr/local/bin install -s -o root -g wheel -m 555 urlview /usr/ports/textproc/urlview/work/stage/usr/local/bin/urlview install -o root -g wheel -m 444 urlview.man /usr/local/man/man1/urlview.1 This is buggy ^^ you probably want to patch the upstream Makefile to respect DESTDIR as it does for all other files it installs. What you want is to change line 321 of Makefile.in to add $(DESTDIR) yes wi= th parenthesis before $(mandir) as they already do in install-binPROGRAMS And upstream will also want that patch as that makes their installation sys= tem consistent ok, cool! So now I get: === Staging for urlview-0.9_7 === Generating temporary packing list /bin/sh ./mkinstalldirs /usr/ports/textproc/urlview/work/stage/usr/local/bin install -s -o root -g wheel -m 555 urlview /usr/ports/textproc/urlview/work/stage/usr/local/bin/urlview install -o root -g wheel -m 444 urlview.man /usr/ports/textproc/urlview/work/stage/usr/local/man/man1/urlview.1 install -o root -g wheel -m 444 /usr/ports/textproc/urlview/work/urlview-0.9/sample.urlview /usr/ports/textproc/urlview/work/stage/usr/local/etc/urlview.conf.sample Compressing man pages # But then: # make makeplist bin/urlview etc/urlview.conf.sample man/man1/urlview.1.gz # make check-orphans man/man1/urlview.1.gz # make package === Building package for urlview-0.9_7 pkg-static: lstat(/usr/ports/textproc/urlview/work/stage/usr/local/urlview.1): No such file or directory *** Error code 1 Stop. make: stopped in /usr/ports/textproc/urlview # What is wrong here? Many thanks Anton As said in make check-orphans the file you need in your plist_file is man/man1/urlview.1.gz not urlview.1 regards, Bapt pgppngV0EK4dQ.pgp Description: PGP signature
Re: Serf update?
On 10/05/13 23:12, olli hauer wrote: On 2013-10-01 18:12, Andrea Venturoli wrote: Hello. Any plan on an update to 1.3? Any timeline? I'm experiencing some bugs with Subversion and somewhere they suggest to try Serf 1.3. Just to decide whether to wait or try something else... I've created a serf-1.3.2 port for testing. http://people.freebsd.org/~ohauer/shar/serf-1.3.shar Since serf-1.3.x uses scons to build we do not get required .la files to build a static subversion. Thanks. The problem I'm having is that my FreeBSD's subversion (1.8.3) cannot connect anymore to an Ubuntu apache22 server, after that side was upgraded, when using https. Looking through forums, I saw some posts blaming this on Serf 1.2. So I downloaded your ports, extracted it, forcibly deleted serf-1.2, installed this 1.3, and recompiled Subversion. Unfortunately it did not help :( bye Thanks anyway av. ___ 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
Messages while (re)installing portupgrade
Because I just switched from ruby1.8 to ruby1.9 I've had to
rebuild and reinstall my ports-mgmt/portupgrade port. That all
went well, but I got some messages at the end of the re-install
process that I've never noticed before, and they are all rather
befuddling to me:
--
Fill ALT_PKGDEP section in pkgtools.conf file for portupgrade to be
aware of alternative dependencies you use.
E.g.
ALT_PKGDEP = {
# Use the -nox11 port when another port depends on category/portexample
'category/portexample' = 'category/portexample-nox11',
}
Note also, portupgrade knows nothing about how to handle ports with
different suffixes (E.g. -nox11). So you should explicitly define
variables (E.g. WITHOUT_X11=yes) for the ports in /etc/make.conf or
pkgtools.conf (MAKE_ARGS section) files.
--
I have no idea what any of the above means. Should I be at all concerned?
Where exactly is this alleged pkgtools.conf file. I looked in /etc.
It ain't there. I've never even heard of it until today.
I grok the general idea that there may be a file someplace (called
pkgtools.conf) wherein one may explicitly override various otherwise
hardwired inter-port dependencies, but what has that got to do with
me?
I _do_ use X, so none of the rest of this stuff seems the least bit
relevant to anything I am doing. Am I perhaps mistaken?
___
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: lang/gcc with default port options don't compile
Hi, Try compile lang/gcc with all options selected (Bootstrap=ON and Java=On), it works for me ... Regards Luis Otte Hi, If I compile lang/gcc with default port options: root at acer_casa_FreeBSD:/usr/ports/lang/gcc # make showconfig === The following configuration options are available for gcc-4.6.3: BOOTSTRAP=off: Build using a full bootstrap JAVA=on: Java platform support === Use 'make config' to modify these settings root at acer_casa_FreeBSD:/usr/ports/lang/gcc # I get next error: decnumber/dpd -I../libdecnumber -I/usr/local/include .././../gcc-4.6.3/gcc/c-f amily/c-common.c -o c-family/c-common.o .././../gcc-4.6.3/gcc/c-family/c-common.c: In function 'record_types_used_by_cur rent_var_decl': .././../gcc-4.6.3/gcc/c-family/c-common.c:9537: error: 'types_used_by_cur_var_de cl' undeclared (first use in this function) .././../gcc-4.6.3/gcc/c-family/c-common.c:9537: error: (Each undeclared identifi er is reported only once .././../gcc-4.6.3/gcc/c-family/c-common.c:9537: error: for each function it appe ars in.) .././../gcc-4.6.3/gcc/c-family/c-common.c:9540: warning: implicit declaration of function 'types_used_by_var_decl_insert' gmake[2]: *** [c-family/c-common.o] Error 1 gmake[2]: Leaving directory `/usr/ports/lang/gcc/work/build/gcc' gmake[1]: *** [all-gcc] Error 2 gmake[1]: Leaving directory `/usr/ports/lang/gcc/work/build' gmake: *** [all] Error 2 *** [do-build] Error code 1 Stop in /usr/ports/lang/gcc. *** [build] Error code 1 Stop in /usr/ports/lang/gcc. root at acer_casa_FreeBSD:/usr/ports/lang/gcc # Somebody can help me ? See 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
Re: Messages while (re)installing portupgrade
On 10/9/2013 6:35 PM, Ronald F. Guilmette wrote:
Because I just switched from ruby1.8 to ruby1.9 I've had to
rebuild and reinstall my ports-mgmt/portupgrade port. That all
went well, but I got some messages at the end of the re-install
process that I've never noticed before, and they are all rather
befuddling to me:
--
Fill ALT_PKGDEP section in pkgtools.conf file for portupgrade to be
aware of alternative dependencies you use.
E.g.
ALT_PKGDEP = {
# Use the -nox11 port when another port depends on
category/portexample
'category/portexample' = 'category/portexample-nox11',
}
Note also, portupgrade knows nothing about how to handle ports with
different suffixes (E.g. -nox11). So you should explicitly define
variables (E.g. WITHOUT_X11=yes) for the ports in /etc/make.conf or
pkgtools.conf (MAKE_ARGS section) files.
--
I have no idea what any of the above means. Should I be at all concerned?
This has been here for many years. You can safely ignore this. It is
just a way to override port dependencies if you want without needing to
modify the port files.
Where exactly is this alleged pkgtools.conf file. I looked in /etc.
It ain't there. I've never even heard of it until today.
portupgrade supports a config file in /usr/local/etc/pkgtools.conf
I grok the general idea that there may be a file someplace (called
pkgtools.conf) wherein one may explicitly override various otherwise
hardwired inter-port dependencies, but what has that got to do with
me?
I _do_ use X, so none of the rest of this stuff seems the least bit
relevant to anything I am doing. Am I perhaps mistaken?
--
Regards,
Bryan Drewery
signature.asc
Description: OpenPGP digital signature
Re: FreeBSD Port: lang/sbcl
On 10/9/13, Joseph Mingrone j...@ftfl.ca wrote: Hi, After upgrading sbcl to 1.1.12, stumpwm no longer compiles. I'm compiling stumpwm from the git repository, which hasn't changed in quite awhile. If there is anything I can test or any other information I can provide, please let me know. Joseph % gmake /usr/local/bin/sbcl --load ./make-image.lisp This is SBCL 1.1.12, an implementation of ANSI Common Lisp. More information about SBCL is available at http://www.sbcl.org/. SBCL is free software, provided as is, with absolutely no warranty. It is mostly in the public domain; some portions are provided under BSD-style licenses. See the CREDITS and COPYING files in the distribution for more information. WARNING: compiling #STATIC-FILE sb-bsd-sockets NEWS completed without its input file #P/usr/local/lib/sbcl/sb-bsd-sockets/NEWS WARNING: loading #STATIC-FILE sb-bsd-sockets NEWS completed without its input file #P/usr/local/lib/sbcl/sb-bsd-sockets/NEWS WARNING: compiling #STATIC-FILE sb-bsd-sockets TODO completed without its input file #P/usr/local/lib/sbcl/sb-bsd-sockets/TODO WARNING: loading #STATIC-FILE sb-bsd-sockets TODO completed without its input file #P/usr/local/lib/sbcl/sb-bsd-sockets/TODO debugger invoked on a ASDF/FIND-SYSTEM:MISSING-COMPONENT: Component STUMPWM not found Yes, lang/sbcl switched to a newer version of ASDF, which handles the loading of modules differently. I had hoped to patch the two dependent ports that are now broken because of this as part of the sbcl update, but I was coming under some pressure to update sbcl, and I didn't have a lot of time. From my cursory look during the sbcl update, I believe that this error can be fixed by patching the broken dependent ports so that they issue a pathspec to the working directory in the require statement in the Makefile, or by splitting eache of the broken ports into two subports, one of which installs source code in the system module directory, and another which subsequently compiles it, as is done now for some of the cl-* ports. I don't know if there are other problems. When the ASDF port and other CL compilers are updated to newer versions of ASDF, the broken ports will probably not work with them, either. Regards, b. Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [RETRY ] Retry EVAL of current toplevel form. 1: [CONTINUE] Ignore error and continue loading file /usr/home/jrm/scm/stumpwm.git/./make-image.lisp. 2: [ABORT ] Abort loading file /usr/home/jrm/scm/stumpwm.git/./make-image.lisp. 3:Ignore runtime option --load ./make-image.lisp. 4:Skip rest of --eval and --load options. 5:Skip to toplevel READ/EVAL/PRINT loop. 6: [EXIT] Exit SBCL (calling #'EXIT, killing the process). ((:METHOD ASDF/OPERATE:OPERATE (SYMBOL T)) ASDF/LISP-ACTION:LOAD-OP STUMPWM) [fast-method] 0] ___ 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
