Re: Warnings from make index
On 2013-Mar-10 21:20:00 +, Chris Rees cr...@freebsd.org wrote: www/vtiger includes bsd.port.pre.mk AND bsd.port.mk; I've fixed that. Thanks for that. -- Peter Jeremy pgpv_TiGhwBCg.pgp Description: PGP signature
devel/lprof-devel build fail - libvigraimpex.so undefined reference
Hi Errors on build: [100%] Building CXX Object src/CMakefiles/lprof.dir/qrc_lprof.o Linking CXX executable lprof /usr/lib/libvigraimpex.so: undefined reference to '_ZNKSt5ctypeIcE13_M_widen_initEv@GLIBCXX_3.4.11' *** Error code 1 1 error *** Error Code 2 1 error *** Error Code 2 1 error *** Error code 1 Stop in /usr/ports/graphics/lprof-devel. Thanks in advance for any help with this David -- David Southwell ARPS AFIAP Photographic Arts Trained experienced competition judge, mentor, trainer, lecturer, Advanced digital techniques, international project photography ___ 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: [CFT] xorg 7.7
2013/3/11 Niclas Zeising zeis...@freebsd.org The FreeBSD xorg team (x11@) presents this update of the FreeBSD xorg port to version 7.7. This CFT is intended to weed out as many bugs and regressions as possible before merging xorg 7.7 into ports, please test it as much as possible, to make it as good as can be. We need testers of both new and old xorg, on as many architectures and hardware combinations as possible. Please report both successes and failures, and remember to include which architecture, graphics card, version of FreeBSD and compiler you are using, as well as relevant logs if any. This CFT and any updates can either be obtained using SVN from https://trillian.chruetertee.ch/svn/ports/branches/xorg-7.7 . Once this ports overlay is obtained, it is necessary to run the xorgmerge script, obtainable here: http://people.freebsd.org/~miwi/xorg/xorgmerge . Please don't forget to update directories before running this script. A patch against the ports tree is also available, and can be obtained from http://people.freebsd.org/~zeising/xorg-7.7.diff . Apply this using either svn patch /path/to/xorg-7.7.diff if your ports tree is managed by svn or patch -p0 -E /path/to/xorg-7.7.diff if your ports tree is managed by portsnap Remember -E, so that empty files are removed. This patch will be kept as up to date as possible, but might lag a little behind the SVN repository. Once the patch is in your ports tree, to build the old xorg, just cd to /usr/ports/x11/xorg and run make install. To get the new xorg, first set WITH_NEW_XORG in /etc/make.conf then proceed as above. Hopefully we will also be able to make packages and test images available for use, however, this is not done yet. A link for these packages and images will be posted in a follow-up mail. In this CFT: * xorg-server 1.12.4 (WITH_NEW_XORG) * Mesa 8.0.5 (WITH_NEW_XORG) * Updated dri * libX11 1.5 * libxcb 1.8 * updates for drivers * Updates for all other utilities and libraries Known issues: The issues with imake and makedepend requiring a gnu compatible cpp is not yet resolved. Hardware acceleration for certain ATI radeon cards might no longer work, if compiled with WITH_NEW_XORG. This is expected to be resolved once the work of porting TTM/KMS for radeon is completed. Thank you very much, thus people that have still old radeon cards such as 4xxx that does not need KMS can just go on with xorg without WITH_NEW_XORG set right? For more information see https://wiki.freebsd.org/Xorg or come visit us on IRC, #freebsd-xorg @ EFNet Best Regards Regards, -- Demelier David ___ 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: [CFT] xorg 7.7
2013/3/12 David Demelier demelier.da...@gmail.com 2013/3/11 Niclas Zeising zeis...@freebsd.org The FreeBSD xorg team (x11@) presents this update of the FreeBSD xorg port to version 7.7. This CFT is intended to weed out as many bugs and regressions as possible before merging xorg 7.7 into ports, please test it as much as possible, to make it as good as can be. We need testers of both new and old xorg, on as many architectures and hardware combinations as possible. Please report both successes and failures, and remember to include which architecture, graphics card, version of FreeBSD and compiler you are using, as well as relevant logs if any. This CFT and any updates can either be obtained using SVN from https://trillian.chruetertee.ch/svn/ports/branches/xorg-7.7 . Once this ports overlay is obtained, it is necessary to run the xorgmerge script, obtainable here: http://people.freebsd.org/~miwi/xorg/xorgmerge . Please don't forget to update directories before running this script. A patch against the ports tree is also available, and can be obtained from http://people.freebsd.org/~zeising/xorg-7.7.diff . Apply this using either svn patch /path/to/xorg-7.7.diff if your ports tree is managed by svn or patch -p0 -E /path/to/xorg-7.7.diff if your ports tree is managed by portsnap Remember -E, so that empty files are removed. This patch will be kept as up to date as possible, but might lag a little behind the SVN repository. Once the patch is in your ports tree, to build the old xorg, just cd to /usr/ports/x11/xorg and run make install. To get the new xorg, first set WITH_NEW_XORG in /etc/make.conf then proceed as above. Hopefully we will also be able to make packages and test images available for use, however, this is not done yet. A link for these packages and images will be posted in a follow-up mail. In this CFT: * xorg-server 1.12.4 (WITH_NEW_XORG) * Mesa 8.0.5 (WITH_NEW_XORG) * Updated dri * libX11 1.5 * libxcb 1.8 * updates for drivers * Updates for all other utilities and libraries Known issues: The issues with imake and makedepend requiring a gnu compatible cpp is not yet resolved. Hardware acceleration for certain ATI radeon cards might no longer work, if compiled with WITH_NEW_XORG. This is expected to be resolved once the work of porting TTM/KMS for radeon is completed. Thank you very much, thus people that have still old radeon cards such as 4xxx that does not need KMS can just go on with xorg without WITH_NEW_XORG set right? You probably could also modify radeon port, add --disable-kms and rebuild it, all should be fine. I'll come up in near days with prebuilt images with all these stuff, to test it easily. For more information see https://wiki.freebsd.org/Xorg or come visit us on IRC, #freebsd-xorg @ EFNet Best Regards Regards, -- Demelier David ___ 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 -- Regards, Alexander Yerenkow ___ 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: [CFT] xorg 7.7
On 03/12/13 11:32, David Demelier wrote: Thank you very much, thus people that have still old radeon cards such as 4xxx that does not need KMS can just go on with xorg without WITH_NEW_XORG set right? Regards, Yes, it should work. I am running with an ATI Radeon HD4850 without problem. The only caveat is that you might not get hardware acceleration, for that TTM/KMS is probably needed, even for older graphics cards. It works fine anyway, at least for regular desktop work. Regards! -- Niclas Zeising ___ 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: [CFT] xorg 7.7
On 03/12/13 11:43, Alexander Yerenkow wrote: You probably could also modify radeon port, add --disable-kms and rebuild it, all should be fine. I'll come up in near days with prebuilt images with all these stuff, to test it easily. This is already done, it is in the patch. Regards! -- Niclas Zeising ___ 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 patch
Em Seg, 2013-03-11 às 10:28 +0100, Ferenc Balku escreveu: Hi Sergio! Awfully sorry to disturb You, but I have found this link via Google http://lists.freebsd.org/pipermail/freebsd-ports/2013-March/081979.html and can not find the patch to download a make VBox work again on our FBSD10 test server. Can You please send me a link to download the patch. Thanks in advance, Best Regards Ferenc Balku No problem I was travel business... here is the patch, the list does not allow attach files... go to the /usr/ports/emulators/virtualbox-ose-kmod, put the fix in the files directory with a name like == patch-the-freebsd-kernel and do a make clean install == --- src/VBox/Runtime/r0drv/freebsd/the-freebsd-kernel.h.orig 2012-12-19 16:27:29.0 -0200 +++ src/VBox/Runtime/r0drv/freebsd/the-freebsd-kernel.h 2013-03-09 14:42:18.924039639 -0300 @@ -50,6 +50,7 @@ #include sys/unistd.h #include sys/kthread.h #include sys/lock.h +#include sys/rwlock.h #include sys/mutex.h #include sys/sched.h #include sys/callout.h @@ -70,6 +71,12 @@ #include sys/resourcevar.h #include machine/cpu.h +/* + fix VM_OBJ_LOCK +*/ +#defineVM_OBJECT_LOCK(o) VM_OBJECT_RLOCK(o) +#defineVM_OBJECT_UNLOCK(o) VM_OBJECT_RUNLOCK(o) + /** * Wrappers around the sleepq_ KPI. */ === ___ 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: [CFT] xorg 7.7
On 03/11/13 22:50, Niclas Zeising wrote: The FreeBSD xorg team (x11@) presents this update of the FreeBSD xorg port to version 7.7. I'd like to state that I've been using this xorg version from the xorg development repo on my laptop in conjunction with the KMS intel driver with quite good success on CURRENT, so this is a success report from me. Thanks for the good work to all involved parties! -- Guido Falsi m...@madpilot.net ___ 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 +-+ devel/gecode| 3.7.3 | 4.0.0 +-+ irc/thales | 1.0 | 1.1.1 +-+ 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: VirtualBox patch
On Tue, Mar 12, 2013 at 09:01:43AM -0300, Sergio de Almeida Lenzi wrote: Em Seg, 2013-03-11 ??s 10:28 +0100, Ferenc Balku escreveu: Hi Sergio! Awfully sorry to disturb You, but I have found this link via Google http://lists.freebsd.org/pipermail/freebsd-ports/2013-March/081979.html and can not find the patch to download a make VBox work again on our FBSD10 test server. Can You please send me a link to download the patch. Thanks in advance, Best Regards Ferenc Balku No problem I was travel business... here is the patch, the list does not allow attach files... go to the /usr/ports/emulators/virtualbox-ose-kmod, put the fix in the files directory with a name like == patch-the-freebsd-kernel and do a make clean install == --- src/VBox/Runtime/r0drv/freebsd/the-freebsd-kernel.h.orig 2012-12-19 16:27:29.0 -0200 +++ src/VBox/Runtime/r0drv/freebsd/the-freebsd-kernel.h 2013-03-09 14:42:18.924039639 -0300 @@ -50,6 +50,7 @@ #include sys/unistd.h #include sys/kthread.h #include sys/lock.h +#include sys/rwlock.h #include sys/mutex.h #include sys/sched.h #include sys/callout.h @@ -70,6 +71,12 @@ #include sys/resourcevar.h #include machine/cpu.h +/* + fix VM_OBJ_LOCK +*/ +#defineVM_OBJECT_LOCK(o) VM_OBJECT_RLOCK(o) +#defineVM_OBJECT_UNLOCK(o) VM_OBJECT_RUNLOCK(o) This is definitely wrong. For the blind substitution, you should use VM_OBJECT_WLOCK/VM_OBJECT_WUNLOCK. pgpKwtPIFBhK3.pgp Description: PGP signature
Re: VirtualBox patch
On Tue, Mar 12, 2013 at 4:17 PM, Konstantin Belousov kostik...@gmail.com wrote: On Tue, Mar 12, 2013 at 09:01:43AM -0300, Sergio de Almeida Lenzi wrote: Em Seg, 2013-03-11 ??s 10:28 +0100, Ferenc Balku escreveu: Hi Sergio! Awfully sorry to disturb You, but I have found this link via Google http://lists.freebsd.org/pipermail/freebsd-ports/2013-March/081979.html and can not find the patch to download a make VBox work again on our FBSD10 test server. Can You please send me a link to download the patch. Thanks in advance, Best Regards Ferenc Balku No problem I was travel business... here is the patch, the list does not allow attach files... go to the /usr/ports/emulators/virtualbox-ose-kmod, put the fix in the files directory with a name like == patch-the-freebsd-kernel and do a make clean install == --- src/VBox/Runtime/r0drv/freebsd/the-freebsd-kernel.h.orig 2012-12-19 16:27:29.0 -0200 +++ src/VBox/Runtime/r0drv/freebsd/the-freebsd-kernel.h 2013-03-09 14:42:18.924039639 -0300 @@ -50,6 +50,7 @@ #include sys/unistd.h #include sys/kthread.h #include sys/lock.h +#include sys/rwlock.h #include sys/mutex.h #include sys/sched.h #include sys/callout.h @@ -70,6 +71,12 @@ #include sys/resourcevar.h #include machine/cpu.h +/* + fix VM_OBJ_LOCK +*/ +#defineVM_OBJECT_LOCK(o) VM_OBJECT_RLOCK(o) +#defineVM_OBJECT_UNLOCK(o) VM_OBJECT_RUNLOCK(o) This is definitely wrong. For the blind substitution, you should use VM_OBJECT_WLOCK/VM_OBJECT_WUNLOCK. It would be great if someone could come up with a proper patch. All I've seen so far looks wrong or hackish and I cannot add that to the port nor send it upstream to get it fixed for future releases. -- Bernhard Froehlich http://www.bluelife.at/ ___ 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
net-im/telepathy-haze update fails
I've been having issues updating net-im/telepathy-haze on amd64 10-CURRENT r247527. Pasted below is the log from `portmaster --no-confirm -wGD net-im/telepathy-haze`: ]0;portmaster: telepathy-haze-0.4.0_5 === Currently installed version: telepathy-haze-0.4.0_5 === Port directory: /usr/ports/net-im/telepathy-haze === Launching 'make checksum' for net-im/telepathy-haze in background === Gathering dependency list for net-im/telepathy-haze from ports === Initial dependency check complete for net-im/telepathy-haze ]0;portmaster: telepathy-haze-0.4.0_5 === Starting build for net-im/telepathy-haze === === All dependencies are up to date === Cleaning for telepathy-haze-0.6.0 === telepathy-haze-0.6.0 depends on file: /usr/local/sbin/pkg - found === Extracting for telepathy-haze-0.6.0 = SHA256 Checksum OK for telepathy-haze-0.6.0.tar.gz. === Patching for telepathy-haze-0.6.0 === telepathy-haze-0.6.0 depends on executable: xsltproc - found === telepathy-haze-0.6.0 depends on executable: gmake - found === telepathy-haze-0.6.0 depends on shared library: purple - found === telepathy-haze-0.6.0 depends on shared library: idn - found === telepathy-haze-0.6.0 depends on shared library: telepathy-glib - found === Configuring for telepathy-haze-0.6.0 === FreeBSD 10 autotools fix applied to /usr/ports/net-im/telepathy-haze/work/telepathy-haze-0.6.0/configure === FreeBSD 10 autotools fix applied to /usr/ports/net-im/telepathy-haze/work/telepathy-haze-0.6.0/m4/libtool.m4 === FreeBSD 10 autotools fix applied to /usr/ports/net-im/telepathy-haze/work/telepathy-haze-0.6.0/aclocal.m4 cd: /usr/ports/net-im/telepathy-haze/work/telepathy-telepathy-haze-0.6.0: No such file or directory env: ./configure: No such file or directory === Script configure failed unexpectedly. Please report the problem to gn...@freebsd.org [maintainer] and attach the /usr/ports/net-im/telepathy-haze/work/telepathy-telepathy-haze-0.6.0/config.log including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. a /usr/local/sbin/pkg info -g -Ea). *** [do-configure] Error code 1 Stop in /usr/ports/net-im/telepathy-haze. === make failed for net-im/telepathy-haze === Aborting update Terminated === You can restart from the point of failure with this command line: portmaster flags net-im/telepathy-haze Thanks, Shawn ___ 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: net-im/telepathy-haze update fails
On Tue, Mar 12, 2013 at 11:28 AM, Shawn Webb latt...@gmail.com wrote:
I've been having issues updating net-im/telepathy-haze on amd64
10-CURRENT r247527. Pasted below is the log from `portmaster --no-confirm
-wGD net-im/telepathy-haze`:
]0;portmaster: telepathy-haze-0.4.0_5
=== Currently installed version: telepathy-haze-0.4.0_5
=== Port directory: /usr/ports/net-im/telepathy-haze
=== Launching 'make checksum' for net-im/telepathy-haze in background
=== Gathering dependency list for net-im/telepathy-haze from ports
=== Initial dependency check complete for net-im/telepathy-haze
]0;portmaster: telepathy-haze-0.4.0_5
=== Starting build for net-im/telepathy-haze ===
=== All dependencies are up to date
=== Cleaning for telepathy-haze-0.6.0
=== telepathy-haze-0.6.0 depends on file: /usr/local/sbin/pkg - found
=== Extracting for telepathy-haze-0.6.0
= SHA256 Checksum OK for telepathy-haze-0.6.0.tar.gz.
=== Patching for telepathy-haze-0.6.0
=== telepathy-haze-0.6.0 depends on executable: xsltproc - found
=== telepathy-haze-0.6.0 depends on executable: gmake - found
=== telepathy-haze-0.6.0 depends on shared library: purple - found
=== telepathy-haze-0.6.0 depends on shared library: idn - found
=== telepathy-haze-0.6.0 depends on shared library: telepathy-glib -
found
=== Configuring for telepathy-haze-0.6.0
=== FreeBSD 10 autotools fix applied to
/usr/ports/net-im/telepathy-haze/work/telepathy-haze-0.6.0/configure
=== FreeBSD 10 autotools fix applied to
/usr/ports/net-im/telepathy-haze/work/telepathy-haze-0.6.0/m4/libtool.m4
=== FreeBSD 10 autotools fix applied to
/usr/ports/net-im/telepathy-haze/work/telepathy-haze-0.6.0/aclocal.m4
cd: /usr/ports/net-im/telepathy-haze/work/telepathy-telepathy-haze-0.6.0:
No such file or directory
env: ./configure: No such file or directory
The problem seems to be the extra 'telepathy-', try commenting out
WRKSRC= ${WRKDIR}/telepathy-${PORTNAME}-${DISTVERSION}
in the ports Makefile.
--
DISCLAIMER:
No electrons were maimed while sending this message. Only slightly bruised.
___
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: net-im/telepathy-haze update fails
On Tue, Mar 12, 2013 at 1:11 PM, Scot Hetzel swhet...@gmail.com wrote:
On Tue, Mar 12, 2013 at 11:28 AM, Shawn Webb latt...@gmail.com wrote:
I've been having issues updating net-im/telepathy-haze on amd64
10-CURRENT r247527. Pasted below is the log from `portmaster --no-confirm
-wGD net-im/telepathy-haze`:
]0;portmaster: telepathy-haze-0.4.0_5
=== Currently installed version: telepathy-haze-0.4.0_5
=== Port directory: /usr/ports/net-im/telepathy-haze
=== Launching 'make checksum' for net-im/telepathy-haze in background
=== Gathering dependency list for net-im/telepathy-haze from ports
=== Initial dependency check complete for net-im/telepathy-haze
]0;portmaster: telepathy-haze-0.4.0_5
=== Starting build for net-im/telepathy-haze ===
=== All dependencies are up to date
=== Cleaning for telepathy-haze-0.6.0
=== telepathy-haze-0.6.0 depends on file: /usr/local/sbin/pkg - found
=== Extracting for telepathy-haze-0.6.0
= SHA256 Checksum OK for telepathy-haze-0.6.0.tar.gz.
=== Patching for telepathy-haze-0.6.0
=== telepathy-haze-0.6.0 depends on executable: xsltproc - found
=== telepathy-haze-0.6.0 depends on executable: gmake - found
=== telepathy-haze-0.6.0 depends on shared library: purple - found
=== telepathy-haze-0.6.0 depends on shared library: idn - found
=== telepathy-haze-0.6.0 depends on shared library: telepathy-glib -
found
=== Configuring for telepathy-haze-0.6.0
=== FreeBSD 10 autotools fix applied to
/usr/ports/net-im/telepathy-haze/work/telepathy-haze-0.6.0/configure
=== FreeBSD 10 autotools fix applied to
/usr/ports/net-im/telepathy-haze/work/telepathy-haze-0.6.0/m4/libtool.m4
=== FreeBSD 10 autotools fix applied to
/usr/ports/net-im/telepathy-haze/work/telepathy-haze-0.6.0/aclocal.m4
cd: /usr/ports/net-im/telepathy-haze/work/telepathy-telepathy-haze-0.6.0:
No such file or directory
env: ./configure: No such file or directory
The problem seems to be the extra 'telepathy-', try commenting out
WRKSRC= ${WRKDIR}/telepathy-${PORTNAME}-${DISTVERSION}
in the ports Makefile.
That worked. 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: net-im/telepathy-haze update fails
On 12-3-2013 18:14, Shawn Webb wrote:
On Tue, Mar 12, 2013 at 1:11 PM, Scot Hetzel swhet...@gmail.com wrote:
On Tue, Mar 12, 2013 at 11:28 AM, Shawn Webb latt...@gmail.com wrote:
I've been having issues updating net-im/telepathy-haze on amd64
10-CURRENT r247527. Pasted below is the log from `portmaster --no-confirm
-wGD net-im/telepathy-haze`:
]0;portmaster: telepathy-haze-0.4.0_5
=== Currently installed version: telepathy-haze-0.4.0_5
=== Port directory: /usr/ports/net-im/telepathy-haze
=== Launching 'make checksum' for net-im/telepathy-haze in background
=== Gathering dependency list for net-im/telepathy-haze from ports
=== Initial dependency check complete for net-im/telepathy-haze
]0;portmaster: telepathy-haze-0.4.0_5
=== Starting build for net-im/telepathy-haze ===
=== All dependencies are up to date
=== Cleaning for telepathy-haze-0.6.0
=== telepathy-haze-0.6.0 depends on file: /usr/local/sbin/pkg - found
=== Extracting for telepathy-haze-0.6.0
= SHA256 Checksum OK for telepathy-haze-0.6.0.tar.gz.
=== Patching for telepathy-haze-0.6.0
=== telepathy-haze-0.6.0 depends on executable: xsltproc - found
=== telepathy-haze-0.6.0 depends on executable: gmake - found
=== telepathy-haze-0.6.0 depends on shared library: purple - found
=== telepathy-haze-0.6.0 depends on shared library: idn - found
=== telepathy-haze-0.6.0 depends on shared library: telepathy-glib -
found
=== Configuring for telepathy-haze-0.6.0
=== FreeBSD 10 autotools fix applied to
/usr/ports/net-im/telepathy-haze/work/telepathy-haze-0.6.0/configure
=== FreeBSD 10 autotools fix applied to
/usr/ports/net-im/telepathy-haze/work/telepathy-haze-0.6.0/m4/libtool.m4
=== FreeBSD 10 autotools fix applied to
/usr/ports/net-im/telepathy-haze/work/telepathy-haze-0.6.0/aclocal.m4
cd: /usr/ports/net-im/telepathy-haze/work/telepathy-telepathy-haze-0.6.0:
No such file or directory
env: ./configure: No such file or directory
The problem seems to be the extra 'telepathy-', try commenting out
WRKSRC= ${WRKDIR}/telepathy-${PORTNAME}-${DISTVERSION}
in the ports Makefile.
That worked. Thanks!
And fixed in ports, thanks for reporting!
___
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 patch
Em Ter, 2013-03-12 às 17:17 +0200, Konstantin Belousov escreveu: On Tue, Mar 12, 2013 at 09:01:43AM -0300, Sergio de Almeida Lenzi wrote: Em Seg, 2013-03-11 ??s 10:28 +0100, Ferenc Balku escreveu: Hi Sergio! Awfully sorry to disturb You, but I have found this link via Google http://lists.freebsd.org/pipermail/freebsd-ports/2013-March/081979.html and can not find the patch to download a make VBox work again on our FBSD10 test server. Can You please send me a link to download the patch. Thanks in advance, Best Regards Ferenc Balku No problem I was travel business... here is the patch, the list does not allow attach files... go to the /usr/ports/emulators/virtualbox-ose-kmod, put the fix in the files directory with a name like == patch-the-freebsd-kernel and do a make clean install == --- src/VBox/Runtime/r0drv/freebsd/the-freebsd-kernel.h.orig 2012-12-19 16:27:29.0 -0200 +++ src/VBox/Runtime/r0drv/freebsd/the-freebsd-kernel.h 2013-03-09 14:42:18.924039639 -0300 @@ -50,6 +50,7 @@ #include sys/unistd.h #include sys/kthread.h #include sys/lock.h +#include sys/rwlock.h #include sys/mutex.h #include sys/sched.h #include sys/callout.h @@ -70,6 +71,12 @@ #include sys/resourcevar.h #include machine/cpu.h +/* + fix VM_OBJ_LOCK +*/ +#defineVM_OBJECT_LOCK(o) VM_OBJECT_RLOCK(o) +#defineVM_OBJECT_UNLOCK(o) VM_OBJECT_RUNLOCK(o) This is definitely wrong. For the blind substitution, you should use VM_OBJECT_WLOCK/VM_OBJECT_WUNLOCK. Ok, you are the guru, I just wanted the virtualbox to have it work asap... I will test this (with WLOCK/WUNLOCK) at once... Thanks for th information ___ 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 patch
On Tue, Mar 12, 2013 at 04:58:34PM +0100, Bernhard Fr?hlich wrote: On Tue, Mar 12, 2013 at 4:17 PM, Konstantin Belousov kostik...@gmail.com wrote: On Tue, Mar 12, 2013 at 09:01:43AM -0300, Sergio de Almeida Lenzi wrote: Em Seg, 2013-03-11 ??s 10:28 +0100, Ferenc Balku escreveu: Hi Sergio! Awfully sorry to disturb You, but I have found this link via Google http://lists.freebsd.org/pipermail/freebsd-ports/2013-March/081979.html and can not find the patch to download a make VBox work again on our FBSD10 test server. Can You please send me a link to download the patch. Thanks in advance, Best Regards Ferenc Balku No problem I was travel business... here is the patch, the list does not allow attach files... go to the /usr/ports/emulators/virtualbox-ose-kmod, put the fix in the files directory with a name like == patch-the-freebsd-kernel and do a make clean install == --- src/VBox/Runtime/r0drv/freebsd/the-freebsd-kernel.h.orig 2012-12-19 16:27:29.0 -0200 +++ src/VBox/Runtime/r0drv/freebsd/the-freebsd-kernel.h 2013-03-09 14:42:18.924039639 -0300 @@ -50,6 +50,7 @@ #include sys/unistd.h #include sys/kthread.h #include sys/lock.h +#include sys/rwlock.h #include sys/mutex.h #include sys/sched.h #include sys/callout.h @@ -70,6 +71,12 @@ #include sys/resourcevar.h #include machine/cpu.h +/* + fix VM_OBJ_LOCK +*/ +#defineVM_OBJECT_LOCK(o) VM_OBJECT_RLOCK(o) +#defineVM_OBJECT_UNLOCK(o) VM_OBJECT_RUNLOCK(o) This is definitely wrong. For the blind substitution, you should use VM_OBJECT_WLOCK/VM_OBJECT_WUNLOCK. It would be great if someone could come up with a proper patch. All I've seen so far looks wrong or hackish and I cannot add that to the port nor send it upstream to get it fixed for future releases. The patch would be to replace all occurences of VM_OBJECT_LOCK with VM_OBJECT_WLOCK, and VM_OBJECT_UNLOCK with VM_OBJECT_WUNLOCK. I assume that vbox module does not assert the lock state. Sorry, I am not set up to produce the patch, but it should just a mechanical substitution. pgpGWYQuAP85V.pgp Description: PGP signature
Re: VirtualBox patch, defininive???
Hello Thanks to Konstantin Belousov kostik...@gmail.com a substitution from RLOCK with WLOCK is the correct way, so a new fix is necessary... go to the /usr/ports/emulators/virtualbox-ose-kmod, put the fix in the files directory with a name like == patch-the-freebsd-kernel and do a make clean install == --- src/VBox/Runtime/r0drv/freebsd/the-freebsd-kernel.h.orig 2012-12-19 16:27:29.0 -0200 +++ src/VBox/Runtime/r0drv/freebsd/the-freebsd-kernel.h 2013-03-09 14:42:18.924039639 -0300 @@ -50,6 +50,7 @@ #include sys/unistd.h #include sys/kthread.h #include sys/lock.h +#include sys/rwlock.h #include sys/mutex.h #include sys/sched.h #include sys/callout.h @@ -70,6 +71,12 @@ #include sys/resourcevar.h #include machine/cpu.h +/* + fix VM_OBJ_LOCK +*/ +#defineVM_OBJECT_LOCK(o) VM_OBJECT_WLOCK(o) +#defineVM_OBJECT_UNLOCK(o) VM_OBJECT_WUNLOCK(o) + /** * Wrappers around the sleepq_ KPI. */ === ___ 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
Issue with egroupware install
Hi, The install is nice enough, however, since everyone is on Apache 2.2 and later now, there's a few things missing in the on-screen notes after the install: It already says this: == POST-INSTALL CONFIGURATION FOR eGroupware Make sure in your php.ini session.save_path='/tmp' is writable upload_max_filesize = 8M 1) Create a user and a database for eGroupware to store all its tables in (or choose an existing database). It doesn't matter what the database or user names are, as this will be configured in a later step. 2) Add the following to your Apache configuration, and restart the server: ### Add the AcceptPathInfo directive only for Apache 2.0.30 or later. Alias /eg /usr/local/www/eg/ AcceptPathInfo On Directory /usr/local/www/eg AllowOverride None Order Allow,Deny Allow from all /Directory Directory /usr/local/www/egdata AllowOverride None Order Allow,Deny Deny from all /Directory 3) Visit your eGroupware site with a browser (i.e., http://your.server.com/eg/), and you should be taken to the install.php script, which will lead you through creating a config file and then setting up eGroupware, creating an admin account, etc. 4) When you come to the setup page,please set the files' and backup's full path with: /usr/local/www/egdata/files /usr/local/www/egdata/backup In step #2, there should be several other things added to the httpd.conf for Apache to work right without pain. It would be better to have this: 2) Add the following to your Apache configuration, and restart the server: In the section for IfModule dir_module, change: DirectoryIndex index.html to: DirectoryInex index.php index.html ### Add the AcceptPathInfo directive only for Apache 2.0.30 or later. In the Alias section, add: Alias /eg /usr/local/www/eg/ AcceptPathInfo On In the Directory section, after the complete Directory path/apache22/cgi-bin snip /Directory? Add: Directory /usr/local/www/eg AllowOverride None Order Allow,Deny Allow from all /Directory Directory /usr/local/www/egdata AllowOverride None Order Allow,Deny Deny from all /Directory In the IfModule mime_module section, After: AddType application/x-compress .Z AddType application/x-gzip .gz .tgz Add: AddType application/x-httpd-php .php AddType application/x-httpd-php-source .phps Just helpin' P. ___ 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: devel/lprof-devel build fail - libvigraimpex.so undefined reference
* David Southwell (da...@vizion2000.net) wrote: Errors on build: [100%] Building CXX Object src/CMakefiles/lprof.dir/qrc_lprof.o Linking CXX executable lprof /usr/lib/libvigraimpex.so: undefined reference to '_ZNKSt5ctypeIcE13_M_widen_initEv@GLIBCXX_3.4.11' *** Error code 1 1 error *** Error Code 2 1 error *** Error Code 2 1 error *** Error code 1 Stop in /usr/ports/graphics/lprof-devel. Thanks in advance for any help with this This really is a result of us sticking with a rotten gcc in the base system for so long. And I expect more and more similar breakages to follow. Here, graphics/vigra uses gcc46 (since r307701) to build, and combiled vigra library depends code only present in libstdc++ from gcc46 (and not in libstdc++ in our base system). To compile lprof, adding USE_GCC=4.6+ to it's Makefile would be enough, however it won't run: % lprof /usr/lib/libstdc++.so.6: version GLIBCXX_3.4.11 required by /usr/local/lib/libvigraimpex.so.4 not found To fix that, one needs to add LD_LIBRARY_PATH=/usr/local/lib/gcc46 into environement. The same thing will be required for all vigra consumers. If gcc46 is optional for vigra, the problem may be temporary fixed by reverting r307701 (fluffy@?), however there will be more and more software depending on newer libstdc++, and we need a way to address that until all supported FreeBSD releases have switched to clang and new c++ stack. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.ru ___ 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: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found
On Mon, Mar 11, 2013 at 02:18:51PM -0700, Steve Kargl wrote: On Mon, Mar 11, 2013 at 10:05:47PM +0100, Dimitry Andric wrote: On 2013-03-11 20:00, Jan Beich wrote: Dimitry Andric d...@freebsd.org writes: $ echo 'sub/foo.barx' | grep sub/foo.bar $ echo $? 1 $ echo 'sub/foo.barx' | env -i grep sub/foo.bar $ echo 'sub/foolbarx' | env -i grep sub/foo.bar $ echo 'sub/foo.barx' | env -i grep 'sub/foo\.bar' sub/foo.barx $ echo 'sub/foo.barx' | env -i grep -o sub/foo.bar sub/foo.bar $ echo 'sub/foo.barx' | env -i grep --color=no sub/foo.bar sub/foo.barx A buggy shortcut? No, after some digging in and debugging of the bsdgrep code, I found out it is a regression caused by r246917, which is a fix for bin/175213: [patch] bsdgrep(1) segfaults upon malicious input. If you revert it, bsdgrep starts working correctly again. First, I can report that bootstrapping gcc-4.8.0 works if I use gnugrep instead of bsdgrep. The above explains why I had previously seen the failure as I was using an older bsdgrep. Second, an apology is owed to the clang gang as I attributed the problem to clang as it showed up on my system after converted everything over to clang. I think it would be best to back out r246917 for now, until the regression can be fixed properly. Having bsdgrep crash is bad, but not returning any results while it should is even worse... I tend to agree with your assessment that r246817 should be reverted, because I hit this issue in configure scripts and there is a large amount of software that uses autotool for configuration. Sorry about this, I will revert it and revisit the problem. I've been using bsdgrep by default for a while and somehow haven't run into this. -Mark ___ 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: Port deprecation reason ``Does not work with Ruby 1.9'' -- what should I do?
On 3/11/2013 4:13 PM, Lev Serebryakov wrote: Hello, Ports. My port (devel/ruby-subversion) is marked for deletion in 2 months because `` Does not work with Ruby 1.9''. What should I do? To be honest, I know nothing about Ruby and this port is part of official subversion distribution. Only thing I could do is to check that it builds and pass make tests. Why port is marked for deletion? Is ruby 1.8 deprecated and removed? Why can't port be for ruby 1.8 only? I believe 1.8 is EOL in June. http://www.ruby-lang.org/en/news/2011/10/06/plans-for-1-8-7/ I can't find anything more recent confirming this though. Yep, that's correct as far as I know. Only tyhing I could do right now -- ask upstream is ruby 1.9 support planned for future releases, but I can not influence upstream to provide (or doesn't provide) such support and I cannot hack sources to make it support ruby 1.9 :( Just out of curiosity, I did a search and found this: http://subversion.tigris.org/issues/show_bug.cgi?id=4083 So perhaps it's fixable. 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
[HEADS UP] Bryan Drewery joins portmgr@
I am pleased to announce that Bryan Drewery, aka bdrewery@, has accepted the gauntlet to work on the FreeBSD Ports Management Team. Bryan first stepped into fray when he first took over portupgrade, then added portmaster to his portfolio, and then joined in with the pkgng devs. He has also been instrutmental in working on poudiere development, an alternative build environment to tinderbox. Please join me in welcoming Bryan to the team. Thomas on behalf of portmgr@ ___ 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: 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 3/10/2013 6:44 AM, O. Hartmann wrote: 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 I have just committed a fix to the ports tree for this. -- Regards, Bryan Drewery bdrewery@freenode/EFNet signature.asc Description: OpenPGP digital signature
fail2ban install issue
Hi, I have read good things about fail2ban, and I would love to install it! I am sorry to trouble you if I am doing something dumb. My server is freebsd-9.1-release, I've updated my ports tree. I get this error when I go to install from ports: root@jupiter:/usr/ports/security/py-fail2ban # uname -aFreeBSD jupiter.my.domain 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243826: Tue Dec 4 06:55:39 UTC 2012 r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386root@jupiter:/usr/ports/security/py-fail2ban # make install clean=== License GPLv2 accepted by the user=== py27-fail2ban-0.8.8_1 depends on file: /usr/local/sbin/pkg - found= fail2ban-fail2ban-0.8.8-0-g51a3be2.tar.gz doesn't seem to exist in /usr/ports/distfiles/.= Attempting to fetch https://github.com/fail2ban/fail2ban/tarball/0.8.8/fail2ban-fail2ban-0.8.8-0-g51a3be2.tar.gzInitializing download: https://github.com/fail2ban/fail2ban/tarball/0.8.8/fail2ban-fail2ban-0.8.8-0-g51a3be2.tar.gzToo many redirects. = Attempting to fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/fail2ban-fail2ban-0.8.8-0-g51a3be2.tar.gzInitializing download: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/fail2ban-fail2ban-0.8.8-0-g51a3be2.tar.gzFile not found. = Couldn't fetch it - please try to retrieve this= port manually into /usr/ports/distfiles/ and try again.*** [do-fetch] Error code 1 Stop in /usr/ports/security/py-fail2ban.root@jupiter:/usr/ports/security/py-fail2ban # If you could point me in the right direction, I would be grateful! Regards,Don Wheeler ___ 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: fail2ban install issue
I just test, it works well. Maybe the problem was solved the time for you to write this email :) Le 12/03/2013 22:21, Donald Wheeler a écrit : Hi, I have read good things about fail2ban, and I would love to install it! I am sorry to trouble you if I am doing something dumb. My server is freebsd-9.1-release, I've updated my ports tree. I get this error when I go to install from ports: root@jupiter:/usr/ports/security/py-fail2ban # uname -aFreeBSD jupiter.my.domain 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243826: Tue Dec 4 06:55:39 UTC 2012 r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386root@jupiter:/usr/ports/security/py-fail2ban # make install clean=== License GPLv2 accepted by the user=== py27-fail2ban-0.8.8_1 depends on file: /usr/local/sbin/pkg - found= fail2ban-fail2ban-0.8.8-0-g51a3be2.tar.gz doesn't seem to exist in /usr/ports/distfiles/.= Attempting to fetch https://github.com/fail2ban/fail2ban/tarball/0.8.8/fail2ban-fail2ban-0.8.8-0-g51a3be2.tar.gzInitializing download: https://github.com/fail2ban/fail2ban/tarball/0.8.8/fail2ban-fail2ban-0.8.8-0-g51a3be2.tar.gzToo many redirects. = Attempting to fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/fail2ban-fail2ban-0.8.8-0-g51a3be2.tar.gzInitializing download: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/fail2ban-fail2ban-0.8.8-0-g51a3be2.tar.gzFile not found. = Couldn't fetch it - please try to retrieve this= port manually into /usr/ports/distfiles/ and try again.*** [do-fetch] Error code 1 Stop in /usr/ports/security/py-fail2ban.root@jupiter:/usr/ports/security/py-fail2ban # If you could point me in the right direction, I would be grateful! Regards,Don Wheeler ___ 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 signature.asc Description: OpenPGP digital signature
Re: devel/lprof-devel build fail - libvigraimpex.so undefined reference
* Dmitry Marakasov (amdmi3@hades.panopticon) wrote: Errors on build: [100%] Building CXX Object src/CMakefiles/lprof.dir/qrc_lprof.o Linking CXX executable lprof /usr/lib/libvigraimpex.so: undefined reference to '_ZNKSt5ctypeIcE13_M_widen_initEv@GLIBCXX_3.4.11' *** Error code 1 1 error *** Error Code 2 1 error *** Error Code 2 1 error *** Error code 1 Stop in /usr/ports/graphics/lprof-devel. Thanks in advance for any help with this This really is a result of us sticking with a rotten gcc in the base system for so long. And I expect more and more similar breakages to follow. Here, graphics/vigra uses gcc46 (since r307701) to build, and combiled vigra library depends code only present in libstdc++ from gcc46 (and not in libstdc++ in our base system). To compile lprof, adding USE_GCC=4.6+ to it's Makefile would be enough, however it won't run: % lprof /usr/lib/libstdc++.so.6: version GLIBCXX_3.4.11 required by /usr/local/lib/libvigraimpex.so.4 not found To fix that, one needs to add LD_LIBRARY_PATH=/usr/local/lib/gcc46 into environement. The same thing will be required for all vigra consumers. If gcc46 is optional for vigra, the problem may be temporary fixed by reverting r307701 (fluffy@?), however there will be more and more software depending on newer libstdc++, and we need a way to address that until all supported FreeBSD releases have switched to clang and new c++ stack. Further digging showed that vigra is built with corresponding -Wl,-rpath=/usr/local/lib/gcc46 which makes it use correct libstdc++. However, that rpath is removed by cmake on installation: -- Installing: /usr/local/lib/libvigraimpex.so.4.190 -- Installing: /usr/local/lib/libvigraimpex.so.4 -- Installing: /usr/local/lib/libvigraimpex.so -- Removed runtime path from /usr/local/lib/libvigraimpex.so.4.190 I have a fix for that: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/176901 With it, no LD_LIBRARY_PATH will be needed, but USE_GCC=4.6+ will still be required for ALL ports which depend on graphics/vigra as long as it has USE_GCC=4.6+ itself. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.ru ___ 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
pkgconf is broken?
Hello, new pkgconf (0.8.12) does different results from previos version (0.8.9) if I have instaled mjpegtools-2.0.0 command: pkgconf --exists --print-errors mjpegtools 1.6.0 mjpegtools 1.8.0 pkgconf version 0.8.9 returns 1 (correct answer) pkgconf version 0.8.12 returs 0, and make the package with errors... ___ 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
