FreeBSD ports which are currently marked forbidden
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as "forbidden" in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats portname: misc/compat3x forbidden because: FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath - not fixed / no lib available build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=compat3x portname: www/firefox forbidden because: too many security issues http://www.vuxml.org/freebsd/922d2398-9e2d-11de-a998-0030843d3802.html http://www.vuxml.org/freebsd/49e8f2ee-8147-11de-a994-0030843d3802.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=firefox portname: www/linux-firefox-devel forbidden because: Security issues http://www.vuxml.org/freebsd/f29fea8f-b19f-11dd-a55e-00163e16.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-firefox-devel portname: www/neon26 forbidden because: see CVE-2009-2474 please use neon28 or neon29 instead build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=neon26 ___ 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 unmaintained ports which are currently scheduled for deletion
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: devel/callgrind description:Valgrind skin for cache simulation and call tracing maintainer: po...@freebsd.org status: BROKEN deprecated because: Included in devel/valgrind expiration date:2009-10-30 build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.9.20091020082641/callgrind-0.9.8.log.bz2 (_Oct_24_15:04:09_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=callgrind portname: lang/gcl description:GNU Common Lisp maintainer: po...@freebsd.org status: BROKEN deprecated because: fails to build on FreeBSD 7.x expiration date:2010-01-12 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=gcl portname: net-mgmt/net-snmp4 description:An extendable SNMP implementation maintainer: po...@freebsd.org status: BROKEN deprecated because: Use net-mgmt/net-snmp port instead expiration date:2009-07-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-mgmt&portname=net-snmp4 portname: net-mgmt/p5-SNMP description:A perl5 module for interfacing with the CMU SNMP library maintainer: po...@freebsd.org deprecated because: Perl SNMP module is now a part of net-mgmt/net-snmp expiration date:2009-08-15 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-mgmt&portname=p5-SNMP portname: www/jakarta-tomcat4 description:Open-source Java web server by Apache, stable 4.0.x branch maintainer: po...@freebsd.org deprecated because: www/jakarta-tomcat5 is recommended instead for new installations expiration date:2009-01-12 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=jakarta-tomcat4 portname: www/jakarta-tomcat5 description:Open-source Java web server by Apache, 5.0.x branch maintainer: po...@freebsd.org deprecated because: Old version, consider using www/tomcat55 or www/tomcat6 instead expiration date:2009-01-12 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=jakarta-tomcat5 portname: x11-toolkits/p5-Gnome description:The main Gnome module of Gtk-Perl maintainer: po...@freebsd.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date:2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=p5-Gnome ___ 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 unmaintained ports which are currently marked forbidden
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as "forbidden" in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: misc/compat3x forbidden because: FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath - not fixed / no lib available build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=compat3x ___ 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 which are currently scheduled for deletion
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: devel/callgrind description:Valgrind skin for cache simulation and call tracing maintainer: po...@freebsd.org status: BROKEN deprecated because: Included in devel/valgrind expiration date:2009-10-30 build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.9.20091020082641/callgrind-0.9.8.log.bz2 (_Oct_24_15:04:09_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=callgrind portname: devel/gdb53 description:Source level debugger - GNU GDB 5.3 maintainer: obr...@freebsd.org status: BROKEN deprecated because: has been broken for 3 months expiration date:2010-01-18 build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2009081417/gdb-5.3_1,1.log (_Aug_17_05:35:15_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=gdb53 portname: lang/gcl description:GNU Common Lisp maintainer: po...@freebsd.org status: BROKEN deprecated because: fails to build on FreeBSD 7.x expiration date:2010-01-12 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=gcl portname: mail/squirrelmail-devel description:A webmail system which accesses mail over IMAP (Development version) maintainer: tabtho...@freebsd.org deprecated because: use mail/squirrelmail expiration date:2010-01-06 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=mail&portname=squirrelmail-devel portname: math/scilab description:A free Matlab clone by INRIA & ENPC maintainer: utis...@googlemail.com deprecated because: unmaintained, many releases behind upstream (without anyone caring), broken nearly everywhere expiration date:2009-11-21 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=math&portname=scilab portname: misc/bibletime-kde3 description:A powerful Bible study application for KDE3 maintainer: tabtho...@freebsd.org deprecated because: use misc/bibletime expiration date:2010-01-06 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=bibletime-kde3 portname: misc/sword15 description:A project framework for manipulating Bible texts maintainer: tabtho...@freebsd.org deprecated because: use misc/sword expiration date:2010-01-06 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=sword15 portname: net-mgmt/net-snmp4 description:An extendable SNMP implementation maintainer: po...@freebsd.org status: BROKEN deprecated because: Use net-mgmt/net-snmp port instead expiration date:2009-07-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-mgmt&portname=net-snmp4 portname: net-mgmt/p5-SNMP description:A perl5 module for interfacing with the CMU SNMP library maintainer: po...@freebsd.org deprecated because: Perl SNMP module is now a part of net-mgmt/net-snmp expiration date:2009-08-15 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-mgmt&portname=p5-SNMP portname: russian/php_doc description:PHP documentation in HTML (outdated version) maintainer: ed...@mavetju.org deprecated because: Support for the Russian translation of the PHP manual seems to have stopped expiration date:2009-12-31 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=russian&portname=php_doc portname: sysutils/ipmi-kmod description:Backport of ipmi driver from FreeBSD 7-CURRENT for FreeBSD 5.3 - 6.1 maintainer: s...@freebsd.org status: IGNORE deprecated because: in base system since 6.2-RELEASE expiration date:2010-01-15 build errors: none. over
FreeBSD ports which are currently marked broken
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as "broken" in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common problem is that recent versions of -CURRENT include gcc4.2, which is much stricter than older versions. The next most common problem is that compiles succeed on the i386 architecture (e.g. the common Intel PC), but fail on one or more of the other architectures due to assumptions about things such as size of various types, byte-alignment issues, and so forth. In occasional cases we see that the same port may have different errors in different build environments. The script that runs on the build cluster uses heuristics to try to 'guess' the error type to help you isolate problems, but it is only a rough guide. One more note: on occasion, there are transient build errors seen on the build farm. Unfortunately, there is not yet any way for this algorithm to tell the difference (humans are much, much better at this kind of thing.) The errors are listed below. In the case where the same problem exists on more than one build environment, the URL points to the latest errorlog for that type. (By 'build environment' here we mean 'combination of 6.x/7.x/-current with target architecture'.) (Note: the dates are included to help you to gauge whether or not the error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: audio/audacious-crossfade broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=audacious-crossfade portname: audio/ccaudio broken because: Does not build with libtool 2.2. build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=ccaudio portname: audio/dino broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=dino portname: audio/ecamegapedal broken because: does not compile build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.7.20091113082031/ecamegapedal-0.4.4_4.log.bz2 (_Nov_15_03:44:30_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=ecamegapedal portname: audio/ecawave broken because: does not compile build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.7.20091113082031/ecawave-0.6.1_5.log.bz2 (_Nov_15_03:02:38_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=ecawave portname: audio/emu10kx broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=emu10kx portname: audio/gmpc-mserver broken because: fails to build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=gmpc-mserver portname: audio/py-libmpdclient broken because: does not build build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2009081417/py26-libmpdclient-0.10.0.log (_Aug_23_08:38:53_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=py-libmpdclient portname: biology/dotter broken because: checksum mismatch build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.9.20090830194252/dotter-20021204.log.bz2 (_Oct_18_18:29:18_UTC_2009) http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2009081417/dotter-20021204.log (_Aug_17_05:33:45_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=biology&portname=dotter portname: chinese/gbk2uni broken because: does not fetch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=gbk2uni portname: chinese/iiimf-le-xcin broken because: does not build build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2009081417/zh-iiimf-le-xcin-0.1.7_5.log (_Aug_23_08:39:47_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=iiimf-le-xcin portname: comms/asmodem broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=comms&portname=asmodem portname: comms/hcfmdm broken because: Does not compile at 7.x or higher build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=comms&portname=hcfmdm portname: comms/hso-kmod broken
FreeBSD unmaintained ports which are currently marked broken
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as "broken" in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common problem is that recent versions of -CURRENT include gcc4.2, which is much stricter than older versions. The next most common problem is that compiles succeed on the i386 architecture (e.g. the common Intel PC), but fail on one or more of the other architectures due to assumptions about things such as size of various types, byte-alignment issues, and so forth. In occasional cases we see that the same port may have different errors in different build environments. The script that runs on the build cluster uses heuristics to try to 'guess' the error type to help you isolate problems, but it is only a rough guide. One more note: on occasion, there are transient build errors seen on the build farm. Unfortunately, there is not yet any way for this algorithm to tell the difference (humans are much, much better at this kind of thing.) The errors are listed below. In the case where the same problem exists on more than one build environment, the URL points to the latest errorlog for that type. (By 'build environment' here we mean 'combination of 6.x/7.x/-current with target architecture'.) (Note: the dates are included to help you to gauge whether or not the error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: audio/audacious-crossfade broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=audacious-crossfade portname: audio/ccaudio broken because: Does not build with libtool 2.2. build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=ccaudio portname: audio/py-libmpdclient broken because: does not build build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2009081417/py26-libmpdclient-0.10.0.log (_Aug_23_08:38:53_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=py-libmpdclient portname: chinese/gbk2uni broken because: does not fetch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=gbk2uni portname: chinese/iiimf-le-xcin broken because: does not build build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2009081417/zh-iiimf-le-xcin-0.1.7_5.log (_Aug_23_08:39:47_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=iiimf-le-xcin portname: comms/asmodem broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=comms&portname=asmodem portname: comms/ltmdm broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=comms&portname=ltmdm portname: comms/yawmppp broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=comms&portname=yawmppp portname: devel/ace+tao broken because: Does not compile on FreeBSD >= 7.0 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=ace%2Btao portname: devel/adabindx broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=adabindx portname: devel/agide broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=agide portname: devel/asis broken because: Does not build after gpl 2009 update to lang/gnat build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=asis portname: devel/callgrind broken because: does not build build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.9.20091020082641/callgrind-0.9.8.log.bz2 (_Oct_24_15:04:09_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=callgrind portname: devel/fampp broken because: FAM system mismatch: gamin is installed, while desired FAM system is fam build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=fampp portname: devel/florist broken because: Does not build after gpl 2009 update to lang/gnat build errors: n
Re: nvidia-driver 64bit version
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Alexey, Alexey Dokuchaev wrote: > On Fri, Dec 04, 2009 at 03:35:47PM +, Alexey Dokuchaev wrote: >> In any case, I'll post a diff here for review before I make any commits >> WRT amd64 support in nvidia-driver. > > OK, see attached diff. I could not test amd64 version, because my amd64 > box is currently down, but will certainly do so once it's up'n'running > again. i386 version works fine so far. > > I would appreciate any testing (esp. amd64) of the patched port. Please > note that some changes in pkg-list occurred; try to see that port > deinstalls cleanly in amd64 case (both via "make deinstall" and > "pkg_delete"). And, of course, that it installs and works. uname -a: FreeBSD vic.hcn-strela.ru 8.0-STABLE FreeBSD 8.0-STABLE #0: Fri Dec 4 00:48:18 MSK 2009 r...@vic.hcn-strela.ru:/usr/obj/usr/src/sys/VIC amd64 4Gb, 8800GTX. Installs: cleanly Deinstalls: cleanly pkg_delete: cleanly Works: yes (tested native app: ioquake3; linux apps: googleearth, linux-quake4) Thank you very much for the port! > > Thanks. > > ./danfe - -- Best regards, Victor Popov mailto:v.a.po...@gmail.com -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.13 (FreeBSD) iEYEARECAAYFAkscPhoACgkQtKisLOtMPvniLgCg0+RJ6+reLMTapNzULZB00Hfz qvYAoM5xNFireXGY1YbDZ+t1/mFW1vON =FLi/ -END PGP SIGNATURE- ___ 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 64bit version
On Fri, Dec 04, 2009 at 03:35:47PM +, Alexey Dokuchaev wrote:
> In any case, I'll post a diff here for review before I make any commits
> WRT amd64 support in nvidia-driver.
OK, see attached diff. I could not test amd64 version, because my amd64
box is currently down, but will certainly do so once it's up'n'running
again. i386 version works fine so far.
I would appreciate any testing (esp. amd64) of the patched port. Please
note that some changes in pkg-list occurred; try to see that port
deinstalls cleanly in amd64 case (both via "make deinstall" and
"pkg_delete"). And, of course, that it installs and works.
Thanks.
./danfe
Index: Makefile
===
RCS file: /mnt/fbsd/development/FreeBSD-CVS/ports/x11/nvidia-driver/Makefile,v
retrieving revision 1.93
diff -u -r1.93 Makefile
--- Makefile29 Sep 2009 13:25:25 - 1.93
+++ Makefile6 Dec 2009 20:56:53 -
@@ -6,18 +6,23 @@
#
PORTNAME= nvidia-driver
-DISTVERSION?= 185.18.36
+DISTVERSION?= 195.22
PORTREVISION?= 0 # As a reminder it can be overridden
CATEGORIES=x11 kld
MASTER_SITES= ${MASTER_SITE_NVIDIA}
+ARCH_SUFX= ${ARCH:S/i386//:S/amd/_/}
+.if ${DISTVERSION} == 195.22
+MASTER_SITE_SUBDIR=XFree86/FreeBSD-x86${ARCH_SUFX}/${DISTVERSION}
+ONLY_FOR_ARCHS=i386 amd64
+.else
MASTER_SITE_SUBDIR=freebsd/${DISTVERSION}
-DISTNAME= NVIDIA-FreeBSD-x86-${DISTVERSION}
+ONLY_FOR_ARCHS=i386
+.endif
+DISTNAME= NVIDIA-FreeBSD-x86${ARCH_SUFX}-${DISTVERSION}
MAINTAINER=da...@freebsd.org
COMMENT= NVidia graphics card binary drivers for hardware OpenGL
rendering
-ONLY_FOR_ARCHS=i386
-
NO_PACKAGE=should be recompiled for a particular FreeBSD kernel
USE_GL=gl
USE_LDCONFIG= yes
@@ -27,8 +32,11 @@
PORTDOCS= *
OPTIONS= FREEBSD_AGP "Use FreeBSD AGP GART driver" off \
- ACPI"Enable support for ACPI Power Management" off \
+ ACPI_PM "Enable support for ACPI Power Management" off \
LINUX "Build with support for Linux compatibility" on
+.if ${DISTVERSION} == 195.22
+OPTIONS+= WBINVD "Enable heavy-weight cache-flush logic" off
+.endif
# Starting with version 1.0-7667, NVidia has dropped support for numerous
# "legacy" GPUs. Consult NVidia README (the Appendix) to find out whether
@@ -37,7 +45,7 @@
# slave ports.
#
# XXX Until NVidia starts to name their releases consistently, employ this
-# ugly hack to derive NVVERSION. XXX
+# ugly hack below to derive NVVERSION. XXX
#
.if ${DISTVERSION:C/[0-9]+//g} == ".." # major.minor.update
NVVERSION= ${DISTVERSION:S/.//g}
@@ -80,7 +88,7 @@
${REINPLACE_CMD} -E 's/undef (NV_SUPPORT_OS_AGP)/define \1/' \
${WRKSRC}/src/nv-freebsd.h
.endif
-.if defined(WITH_ACPI)
+.if defined(WITH_ACPI_PM)
${REINPLACE_CMD} -E 's/undef (NV_SUPPORT_ACPI_PM)/define \1/' \
${WRKSRC}/src/nv-freebsd.h
.endif
@@ -88,8 +96,12 @@
${REINPLACE_CMD} -E 's/define (NV_SUPPORT_LINUX_COMPAT)/undef \1/' \
${WRKSRC}/src/nv-freebsd.h
.endif
+.if defined(WITH_WBINVD)
+ ${REINPLACE_CMD} -E 's/undef (NV_USE_WBINVD)/define \1/' \
+ ${WRKSRC}/src/nv-freebsd.h
+.endif
# Don't build any binaries (nvidia-settings and nvidia-xconfig) and manuals
-.if ${NVVERSION} < 974600
+.if ${NVVERSION} < 974600 || ${NVVERSION} == 1952200
${REINPLACE_CMD} -E 's/(extension).*/\1/' ${WRKSRC}/x11/Makefile
.else
${REINPLACE_CMD} -E 's/(lib).*/\1/' ${WRKSRC}/x11/Makefile
@@ -111,7 +123,7 @@
.if ${NVVERSION} < 817400
@${REINPLACE_CMD} '/libnvidia-cfg/d' ${TMPPLIST}
.endif
-.if ${NVVERSION} < 974600
+.if ${NVVERSION} < 974600 || ${NVVERSION} == 1952200
@${REINPLACE_CMD} '/wfb/d' ${TMPPLIST}
.endif
.if ${NVVERSION} < 1802900
Index: distinfo
===
RCS file: /mnt/fbsd/development/FreeBSD-CVS/ports/x11/nvidia-driver/distinfo,v
retrieving revision 1.33
diff -u -r1.33 distinfo
--- distinfo29 Sep 2009 13:25:25 - 1.33
+++ distinfo6 Dec 2009 18:19:43 -
@@ -1,6 +1,9 @@
-MD5 (NVIDIA-FreeBSD-x86-185.18.36.tar.gz) = feff4da79a8c3a2f194f46c95c545adb
-SHA256 (NVIDIA-FreeBSD-x86-185.18.36.tar.gz) =
890b9543d3c81bccc72d60c653647a719c9037f8fc7a88144a18b2a012fbd4a7
-SIZE (NVIDIA-FreeBSD-x86-185.18.36.tar.gz) = 19245550
+MD5 (NVIDIA-FreeBSD-x86-195.22.tar.gz) = 2c7faa5baa155693be978c446c5d44a3
+SHA256 (NVIDIA-FreeBSD-x86-195.22.tar.gz) =
2299aeadeec81a1210d65529c17c2829fdc4d5586c46b1ae6f8b20089a2122e8
+SIZE (NVIDIA-FreeBSD-x86-195.22.tar.gz) = 24784839
+MD5 (NVIDIA-FreeBSD-x86_64-195.22.tar.gz) = c9b0cdeb68d573556a38e16c02ffed55
+SHA256 (NVIDIA-FreeBSD-x86_64-195.22.tar.gz) =
3a6a0fc3003615c07090c04f2d5b41fa86cf8493309bf48eff8bcaa37126508c
+SIZE (NVIDIA-FreeBSD-x86_64-195.22.tar.gz
Re: sshd on FBSD 8.0-RC2/3
2009/12/6 Peter Beckman : > On Sun, 6 Dec 2009, Dmitry Pryanishnikov wrote: >> * LD_LIBRARY_PATH >> * rpath in the referencing file >> * ldconfig hints >> * /lib:/usr/lib >> */ >> >> Looks like 'libssl.so.6 => /usr/local/lib/libssl.so.6' is set via >> rpath - it overrides standard hints path >> '/lib:/usr/lib:/usr/lib/compat:/usr/local/lib...' but still can be >> overridden by LD_LIBRARY_PATH. > > You. Are. The. Man. I really appreciate you taking the time to dig that > up. I hope it will help someone else in the future also getting confused > with why one library is being used over another. Thanks!!! You are welcome. Yet I don't understand why these library references aren't just contain absolute library paths - instead of all this path traversing magic. That would be much more secure and less error-prone... -- Sincerely, Dmitry nic-hdl: LYNX-RIPE ___ 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"
How do I make npviewer.bin respect $TMPDIR ??
Howdy, I'm -current, i386, linux_base-f10-10_2, and linux-f10-flashplugin-10.0r32; all with the latest firefox 35. It all works fine, until my teeny tiny (24M) memory disk /tmp gets full. I have created a wrapper script for firefox to set TMPDIR (and TMP and TEMPDIR just in case) to a large partition on local disk, which works for firefox proper, but npviewer.bin is still putting its temp files on the real /tmp. So, how do I whip it into shape? Doug -- Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.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"
Re: [HEADS UP] Experimental 3D HW accel support for Radeon HD 2xxx, 3xxx and 4xxx.
=?ISO-8859-1?Q?Marius_N=FCnnerich?= writes: > One thing I know is interesting for many people is playing World > of Warcraft under wine. Last time I checked it wasn't even > possible under linux with catalyst. Do you know anything about > this or have tried it? I am not 100% certain - I use neither WoW or Linux - but I believe this is incorrect. I think a friend of a friend has this working. Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [HEADS UP] Experimental 3D HW accel support for Radeon HD 2xxx, 3xxx and 4xxx.
On Sun, Dec 6, 2009 at 15:03, Robert Noland wrote: > On Sat, 2009-12-05 at 10:01 +0200, Alex Kozlov wrote: >> On Sat, Dec 05, 2009 at 10:42:43AM +0900, Norikatsu Shigemura wrote: >> > Hi Radeon HD 2xxx, 3xxx and 4xxx users! >> > >> > I'm ready to update ports related Mesa3D to 7.6 base, graphics/dri, >> > graphics/libGL*, graphics/libglut, graphics/mesa-demos and >> > graphics/libdrm. Please see also my attached patch file. I'll >> > update these as soon as tomorrow. >> > >> > Mesa3D 7.6 supports experimental r600 driver, as known as AMD >> > R6xx/R7xx architecture. I confirmed that it's good works, but >> > buggy on my Radeon HD 4850 environment with 9-current/amd64 and >> > xf86-video-radeonhd-devel. Please see also [I known problem] >> > section. >> I use similiar setup(but with mesa git master) for more than a month >> without a problem. HD 3650 AGP. glxgear, other demos and even some old >> games in wine like deusex work fine. > > Openarena, UT, vdrift, nexuiz, etc... should all work fairly well also. > There are still features that are not yet implemented on r600, but I > tend to run all of the above all video options enabled on highest > settings. Really large textures are slow and it seems like I found one > option that really hurt performance (bloom maybe), but otherwise they > are all more than playable on my HD4650 core2duo e7400. > > Disclaimer: I'm not a gamer... but I do use them for testing. > > robert. One thing I know is interesting for many people is playing World of Warcraft under wine. Last time I checked it wasn't even possible under linux with catalyst. Do you know anything about this or have tried it? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [HEADS UP] Experimental 3D HW accel support for Radeon HD 2xxx, 3xxx and 4xxx.
Hi rnoland. Thank you. I'll commit after 7.6.1 release, at least. On Sun, 06 Dec 2009 07:51:22 -0600 Robert Noland wrote: > Actually, looking through the patch now... Two things jump out at me... > We can't currently update libdrm in the ports collection without > breaking nouveau. The second is, don't enable libdrm_radeon, even when > we can. libdrm_radeon is only needed for TTM/KMS enabled radeon and may > cause upgrade/build issues if it exists. OK. I'll change libdrm_radeon is OPTIONal(default off), and r600_dri.so installable by libdrm_radeon exists. ___ 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: The new cups ports seem to not recognize usb printers on FreeBSD 7.2-STABLE
End of Story. I recompiled cups without LIBUSB and the 7.2 servers can now print. Such a simple solution still makes me think that a note in ports/UPDATING could be a real time saver. I want to thank Matt, Gary, Steve and Brian for their help. have a great weekend, ed Quoting Matt Dawson : On Sunday 06 Dec 2009 11:17:52 you wrote: On Sunday 06 Dec 2009 00:00:03 freebsd-ports-requ...@freebsd.org wrote: > > An option WITH_LIBUSB was added to the cups-base/Makefile. That's > > probably what Dirk meant. > > Thanks for the explanation, Gary. I have it set with make config but > just hardcoded it into the Makefile and am recompiling but I doubt it > will change but there is still hope. ;) The attached patch works on 8.0-RELEASE for me, restoring the non-libusb functionality. Leave the libusb option disabled and just compile as normal. Gah, sorry about the subject line. Won't happen again. -- Matt Dawson MTD15-RIPE m...@chronos.org.uk ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [HEADS UP] Experimental 3D HW accel support for Radeon HD 2xxx, 3xxx and 4xxx.
On Sat, 2009-12-05 at 10:01 +0200, Alex Kozlov wrote: > On Sat, Dec 05, 2009 at 10:42:43AM +0900, Norikatsu Shigemura wrote: > > Hi Radeon HD 2xxx, 3xxx and 4xxx users! > > > > I'm ready to update ports related Mesa3D to 7.6 base, graphics/dri, > > graphics/libGL*, graphics/libglut, graphics/mesa-demos and > > graphics/libdrm. Please see also my attached patch file. I'll > > update these as soon as tomorrow. > > > > Mesa3D 7.6 supports experimental r600 driver, as known as AMD > > R6xx/R7xx architecture. I confirmed that it's good works, but > > buggy on my Radeon HD 4850 environment with 9-current/amd64 and > > xf86-video-radeonhd-devel. Please see also [I known problem] > > section. > I use similiar setup(but with mesa git master) for more than a month > without a problem. HD 3650 AGP. glxgear, other demos and even some old > games in wine like deusex work fine. Openarena, UT, vdrift, nexuiz, etc... should all work fairly well also. There are still features that are not yet implemented on r600, but I tend to run all of the above all video options enabled on highest settings. Really large textures are slow and it seems like I found one option that really hurt performance (bloom maybe), but otherwise they are all more than playable on my HD4650 core2duo e7400. Disclaimer: I'm not a gamer... but I do use them for testing. robert. > > -- > Adios > ___ > freebsd-...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-x11 > To unsubscribe, send any mail to "freebsd-x11-unsubscr...@freebsd.org" -- Robert Noland FreeBSD ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [HEADS UP] Experimental 3D HW accel support for Radeon HD 2xxx, 3xxx and 4xxx.
On Sat, 2009-12-05 at 10:42 +0900, Norikatsu Shigemura wrote: > Hi Radeon HD 2xxx, 3xxx and 4xxx users! > > I'm ready to update ports related Mesa3D to 7.6 base, graphics/dri, > graphics/libGL*, graphics/libglut, graphics/mesa-demos and > graphics/libdrm. Please see also my attached patch file. I'll > update these as soon as tomorrow. > > Mesa3D 7.6 supports experimental r600 driver, as known as AMD > R6xx/R7xx architecture. I confirmed that it's good works, but > buggy on my Radeon HD 4850 environment with 9-current/amd64 and > xf86-video-radeonhd-devel. Please see also [I known problem] > section. > > [kernel support] > maybe, 7-stable, 8-release(at least 8-stable) and 9-current are OK. > http://svn.freebsd.org/changeset/base/196470 (HEAD 2009/08/23) > http://svn.freebsd.org/changeset/base/198685 (RELENG_8 2009/10/30) > http://svn.freebsd.org/changeset/base/198686 (RELENG_7 2009/10/30) > > [X11 driver support] > x11-drivers/xf86-video-ati OK > x11-drivers/xf86-video-radeonhd I don't know > x11-drivers/xf86-video-radeonhd-devel OK > > [To enable xorg.conf] > Section "ServerFlags" > Option "AIGLX" "true" > EndSection > > [I know a problem] > 3D accelerated applications like glxgear, compiz display with > bluish coloring. I confirmed git master branch Mesa3D codes, > too. So I consider that this problem wasn't be fixed. > > [Why update to 7.6] > I confirmed git master and 7.6, I think these are almost same > quality. So I choose 7.6. Actually, looking through the patch now... Two things jump out at me... We can't currently update libdrm in the ports collection without breaking nouveau. The second is, don't enable libdrm_radeon, even when we can. libdrm_radeon is only needed for TTM/KMS enabled radeon and may cause upgrade/build issues if it exists. robert. > ___ > freebsd-...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-x11 > To unsubscribe, send any mail to "freebsd-x11-unsubscr...@freebsd.org" -- Robert Noland FreeBSD ___ 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: firefox-35 does not terminate.
Le Fri, 2 Oct 2009 23:47:06 +0200, Patrick Lamaiziere a écrit : > firefox 35 does not terminate here, when I quit it, it continue to > runs at 100%. Even if I only go to a simple page like google, so I > don't think it's related to the flash plugin(?) Just find today... It's because I use gtk-qt4-engine. "setenv GTK_QT_ENGINE_DISABLE yes" as a work-around. 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: The new cups ports seem to not recognize usb printers on FreeBSD 7.2-STABLE
On Sunday 06 Dec 2009 12:00:23 freebsd-ports-requ...@freebsd.org wrote:
> On Sunday 06 Dec 2009 00:00:03 freebsd-ports-requ...@freebsd.org wrote:
> > > An option WITH_LIBUSB was added to the cups-base/Makefile. That's
> > > probably what Dirk meant.
> >
> >
> > Thanks for the explanation, Gary. I have it set with make config
> > but just hardcoded it into the Makefile and am recompiling but I
> > doubt it will change but there is still hope. ;)
>
> The attached patch works on 8.0-RELEASE for me, restoring the
> non-libusb functionality. Leave the libusb option disabled and just
> compile as normal.
The attached couple of patches fix this port in all cases, tested with
tinderbox. Since libusb is in base for FBSD>8 it needs handling
differently. Note well that if you use libusb, you need to NOT attach the
ulpt* driver to the device, i.e. remove ulpt from your kernel or don't load
it at boot.
Also fixed is the CUPS_OVERWRITE_BASE case deinstall, restoring the correct
permissions to lp and friends.
--
Matt Dawson
MTD15-RIPE
m...@chronos.org.uk
--- ./ports/print/cups-base/Makefile.orig 2009-12-06 11:02:46.0 +
+++ ./ports/print/cups-base/Makefile 2009-12-06 12:21:21.0 +
@@ -173,8 +173,13 @@
RUN_DEPENDS+= xdg-open:${PORTSDIR}/devel/xdg-utils
.endif
-.if !defined(CUPS_CLIENT) && !defined(CUPS_IMAGE) && defined(WITH_LIBUSB)
+.if !defined(CUPS_CLIENT) && !defined(CUPS_IMAGE) && defined(WITH_LIBUSB) && ${OSVERSION}>80
+CPPFLAGS+= -I/usr/include
+LDFLAGS+= -L/usr/lib
+.elif !defined(CUPS_CLIENT) && !defined(CUPS_IMAGE) && defined(WITH_LIBUSB) && ${OSVERSION}<79
LIB_DEPENDS+= usb:${PORTSDIR}/devel/libusb
+.else
+CONFIGURE_ARGS+= --disable-libusb
.endif
.if defined(CUPS_CLIENT)
--- ./ports/print/cups-base/pkg-plist.orig 2009-12-06 12:23:00.0 +
+++ ./ports/print/cups-base/pkg-plist 2009-12-06 12:24:18.0 +
@@ -20,6 +20,11 @@
%%overwrit...@exec if test -e /usr/bin/lpr; then chmod -h 0 /usr/bin/lpr; fi
%%overwrit...@exec if test -e /usr/bin/lprm; then chmod -h 0 /usr/bin/lprm; fi
%%overwrit...@exec if test -e /usr/sbin/lpc; then chmod -h 0 /usr/sbin/lpc; fi
+%%overwrit...@unexec if test -e /usr/bin/lp; then chmod -h 0555 /usr/bin/lp; fi
+%%overwrit...@unexec if test -e /usr/bin/lpq; then chmod -h 06555 /usr/bin/lpq; fi
+%%overwrit...@unexec if test -e /usr/bin/lpr; then chmod -h 06555 /usr/bin/lpr; fi
+%%overwrit...@unexec if test -e /usr/bin/lprm; then chmod -h 06555 /usr/bin/lprm; fi
+%%overwrit...@unexec if test -e /usr/sbin/lpc; then chmod -h 02555 /usr/sbin/lpc; fi
@unexec if cmp -s %D/etc/cups/cupsd.conf.N %D/etc/cups/cupsd.conf; then rm -f %D/etc/cups/cupsd.conf; fi
etc/cups/cupsd.conf.N
@exec if test ! -f %D/etc/cups/cupsd.conf; then cp -p %D/etc/cups/cupsd.conf.N %D/etc/cups/cupsd.conf; fi
signature.asc
Description: This is a digitally signed message part.
Re: [patch] switch to Emacs 23
On Wed, 02 Dec 2009 14:24:03 +0300 Boris Samorodov wrote: > here is a patch to switch to Emacs 23 as a default. There are > 50 affected ports. Tests were done at tinderbox. Please give > this patch a try. I'm going to fire up an exp run after some > testing. The patch is relative to PORTSDIR: > > ftp://ftp.ipt.ru/pub/download/ports.diff.bz2 > Seems to work pretty well on 9-C and AMD64. There are LOTS of "casting pointer to integer of a different size" warnings, but that's just sloppy programming upstream. --- Gary Jennejohn ___ 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: The new cups ports seem to not recognize usb printers on FreeBSD 7.2-STABLE
On Sunday 06 Dec 2009 11:17:52 you wrote: > On Sunday 06 Dec 2009 00:00:03 freebsd-ports-requ...@freebsd.org wrote: > > > An option WITH_LIBUSB was added to the cups-base/Makefile. That's > > > probably what Dirk meant. > > > > Thanks for the explanation, Gary. I have it set with make config but > > just hardcoded it into the Makefile and am recompiling but I doubt it > > will change but there is still hope. ;) > > The attached patch works on 8.0-RELEASE for me, restoring the non-libusb > functionality. Leave the libusb option disabled and just compile as > normal. > Gah, sorry about the subject line. Won't happen again. -- Matt Dawson MTD15-RIPE m...@chronos.org.uk signature.asc Description: This is a digitally signed message part.
Re: freebsd-ports Digest, Vol 341, Issue 7
On Sunday 06 Dec 2009 00:00:03 freebsd-ports-requ...@freebsd.org wrote:
> > An option WITH_LIBUSB was added to the cups-base/Makefile. That's
> > probably what Dirk meant.
>
> Thanks for the explanation, Gary. I have it set with make config but
> just hardcoded it into the Makefile and am recompiling but I doubt it
> will change but there is still hope. ;)
The attached patch works on 8.0-RELEASE for me, restoring the non-libusb
functionality. Leave the libusb option disabled and just compile as normal.
--
Matt Dawson
MTD15-RIPE
m...@chronos.org.uk
--- ./ports/print/cups-base/Makefile.orig 2009-12-06 11:02:46.0 +
+++ ./ports/print/cups-base/Makefile 2009-12-06 11:09:36.0 +
@@ -175,6 +175,8 @@
.if !defined(CUPS_CLIENT) && !defined(CUPS_IMAGE) && defined(WITH_LIBUSB)
LIB_DEPENDS+= usb:${PORTSDIR}/devel/libusb
+.else
+CONFIGURE_ARGS+= --disable-libusb
.endif
.if defined(CUPS_CLIENT)
___
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"
