INDEX build failed for 8.x
INDEX build failed with errors: Generating INDEX-8 - please wait../home/indexbuild/tindex/ports/Mk/bsd.pbi.mk, line 20: warning: duplicate script for target check-pbimanager ignored /home/indexbuild/tindex/ports/Mk/bsd.pbi.mk, line 45: warning: duplicate script for target pbi-generate ignored /home/indexbuild/tindex/ports/Mk/bsd.pbi.mk, line 46: warning: duplicate script for target pbi-generate ignored /home/indexbuild/tindex/ports/Mk/bsd.pbi.mk, line 47: warning: duplicate script for target pbi-generate ignored /home/indexbuild/tindex/ports/Mk/bsd.pbi.mk, line 50: warning: duplicate script for target clean-pbi ignored /home/indexbuild/tindex/ports/Mk/bsd.pbi.mk, line 51: warning: duplicate script for target clean-pbi ignored Done. make_index: emh-xemacs21-mule-1.14.1_13: no entry for /usr/ports/editors/semi-xemacs21-mule make_index: emh-xemacs21-mule-1.14.1_13: no entry for /usr/ports/editors/semi-xemacs21-mule make_index: wanderlust-xemacs21-mule-2.14.0_14: no entry for /usr/ports/editors/semi-xemacs21-mule make_index: wanderlust-xemacs21-mule-2.14.0_14: no entry for /usr/ports/editors/semi-xemacs21-mule Committers on the hook: amdmi3 bapt beech dinoex glewis koobs linimon marcus miwi rm sunpoet wen Most recent SVN update was: Updating '.': Uports-mgmt/portlint/src/portlint.pl Uports-mgmt/portlint/Makefile Uwww/rubygem-jwt/Makefile UU www/rubygem-jwt/distinfo UU astro/cfitsio/pkg-plist Uastro/cfitsio/Makefile Uastro/cfitsio/distinfo Ddevel/buildbot/files Udevel/buildbot/distinfo Udevel/buildbot/pkg-plist Udevel/buildbot/Makefile UU devel/buildbot-slave/distinfo UU devel/buildbot-slave/files/patch-setup.py Adevel/buildbot-slave/files/patch-buildslave__testinit__.py UU devel/buildbot-slave/pkg-plist UU devel/buildbot-slave/Makefile Atextproc/stardict-dict-fa_IR Atextproc/stardict-dict-fa_IR/Makefile Atextproc/stardict-dict-fa_IR/distinfo Atextproc/stardict-dict-fa_IR/pkg-descr Utextproc/Makefile Ulang/dlv/Makefile Ulang/dlv/distinfo Ulang/dlv/pkg-descr Ugraphics/netpbm/distinfo Ugraphics/netpbm/Makefile Ugraphics/giflib/pkg-plist Ugraphics/giflib/Makefile Unet-im/libpurple/Makefile Anet-im/libpurple/files/patch-libpurple-protocols-irc-Makefile.in Anet-im/libpurple/files/patch-libpurple-protocols-irc-Makefile.am Updated to revision 313817. ___ 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
INDEX now builds successfully on 8.x
___ 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
CURRENT (r248128): PKGNG weirdness: openldap-sasl-client-2.4.33_1 conflicts with installed package(s): openldap-sasl-client-2.4.33_1 AND /usr/local AND net/openldap24-sasl-client
On FreeBSD 10.0-CURRENT #0 r248128: Sun Mar 10 10:41:10 CET 2013 I receive the error message below when trying to update installed port openldap24-sasl-client: === Cleaning for openldap-sasl-client-2.4.33_1 === Waiting on fetch checksum for net/openldap24-sasl-client === === openldap-sasl-client-2.4.33_1 conflicts with installed package(s): openldap-sasl-client-2.4.33_1 /usr/local net/openldap24-sasl-client They install files into the same place. You may want to stop build with Ctrl + C. This looks weird tome, since how can /usr/local/ be a port? My update tool is ports-mgmt/portmaster. Regards, Oliver ___ 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 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 +-+ graphics/rawtherapee| 4.0.9 | 4.0.10 +-+ 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...@portscout.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: FreeBSD Port: pftop-0.7_1
Fabian Keil freebsd-lis...@fabiankeil.de wrote: Thomas Kinsey t...@exigent.com wrote: I've noticed that rule numbers do not display in pftop, and further that this (http://openbsd.7691.n7.nabble.com/pftop-Rule-number-shown-as-quot-0-quot-or-quot-quot-td122537.html) seems to resolve the issue. Not being fluent in C, I'm not really sure what is going on here, but I hope this helps! Thanks for the report. If you are using pf 4.5 you could try the following patch: http://www.fabiankeil.de/sourcecode/freebsd/pftop-0.7_2.diff If you aren't, please let me know the FreeBSD or pf version and I'll update the patch. Thomas confirmed via private mail that the patch works as expected. Could someone please timeout ports/175927 and apply it? ports/164362 could then be closed as well. Fabian signature.asc Description: PGP signature
Re: VirtualBox broken by recent commit -248084
On 10 Mar 2013 07:07, AN a...@neu.net wrote: FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #36 r248127: Sun Mar 10 00:13:59 CST 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 Virtualbox was broken by this commit: http://svnweb.freebsd.org/base?view=revisionrevision=248084 === Registering installation for virtualbox-ose-kmod-4.2.6_1 Installing virtualbox-ose-kmod-4.2.6_1... done === Cleaning for virtualbox-ose-kmod-4.2.6_1 [root@FBSD10 /usr/ports/emulators/virtualbox-ose-kmod]# kldload vboxdrv.ko kldload: can't load vboxdrv.ko: Exec format error This error isn't helpful; what went into /var/log/messages as kldload was executed? Chris ___ 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: VirtualBox broken by recent commit -248084
Em Dom, 2013-03-10 às 15:43 +, Chris Rees escreveu: On 10 Mar 2013 07:07, AN a...@neu.net wrote: FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #36 r248127: Sun Mar 10 00:13:59 CST 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 Virtualbox was broken by this commit: http://svnweb.freebsd.org/base?view=revisionrevision=248084 === Registering installation for virtualbox-ose-kmod-4.2.6_1 Installing virtualbox-ose-kmod-4.2.6_1... done === Cleaning for virtualbox-ose-kmod-4.2.6_1 [root@FBSD10 /usr/ports/emulators/virtualbox-ose-kmod]# kldload vboxdrv.ko kldload: can't load vboxdrv.ko: Exec format error This error isn't helpful; what went into /var/log/messages as kldload was executed? Chris ___ 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 The last 10.0 CURRENT changed the way lock is handled. so a fix in the virtualbox-kmod is needed put this file the files directory and do a make clean install should 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: VirtualBox broken by recent commit -248084
On Sun, 10 Mar 2013, Chris Rees wrote: On 10 Mar 2013 07:07, AN a...@neu.net wrote: FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #36 r248127: Sun Mar 10 00:13:59 CST 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 Virtualbox was broken by this commit: http://svnweb.freebsd.org/base?view=revisionrevision=248084 === Registering installation for virtualbox-ose-kmod-4.2.6_1 Installing virtualbox-ose-kmod-4.2.6_1... done === Cleaning for virtualbox-ose-kmod-4.2.6_1 [root@FBSD10 /usr/ports/emulators/virtualbox-ose-kmod]# kldload vboxdrv.ko kldload: can't load vboxdrv.ko: Exec format error This error isn't helpful; what went into /var/log/messages as kldload was executed? Chris Hi Chris: # kldload vboxdrv.ko then from dmesg: link_elf_obj: symbol VM_OBJECT_LOCK undefined linker_load_file: Unsupported file type ___ 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: nvidia-driver broken by recent commit - 248084
On Sun, Mar 10, 2013 at 1:17 AM, AN a...@neu.net wrote: FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #36 r248127: Sun Mar 10 00:13:59 CST 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 /usr/ports/x11/nvidia-driver is broken, probably by this commit: http://svnweb.freebsd.org/base?view=revisionrevision=248084 From commit log:The KPI results heavilly broken by this commit. Thirdy part ports must be updated accordingly (I can think off-hand of VirtualBox, for example). root@FBSD10 /usr/ports/x11/nvidia-driver]# make clean === Cleaning for nvidia-driver-310.32 [root@FBSD10 /usr/ports/x11/nvidia-driver]# make install clean === License NVIDIA accepted by the user === Found saved configuration for nvidia-driver-304.64 === nvidia-driver-310.32 depends on file: /usr/local/sbin/pkg - found === Extracting for nvidia-driver-310.32 = SHA256 Checksum OK for NVIDIA-FreeBSD-x86_64-310.32.tar.gz. === Patching for nvidia-driver-310.32 === Applying extra patch /usr/ports/x11/nvidia-driver/files/r246085-patch-src-nvidia_linux.c === nvidia-driver-310.32 depends on file: /usr/local/libdata/pkgconfig/xorg-server.pc - found === nvidia-driver-310.32 depends on shared library: GL.1 - found === Configuring for nvidia-driver-310.32 === Building for nvidia-driver-310.32 === src (all) @ - /usr/src/sys machine - /usr/src/sys/amd64/include x86 - /usr/src/sys/x86/include awk -f @/tools/makeobjops.awk @/kern/device_if.m -h awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h awk -f @/tools/makeobjops.awk @/dev/pci/pci_if.m -h awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -p awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -q awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -h cc -O2 -pipe -fno-strict-aliasing -DNV_VERSION_STRING=\310.32\ -D__KERNEL__ -DNVRM -Wno-unused-function -Wuninitialized -O -mno-red-zone -mcmodel=kernel -UDEBUG -U_DEBUG -DNDEBUG -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I. -I@ -I@/contrib/altq -fno-common -fno-omit-frame-pointer -mno-aes -mno-avx -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -std=iso9899:1999 -Qunused-arguments -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -c nvidia_ctl.c In file included from nvidia_ctl.c:14: In file included from ./nv-freebsd.h:77: @/vm/vm_pager.h:127:2: error: implicit declaration of function 'rw_assert' is invalid in C99 [-Werror,-Wimplicit-function-declaration] VM_OBJECT_ASSERT_WLOCKED(object); ^ @/vm/vm_object.h:212:2: note: expanded from macro 'VM_OBJECT_ASSERT_WLOCKED' rw_assert((object)-lock, RA_WLOCKED) ^ In file included from nvidia_ctl.c:14: In file included from ./nv-freebsd.h:77: @/vm/vm_pager.h:127:2: error: use of undeclared identifier 'RA_WLOCKED' VM_OBJECT_ASSERT_WLOCKED(object); ^ @/vm/vm_object.h:212:29: note: expanded from macro 'VM_OBJECT_ASSERT_WLOCKED' rw_assert((object)-lock, RA_WLOCKED) ^ In file included from nvidia_ctl.c:14: In file included from ./nv-freebsd.h:77: @/vm/vm_pager.h:144:2: error: use of undeclared identifier 'RA_WLOCKED' VM_OBJECT_ASSERT_WLOCKED(object); ^ @/vm/vm_object.h:212:29: note: expanded from macro 'VM_OBJECT_ASSERT_WLOCKED' rw_assert((object)-lock, RA_WLOCKED) ^ In file included from nvidia_ctl.c:14: In file included from ./nv-freebsd.h:77: @/vm/vm_pager.h:168:2: error: use of undeclared identifier 'RA_WLOCKED' VM_OBJECT_ASSERT_WLOCKED(object); ^ @/vm/vm_object.h:212:29: note: expanded from macro 'VM_OBJECT_ASSERT_WLOCKED' rw_assert((object)-lock, RA_WLOCKED) ^ In file included from nvidia_ctl.c:14: In file included from ./nv-freebsd.h:77: @/vm/vm_pager.h:191:2: error: use of undeclared identifier 'RA_WLOCKED' VM_OBJECT_ASSERT_WLOCKED(m-object); ^ @/vm/vm_object.h:212:29: note: expanded from macro 'VM_OBJECT_ASSERT_WLOCKED' rw_assert((object)-lock, RA_WLOCKED) ^ 5 errors generated. *** [nvidia_ctl.o] Error code 1 Stop in /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86_64-310.32/src. *** [all] Error code 1 Stop in /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86_64-310.32. *** [do-build] Error code 1 Stop in /usr/ports/x11/nvidia-driver. *** [install] Error code 1 Stop in /usr/ports/x11/nvidia-driver. [root@FBSD10 /usr/ports/x11/nvidia-driver]# Place the following diff in a file at /usr/ports/x11/nvidia-driver/files/patch-r248084-vm-locking-changes.diff
Re: VirtualBox broken by recent commit -248084
On Sun, 10 Mar 2013, Sergio de Almeida Lenzi wrote: Em Dom, 2013-03-10 as 15:43 +, Chris Rees escreveu: On 10 Mar 2013 07:07, AN a...@neu.net wrote: FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #36 r248127: Sun Mar 10 00:13:59 CST 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 Virtualbox was broken by this commit: http://svnweb.freebsd.org/base?view=revisionrevision=248084 === Registering installation for virtualbox-ose-kmod-4.2.6_1 Installing virtualbox-ose-kmod-4.2.6_1... done === Cleaning for virtualbox-ose-kmod-4.2.6_1 [root@FBSD10 /usr/ports/emulators/virtualbox-ose-kmod]# kldload vboxdrv.ko kldload: can't load vboxdrv.ko: Exec format error This error isn't helpful; what went into /var/log/messages as kldload was executed? Chris The last 10.0 CURRENT changed the way lock is handled. so a fix in the virtualbox-kmod is needed put this file the files directory and do a make clean install should work... I can confirm that with the attached patch, VirtualBox is working again. Thanks Sergio for the fix. # kldstat Id Refs AddressSize Name 1 18 0x8020 117e9a0 kernel 21 0x81412000 9a02 linprocfs.ko 31 0x8141c000 4fbcblinux.ko 41 0x8146c000 3493 ums.ko 51 0x8147 29c4 uhid.ko [root@FBSD10 /usr/ports/emulators/virtualbox-ose-kmod]# kldload vboxdrv.ko [root@FBSD10 /usr/ports/emulators/virtualbox-ose-kmod]# kldstat Id Refs AddressSize Name 1 20 0x8020 117e9a0 kernel 21 0x81412000 9a02 linprocfs.ko 31 0x8141c000 4fbcblinux.ko 41 0x8146c000 3493 ums.ko 51 0x8147 29c4 uhid.ko 61 0x81473000 2e7c0vboxdrv.ko ___ 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: nvidia-driver broken by recent commit - 248084
On Sun, 10 Mar 2013, Brandon Gooch wrote: On Sun, Mar 10, 2013 at 1:17 AM, AN a...@neu.net wrote: FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #36 r248127: Sun Mar 10 00:13:59 CST 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 /usr/ports/x11/nvidia-driver is broken, probably by this commit: http://svnweb.freebsd.org/base?view=revisionrevision=248084 From commit log:The KPI results heavilly broken by this commit. Thirdy part ports must be updated accordingly (I can think off-hand of VirtualBox, for example). root@FBSD10 /usr/ports/x11/nvidia-driver]# make clean === Cleaning for nvidia-driver-310.32 [root@FBSD10 /usr/ports/x11/nvidia-driver]# make install clean === License NVIDIA accepted by the user === Found saved configuration for nvidia-driver-304.64 === nvidia-driver-310.32 depends on file: /usr/local/sbin/pkg - found === Extracting for nvidia-driver-310.32 = SHA256 Checksum OK for NVIDIA-FreeBSD-x86_64-310.32.tar.gz. === Patching for nvidia-driver-310.32 === Applying extra patch /usr/ports/x11/nvidia-driver/files/r246085-patch-src-nvidia_linux.c === nvidia-driver-310.32 depends on file: /usr/local/libdata/pkgconfig/xorg-server.pc - found === nvidia-driver-310.32 depends on shared library: GL.1 - found === Configuring for nvidia-driver-310.32 === Building for nvidia-driver-310.32 === src (all) @ - /usr/src/sys machine - /usr/src/sys/amd64/include x86 - /usr/src/sys/x86/include awk -f @/tools/makeobjops.awk @/kern/device_if.m -h awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h awk -f @/tools/makeobjops.awk @/dev/pci/pci_if.m -h awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -p awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -q awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -h cc -O2 -pipe -fno-strict-aliasing -DNV_VERSION_STRING=\310.32\ -D__KERNEL__ -DNVRM -Wno-unused-function -Wuninitialized -O -mno-red-zone -mcmodel=kernel -UDEBUG -U_DEBUG -DNDEBUG -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I. -I@ -I@/contrib/altq -fno-common -fno-omit-frame-pointer -mno-aes -mno-avx -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -std=iso9899:1999 -Qunused-arguments -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -c nvidia_ctl.c In file included from nvidia_ctl.c:14: In file included from ./nv-freebsd.h:77: @/vm/vm_pager.h:127:2: error: implicit declaration of function 'rw_assert' is invalid in C99 [-Werror,-Wimplicit-function-declaration] VM_OBJECT_ASSERT_WLOCKED(object); ^ @/vm/vm_object.h:212:2: note: expanded from macro 'VM_OBJECT_ASSERT_WLOCKED' rw_assert((object)-lock, RA_WLOCKED) ^ In file included from nvidia_ctl.c:14: In file included from ./nv-freebsd.h:77: @/vm/vm_pager.h:127:2: error: use of undeclared identifier 'RA_WLOCKED' VM_OBJECT_ASSERT_WLOCKED(object); ^ @/vm/vm_object.h:212:29: note: expanded from macro 'VM_OBJECT_ASSERT_WLOCKED' rw_assert((object)-lock, RA_WLOCKED) ^ In file included from nvidia_ctl.c:14: In file included from ./nv-freebsd.h:77: @/vm/vm_pager.h:144:2: error: use of undeclared identifier 'RA_WLOCKED' VM_OBJECT_ASSERT_WLOCKED(object); ^ @/vm/vm_object.h:212:29: note: expanded from macro 'VM_OBJECT_ASSERT_WLOCKED' rw_assert((object)-lock, RA_WLOCKED) ^ In file included from nvidia_ctl.c:14: In file included from ./nv-freebsd.h:77: @/vm/vm_pager.h:168:2: error: use of undeclared identifier 'RA_WLOCKED' VM_OBJECT_ASSERT_WLOCKED(object); ^ @/vm/vm_object.h:212:29: note: expanded from macro 'VM_OBJECT_ASSERT_WLOCKED' rw_assert((object)-lock, RA_WLOCKED) ^ In file included from nvidia_ctl.c:14: In file included from ./nv-freebsd.h:77: @/vm/vm_pager.h:191:2: error: use of undeclared identifier 'RA_WLOCKED' VM_OBJECT_ASSERT_WLOCKED(m-object); ^ @/vm/vm_object.h:212:29: note: expanded from macro 'VM_OBJECT_ASSERT_WLOCKED' rw_assert((object)-lock, RA_WLOCKED) ^ 5 errors generated. *** [nvidia_ctl.o] Error code 1 Stop in /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86_64-310.32/src. *** [all] Error code 1 Stop in /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86_64-310.32. *** [do-build] Error code 1 Stop in /usr/ports/x11/nvidia-driver. *** [install] Error code 1 Stop in /usr/ports/x11/nvidia-driver. [root@FBSD10 /usr/ports/x11/nvidia-driver]# Place the following diff in a file at /usr/ports/x11/nvidia-driver/files/patch-r248084-vm-locking-changes.diff (assuming your ports tree is at /usr/ports; adjust
Re: Re: [RFC] lang/pypy
On Sunday, 10 March 2013 00:37:15 poyop...@puripuri.plala.or.jp wrote: Hi, good work, David. Hi Kuro It compiles, packages and works flawlessly here for replacement of 1.9 so far for a week. Great, thanks. Good to know :-) On my compile box, amd64/Athlon64 5050e 2.6GHz 2 core/8GB, memory requirement for translation processes is far less than warning shown. It prevents build with | warn: this system has insufficient memory, expected at least 9227MiB RAM however my translation processes under -DPYPY_IGNORE_MEMORY take 2GB for normal binary and 2.5GB for sandboxed one so they aggregate 4.5GB to run parallel. This is good news. Could you please detail how you measured peak memory? I might need to retest the port. This is far less than expected, no page thrashing, no hang, no stuttering. It does not matter being with pypy1.9 or pypy2.0 (yes, I built twice for 2.0 self hosting. Not tried with cPython.) So I think this warning is a bit excessive that makes everyone just put PYPY_IGNORE_MEMORY=1 in their make.conf. Just in my case. I'll disable the test for now and revise my estimation. Thanks for reporting back. Regards signature.asc Description: This is a digitally signed message part.
Warnings from make index
For the past several days, I've been getting the following. I haven't yet tracked down the commit that caused it. Generating INDEX-8 - please wait../usr/ports/Mk/bsd.pbi.mk, line 20: warning: duplicate script for target check-pbimanager ignored /usr/ports/Mk/bsd.pbi.mk, line 45: warning: duplicate script for target pbi-generate ignored /usr/ports/Mk/bsd.pbi.mk, line 46: warning: duplicate script for target pbi-generate ignored /usr/ports/Mk/bsd.pbi.mk, line 47: warning: duplicate script for target pbi-generate ignored /usr/ports/Mk/bsd.pbi.mk, line 50: warning: duplicate script for target clean-pbi ignored /usr/ports/Mk/bsd.pbi.mk, line 51: warning: duplicate script for target clean-pbi ignored -- Peter Jeremy pgpg1Zj0hykh0.pgp Description: PGP signature
Re: Warnings from make index
On 10 March 2013 19:22, Peter Jeremy pe...@rulingia.com wrote: For the past several days, I've been getting the following. I haven't yet tracked down the commit that caused it. Generating INDEX-8 - please wait../usr/ports/Mk/bsd.pbi.mk, line 20: warning: duplicate script for target check-pbimanager ignored /usr/ports/Mk/bsd.pbi.mk, line 45: warning: duplicate script for target pbi-generate ignored /usr/ports/Mk/bsd.pbi.mk, line 46: warning: duplicate script for target pbi-generate ignored /usr/ports/Mk/bsd.pbi.mk, line 47: warning: duplicate script for target pbi-generate ignored /usr/ports/Mk/bsd.pbi.mk, line 50: warning: duplicate script for target clean-pbi ignored /usr/ports/Mk/bsd.pbi.mk, line 51: warning: duplicate script for target clean-pbi ignored Well, the targets in bsd.pbi.mk should have been wrapped with .if !target, but this is showing that something is perhaps including bsd.port.pre.mk twice and somehow getting away with it, or that something is directly including bsd.pbi.mk in the port's Makefile. I've run make index with -dl, logging at [1]. It should at least provide the category of the troublesome port when it's finished. Chris [1] http://www.bayofrum.net/~crees/scratch/makeindexverbose.log ___ 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
CFT mplayer and mencoder snapshot
Hi folks, I have prepared a recent snapshot of mplayer and mencoder. The port itself has changed quite a bit, therefore testing and reporting (and patches if necessary) are greatly appreciated. The port tarballs can be found here: https://bsdistfiles.googlecode.com/files/m20130310.tar.xz Main changes: - Reduce the number of dependencies (use internal ffmpeg whenever possible) in mplayer - Do not build with clang on i386 - Use new options framework Happy testing Riggs ___ 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: [RFC] lang/pypy
Hi David, At Sun, 10 Mar 2013 21:18:12 +0300, David Naylor wrote: however my translation processes under -DPYPY_IGNORE_MEMORY take 2GB for normal binary and 2.5GB for sandboxed one so they aggregate 4.5GB to run parallel. This is good news. Could you please detail how you measured peak memory? I might need to retest the port. I heuristically measured them with top(1) RESources, amount of ZFS ARC and swap increased. Oh and free memory after one of translation process finised. I'm afraid I couldn't provide reproducible method for environments for others. I'll disable the test for now and revise my estimation. Thanks for reporting back. I wonder where so much difference of memory usage between yours and mine comes from. 5.5GB vs 2.5GB on the same platform (64bit/pypy) is not so negligible. -- Kuro poyop...@puripuri.plala.or.jp PS. like this, please. thanks for the offer. ___ 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
20130308 UPDATING: folks, libgee
I am mildly confused by the UPDATING warning on the repocopies for net-im/folks and devel/libgee. Is the intention that *everybody* should be using the repocopied versions? Will there be a point in the future where we switch back to the base ports? ___ 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: Warnings from make index
On 10 March 2013 19:49, Chris Rees cr...@freebsd.org wrote: On 10 March 2013 19:22, Peter Jeremy pe...@rulingia.com wrote: For the past several days, I've been getting the following. I haven't yet tracked down the commit that caused it. Generating INDEX-8 - please wait../usr/ports/Mk/bsd.pbi.mk, line 20: warning: duplicate script for target check-pbimanager ignored /usr/ports/Mk/bsd.pbi.mk, line 45: warning: duplicate script for target pbi-generate ignored /usr/ports/Mk/bsd.pbi.mk, line 46: warning: duplicate script for target pbi-generate ignored /usr/ports/Mk/bsd.pbi.mk, line 47: warning: duplicate script for target pbi-generate ignored /usr/ports/Mk/bsd.pbi.mk, line 50: warning: duplicate script for target clean-pbi ignored /usr/ports/Mk/bsd.pbi.mk, line 51: warning: duplicate script for target clean-pbi ignored Well, the targets in bsd.pbi.mk should have been wrapped with .if !target, but this is showing that something is perhaps including bsd.port.pre.mk twice and somehow getting away with it, or that something is directly including bsd.pbi.mk in the port's Makefile. I've run make index with -dl, logging at [1]. It should at least provide the category of the troublesome port when it's finished. Chris OK, found it. www/vtiger includes bsd.port.pre.mk AND bsd.port.mk; I've fixed that. This should error out, so someone somehow has broken that part of bsd.port.mk. Chris ___ 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
Installing empathy-2.32.2_3...warning: undefined reference
FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #36 r248127: Sun Mar 10 00:13:59 CST 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 Making install in src gmake[1]: Entering directory `/usr/ports/net-im/empathy/work/empathy-2.34.0/src' gmake install-am gmake[2]: Entering directory `/usr/ports/net-im/empathy/work/empathy-2.34.0/src' GEN/usr/local/include/gstreamer-0.10/gst/audio/audio-enumtypes.h CC empathy_av-empathy-audio-sink.o In file included from empathy-audio-sink.c:25: In file included from /usr/local/include/gstreamer-0.10/gst/audio/audio.h:26: In file included from /usr/local/include/gstreamer-0.10/gst/audio/multichannel.h:21: /usr/local/include/gstreamer-0.10/gst/audio/audio-enumtypes.h:4:11: warning: extra tokens at end of #ifndef directive [-Wextra-tokens] #ifndef __/USR/LOCAL/INCLUDE/GSTREAMER_0.10/GST/AUDIO/AUDIO_ENUM_TYPES_H__ ^ // /usr/local/include/gstreamer-0.10/gst/audio/audio-enumtypes.h:5:11: warning: ISO C99 requires whitespace after the macro name [-Wc99-extensions] #define __/USR/LOCAL/INCLUDE/GSTREAMER_0.10/GST/AUDIO/AUDIO_ENUM_TYPES_H__ ^ /usr/local/include/gstreamer-0.10/gst/audio/audio-enumtypes.h:12:9: error: macro names must be identifiers #define /USR/LOCAL/INCLUDE/GSTREAMER_TYPE_AUDIO_FORMAT (gst_audio_format_get_type()) ^ /usr/local/include/gstreamer-0.10/gst/audio/audio-enumtypes.h:14:9: error: macro names must be identifiers #define /USR/LOCAL/INCLUDE/GSTREAMER_TYPE_AUDIO_FORMAT_FLAGS (gst_audio_format_flags_get_type()) ^ /usr/local/include/gstreamer-0.10/gst/audio/audio-enumtypes.h:16:9: error: macro names must be identifiers #define /USR/LOCAL/INCLUDE/GSTREAMER_TYPE_AUDIO_FLAGS (gst_audio_flags_get_type()) ^ /usr/local/include/gstreamer-0.10/gst/audio/audio-enumtypes.h:18:9: error: macro names must be identifiers #define /USR/LOCAL/INCLUDE/GSTREAMER_TYPE_AUDIO_FIELD_FLAG (gst_audio_field_flag_get_type()) ^ empathy-audio-sink.c:160:27: warning: 'g_mutex_new' is deprecated [-Wdeprecated-declarations] priv-audio_bins_lock = g_mutex_new (); ^ /usr/local/include/glib-2.0/glib/deprecated/gthread.h:272:17: note: 'g_mutex_new' declared here GMutex *g_mutex_new (void); ^ empathy-audio-sink.c:257:5: warning: 'g_mutex_free' is deprecated [-Wdeprecated-declarations] g_mutex_free (priv-audio_bins_lock); ^ /usr/local/include/glib-2.0/glib/deprecated/gthread.h:274:17: note: 'g_mutex_free' declared here voidg_mutex_free(GMutex *mutex); ^ 4 warnings and 4 errors generated. gmake[2]: *** [empathy_av-empathy-audio-sink.o] Error 1 gmake[2]: Leaving directory `/usr/ports/net-im/empathy/work/empathy-2.34.0/src' gmake[1]: *** [install] Error 2 gmake[1]: Leaving directory `/usr/ports/net-im/empathy/work/empathy-2.34.0/src' gmake: *** [install-recursive] Error 1 *** [do-install] Error code 2 Stop in /usr/ports/net-im/empathy. *** [install] Error code 1 Stop in /usr/ports/net-im/empathy. *** [reinstall] Error code 1 Stop in /usr/ports/net-im/empathy. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20130310-63309-ggpcwf-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=empathy-2.32.2_3 UPGRADE_PORT_VER=2.32.2_3 make -DINSTALLS_DEPENDS reinstall --- Updating dependency info --- Restoring the old version Installing empathy-2.32.2_3...warning: undefined reference to schema id='org.gnome.desktop.default-applications.at'/ warning: undefined reference to schema id='org.gnome.Empathy.accounts'/ done --- Removing old package' ** Fix the installation problem and try again. --- Installation of net-im/empathy ended at: Sun, 10 Mar 2013 16:17:01 -0500 (consumed 00:00:08) --- Upgrade of net-im/empathy ended at: Sun, 10 Mar 2013 16:17:01 -0500 (consumed 00:03:55) --- ** Upgrade tasks 2: 1 done, 0 ignored, 0 skipped and 1 failed ___ 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: Installing empathy-2.32.2_3...warning: undefined reference
On 10-3-2013 22:29, AN wrote: FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #36 r248127: Sun Mar 10 00:13:59 CST 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 Thanks for the report, this is already known. Sadly I haven't managed to find a solution for this :/ -Koop Making install in src gmake[1]: Entering directory `/usr/ports/net-im/empathy/work/empathy-2.34.0/src' gmake install-am gmake[2]: Entering directory `/usr/ports/net-im/empathy/work/empathy-2.34.0/src' GEN /usr/local/include/gstreamer-0.10/gst/audio/audio-enumtypes.h CC empathy_av-empathy-audio-sink.o In file included from empathy-audio-sink.c:25: In file included from /usr/local/include/gstreamer-0.10/gst/audio/audio.h:26: In file included from /usr/local/include/gstreamer-0.10/gst/audio/multichannel.h:21: /usr/local/include/gstreamer-0.10/gst/audio/audio-enumtypes.h:4:11: warning: extra tokens at end of #ifndef directive [-Wextra-tokens] #ifndef __/USR/LOCAL/INCLUDE/GSTREAMER_0.10/GST/AUDIO/AUDIO_ENUM_TYPES_H__ ^ // /usr/local/include/gstreamer-0.10/gst/audio/audio-enumtypes.h:5:11: warning: ISO C99 requires whitespace after the macro name [-Wc99-extensions] #define __/USR/LOCAL/INCLUDE/GSTREAMER_0.10/GST/AUDIO/AUDIO_ENUM_TYPES_H__ ^ /usr/local/include/gstreamer-0.10/gst/audio/audio-enumtypes.h:12:9: error: macro names must be identifiers #define /USR/LOCAL/INCLUDE/GSTREAMER_TYPE_AUDIO_FORMAT (gst_audio_format_get_type()) ^ /usr/local/include/gstreamer-0.10/gst/audio/audio-enumtypes.h:14:9: error: macro names must be identifiers #define /USR/LOCAL/INCLUDE/GSTREAMER_TYPE_AUDIO_FORMAT_FLAGS (gst_audio_format_flags_get_type()) ^ /usr/local/include/gstreamer-0.10/gst/audio/audio-enumtypes.h:16:9: error: macro names must be identifiers #define /USR/LOCAL/INCLUDE/GSTREAMER_TYPE_AUDIO_FLAGS (gst_audio_flags_get_type()) ^ /usr/local/include/gstreamer-0.10/gst/audio/audio-enumtypes.h:18:9: error: macro names must be identifiers #define /USR/LOCAL/INCLUDE/GSTREAMER_TYPE_AUDIO_FIELD_FLAG (gst_audio_field_flag_get_type()) ^ empathy-audio-sink.c:160:27: warning: 'g_mutex_new' is deprecated [-Wdeprecated-declarations] priv-audio_bins_lock = g_mutex_new (); ^ /usr/local/include/glib-2.0/glib/deprecated/gthread.h:272:17: note: 'g_mutex_new' declared here GMutex *g_mutex_new (void); ^ empathy-audio-sink.c:257:5: warning: 'g_mutex_free' is deprecated [-Wdeprecated-declarations] g_mutex_free (priv-audio_bins_lock); ^ /usr/local/include/glib-2.0/glib/deprecated/gthread.h:274:17: note: 'g_mutex_free' declared here voidg_mutex_free(GMutex *mutex); ^ 4 warnings and 4 errors generated. gmake[2]: *** [empathy_av-empathy-audio-sink.o] Error 1 gmake[2]: Leaving directory `/usr/ports/net-im/empathy/work/empathy-2.34.0/src' gmake[1]: *** [install] Error 2 gmake[1]: Leaving directory `/usr/ports/net-im/empathy/work/empathy-2.34.0/src' gmake: *** [install-recursive] Error 1 *** [do-install] Error code 2 Stop in /usr/ports/net-im/empathy. *** [install] Error code 1 Stop in /usr/ports/net-im/empathy. *** [reinstall] Error code 1 Stop in /usr/ports/net-im/empathy. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20130310-63309-ggpcwf-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=empathy-2.32.2_3 UPGRADE_PORT_VER=2.32.2_3 make -DINSTALLS_DEPENDS reinstall --- Updating dependency info --- Restoring the old version Installing empathy-2.32.2_3...warning: undefined reference to schema id='org.gnome.desktop.default-applications.at'/ warning: undefined reference to schema id='org.gnome.Empathy.accounts'/ done --- Removing old package' ** Fix the installation problem and try again. --- Installation of net-im/empathy ended at: Sun, 10 Mar 2013 16:17:01 -0500 (consumed 00:00:08) --- Upgrade of net-im/empathy ended at: Sun, 10 Mar 2013 16:17:01 -0500 (consumed 00:03:55) --- ** Upgrade tasks 2: 1 done, 0 ignored, 0 skipped and 1 failed ___ 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
x11-toolkits/pango update to 1.30 fails to build
Posting this for the benefit of search engines and seekers. Following the most recent ports update to pango (svn 313633) I was unable to get it to build properly until I rebuilt cairo with this bit flipped: WITH GLIB Enable GObject Functions Feature A bunch of interdependent ports (glib gtk gobject-introspection etc) were were also rebuit, so I'm not sure what broke but it seems similar to what is described here: http://lists.freebsd.org/pipermail/freebsd-ports/2012-June/075519.html Regards ___ 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: Warnings from make index
On 3/10/2013 2:49 PM, Chris Rees wrote: On 10 March 2013 19:22, Peter Jeremy pe...@rulingia.com wrote: For the past several days, I've been getting the following. I haven't yet tracked down the commit that caused it. Generating INDEX-8 - please wait../usr/ports/Mk/bsd.pbi.mk, line 20: warning: duplicate script for target check-pbimanager ignored /usr/ports/Mk/bsd.pbi.mk, line 45: warning: duplicate script for target pbi-generate ignored /usr/ports/Mk/bsd.pbi.mk, line 46: warning: duplicate script for target pbi-generate ignored /usr/ports/Mk/bsd.pbi.mk, line 47: warning: duplicate script for target pbi-generate ignored /usr/ports/Mk/bsd.pbi.mk, line 50: warning: duplicate script for target clean-pbi ignored /usr/ports/Mk/bsd.pbi.mk, line 51: warning: duplicate script for target clean-pbi ignored Well, the targets in bsd.pbi.mk should have been wrapped with .if !target, but this is showing that something is perhaps including bsd.port.pre.mk twice and somehow getting away with it, or that something is directly including bsd.pbi.mk in the port's Makefile. ports/176825 should fix the bpm issue. Regards, Bryan signature.asc Description: OpenPGP digital signature
Re: lang/ruby19: ruby-1.9.3.392, 1 is vulnerable: ** [check-vulnerable] Error code 1
I try to compile port lang/ruby19 and I always get on a FreeBSD 9.1-STABLE box the following error message, which is obviously triggered by some port auditing - but I do not find the knob to switch it off. Can someone give a hint, please? This shouldn't be happening. Perhaps your portaudit data is out of date? Try portaudit -Fda as root. Steve ___ 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
