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 5.x/6.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: chinese/iiimf-le-xcin broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=iiimf-le-xcin portname: deskutils/mical broken because: Miscellaneous run-time failures due out of sync with the current versions of dependencies build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=deskutilsportname=mical portname: devel/ace+tao broken because: Does not compile on FreeBSD = 7.0 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=ace%2Btao portname: devel/agide broken because: does not build build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.8.20090513195558/agide-0.124_2.log (_May_19_01:48:19_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=agide 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=develportname=fampp portname: devel/linuxthreads broken because: leaves file on deinstall build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.7.20090524180327/linuxthreads-2.2.3_23.log (_May__6_20:58:39_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linuxthreads portname: devel/p5-ORBit broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=p5-ORBit portname: devel/ruby-p4 broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=ruby-p4 portname: emulators/snes9express broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=emulatorsportname=snes9express portname: games/amy broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=gamesportname=amy portname: games/fgsd broken because: does not build with simgear build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=gamesportname=fgsd portname: games/hlstatsx broken because: Does not fetch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=gamesportname=hlstatsx portname: graphics/demeter broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=demeter portname: graphics/libvisual-plugins broken because: Broken objformat handling build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=libvisual-plugins portname: graphics/pixieplus broken because: does not compile build errors:
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 5.x/6.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/dino broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=dino portname: audio/emu10kx broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=emu10kx portname: audio/gai-album broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=gai-album portname: audio/gai-visual-audio broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=gai-visual-audio portname: audio/gnomad2 broken because: does not compile with current version of libmtp build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=gnomad2 portname: audio/p5-Audio-TagLib broken because: does not build with taglib 1.5 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=p5-Audio-TagLib portname: audio/py-sdl_mixer broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=py-sdl_mixer portname: audio/sineshaper broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=sineshaper portname: biology/embassy broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=biologyportname=embassy portname: cad/alliance broken because: does not compile build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.8.20090325165011/alliance-5.0.20070718_1.log (_Mar_26_08:21:12_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=cadportname=alliance portname: cad/freecad broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=cadportname=freecad portname: chinese/iiimf-le-xcin broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=iiimf-le-xcin portname: comms/gfax broken because: doesn't build with mono 2.0.1 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=commsportname=gfax portname: comms/hcfmdm broken because: Does not compile at 7.x build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=commsportname=hcfmdm portname: converters/mimelib broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=convertersportname=mimelib portname: databases/erserver broken because: Does not compile with GCC 4.2 build errors: none. overview:
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: audio/festival+OGI description:Text-to-speech system with OGI residual LPC synthesizer maintainer: po...@freebsd.org deprecated because: unmaintained, does not work with current versions of GCC, needs gcc295 which has been failing to build for months expiration date:2009-04-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=festival%2BOGI portname: audio/festlex-ifd description:Italian lexicon for Festival maintainer: po...@freebsd.org deprecated because: unfulfilled dependencies for 8+ months, no active maintainer, no user interest expiration date:2009-06-10 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=festlex-ifd portname: audio/festogi-italian description:Italian support for Festival maintainer: po...@freebsd.org deprecated because: unfulfilled dependencies for 8+ months, no active maintainer, no user interest expiration date:2009-06-10 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=festogi-italian portname: audio/festogi-spanish description:Mexican Spanish support for Festival maintainer: po...@freebsd.org deprecated because: unfulfilled dependencies for 8+ months, no maintainer, no user interest expiration date:2009-06-09 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=festogi-spanish portname: audio/festvox-jph description:American English male voice for Festival maintainer: po...@freebsd.org deprecated because: unfulfilled dependencies for 8+ months, no maintainer, no user interest expiration date:2009-06-09 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=festvox-jph portname: audio/festvox-lp description:Italian female voice for Festival maintainer: po...@freebsd.org deprecated because: unfulfilled dependencies for 8+ months, no active maintainer, no user interest expiration date:2009-06-10 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=festvox-lp portname: audio/festvox-mwm description:American English male voice for Festival maintainer: po...@freebsd.org deprecated because: unfulfilled dependencies for 8+ months, no maintainer, no user interest expiration date:2009-06-09 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=festvox-mwm portname: audio/festvox-ogirab description:British English male voice for Festival (non-commercial use only) maintainer: po...@freebsd.org deprecated because: unfulfilled dependencies for 8+ months, no maintainer, no user interest expiration date:2009-06-09 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=festvox-ogirab portname: audio/festvox-pc description:Italian male voice for Festival maintainer: po...@freebsd.org deprecated because: unfulfilled dependencies for 8+ months, no active maintainer, no user interest expiration date:2009-06-10 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=festvox-pc portname: audio/festvox-tll description:American English female voice for Festival (no commercial use) maintainer: po...@freebsd.org deprecated because: unfulfilled dependencies for 8+ months, no maintainer, no user interest expiration date:2009-06-09 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=festvox-tll portname: games/amy
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: audio/festival+OGI description:Text-to-speech system with OGI residual LPC synthesizer maintainer: po...@freebsd.org deprecated because: unmaintained, does not work with current versions of GCC, needs gcc295 which has been failing to build for months expiration date:2009-04-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=festival%2BOGI portname: audio/festlex-ifd description:Italian lexicon for Festival maintainer: po...@freebsd.org deprecated because: unfulfilled dependencies for 8+ months, no active maintainer, no user interest expiration date:2009-06-10 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=festlex-ifd portname: audio/festogi-italian description:Italian support for Festival maintainer: po...@freebsd.org deprecated because: unfulfilled dependencies for 8+ months, no active maintainer, no user interest expiration date:2009-06-10 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=festogi-italian portname: audio/festogi-spanish description:Mexican Spanish support for Festival maintainer: po...@freebsd.org deprecated because: unfulfilled dependencies for 8+ months, no maintainer, no user interest expiration date:2009-06-09 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=festogi-spanish portname: audio/festvox-abc description:Mexican Spanish male voice for Festival speech synthesis system maintainer: ara...@freebsd.org status: IGNORE deprecated because: unfulfilled dependencies for 8+ months, no user interest. expiration date:2009-06-09 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=festvox-abc portname: audio/festvox-hvs description:Mexican Spanish female voice for Festival maintainer: ara...@freebsd.org status: IGNORE deprecated because: unfulfilled dependencies for 8+ months, no user interest. expiration date:2009-06-09 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=festvox-hvs portname: audio/festvox-jph description:American English male voice for Festival maintainer: po...@freebsd.org deprecated because: unfulfilled dependencies for 8+ months, no maintainer, no user interest expiration date:2009-06-09 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=festvox-jph portname: audio/festvox-lp description:Italian female voice for Festival maintainer: po...@freebsd.org deprecated because: unfulfilled dependencies for 8+ months, no active maintainer, no user interest expiration date:2009-06-10 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=festvox-lp portname: audio/festvox-mwm description:American English male voice for Festival maintainer: po...@freebsd.org deprecated because: unfulfilled dependencies for 8+ months, no maintainer, no user interest expiration date:2009-06-09 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=festvox-mwm portname: audio/festvox-ogirab description:British English male voice for Festival (non-commercial use only) maintainer: po...@freebsd.org deprecated because: unfulfilled dependencies for 8+ months, no maintainer, no user interest expiration date:2009-06-09 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=festvox-ogirab
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: chinese/wordpress forbidden because: http://www.vuxml.org/freebsd/622bc638-be27-11dd-a578-0030843d3802.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=wordpress 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=miscportname=compat3x portname: www/awstats-devel forbidden because: http://www.vuxml.org/freebsd/27d78386-d35f-11dd-b800-001b77d09812.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=awstats-devel 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=wwwportname=linux-firefox-devel ___ 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 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: chinese/wordpress forbidden because: http://www.vuxml.org/freebsd/622bc638-be27-11dd-a578-0030843d3802.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=wordpress portname: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=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=miscportname=compat3x portname: www/amaya forbidden because: Security issues http://www.vuxml.org/freebsd/a89b76a7-f6bd-11dd-94d9-0030843d3802.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=amaya portname: www/awstats-devel forbidden because: http://www.vuxml.org/freebsd/27d78386-d35f-11dd-b800-001b77d09812.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=awstats-devel portname: www/linux-firefox forbidden because: Security issues http://www.vuxml.org/freebsd/8b491182-f842-11dd-94d9-0030843d3802.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=linux-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=wwwportname=linux-firefox-devel portname: www/tdiary-devel forbidden because: contains a vulnerability: http://www.tdiary.org/20071215.html written in Japanese build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=tdiary-devel ___ 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: MAKE_JOBS_UNSAFE (some more ports)
On Saturday 06 June 2009 22:56:47 Ion-Mihai Tetcu wrote: On Sat, 6 Jun 2009 18:05:14 +0200 David Naylor naylor.b.da...@gmail.com wrote: P.S. Is anyone interested in a list of ports that do not compile under tmpfs? Me. The following are on my blacklist for tmpfs build, where: # df -h | grep tmp tmpfs 8.3G 12M8.3G 0%/tmp # grep WRKDIRPREFIX /etc/make.conf WRKDIRPREFIX=/tmp editors/openoffice.org-3 (just to big for my computer to handle) security/gpgme* lang/ocaml** java/openjdk6*** * Confirmed build failure on 7.1p2 and -Current from December * Confirmed build success on -Current from Saturday ** I had a strange problems with math/facile that it wouldn't build if ocaml was built on tmpfs (didn't confirm this one) *** Cannot reproduce (although do remember it) From what I read it appeared that tmpfs had an internal locking problem however it appears to be fixed in current. signature.asc Description: This is a digitally signed message part.
portupgrade and ruby-1.8.7.160
Hi, Ever since I upgraded to ruby-1.8.7.160 on two separate hosts this past week, portupgrade has been complaining with: ** Database file locked. Waiting. or ** Stale lock removed. even if there is only one portupgrade process that's running. If I revert back to ruby-1.8.7.72, these warnings go away. I wouldn't mind these warnings so much, except that the Database file locked message also has an annoying timeout period associated with it. Cheers. -- Jonathan Chen j...@chen.org.nz -- A little learning is a dangerous thing but a lot of ignorance is just as bad. - Bob Edwards ___ 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/nvidia-driver] conflicts with linux dri ports
Hi! I've just received a report at emulation@ about x11/nvidia-driver and other linux dri ports to be in conflict. If a linux dri port is installed x11/nvidia-driver seems to replace libGL.so with a link to nvidia library. Not good. Is it right to mark this port and other linux dri ports to be in conflict? WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: plans to retire kqemu (poll)
Sound a bit stupid to retire it in favor of options such as Xen or VirtualBox. Kqemu is non-obtrusive, tested, and easily ported between systems. For some of us, good hardware or new hardware is not an option. From: n...@jelal.kn-bremen.de Date: Fri, 5 Jun 2009 20:59:32 +0200 To: freebsd-emulat...@freebsd.org; freebsd-ports@FreeBSD.org CC: Subject: plans to retire kqemu (poll) Hi! If you are using kqemu you might want to fill out this little poll set up by Anthony Liguori, a qemu developer: http://www.micropoll.com/akira/mpview/604126-172373 Here is his original posting on the qemu list: http://lists.gnu.org/archive/html/qemu-devel/2009-06/msg00151.html And here is one of the threads discussing reasons for the plans: http://lists.gnu.org/archive/html/qemu-devel/2009-06/msg00019.html Just so you know... Juergen ___ 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 _ Windows Live™ SkyDrive™: Get 25 GB of free online storage. http://windowslive.com/online/skydrive?ocid=TXT_TAGLM_WL_SD_25GB_062009___ 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: [x11/nvidia-driver] conflicts with linux dri ports
Boris Samorodov wrote:
Hi!
Hello there,
I've just received a report at emulation@ about x11/nvidia-driver and
other linux dri ports to be in conflict.
If a linux dri port is installed x11/nvidia-driver seems to replace
libGL.so with a link to nvidia library. Not good. Is it right to
mark this port and other linux dri ports to be in conflict?
Weird, as this is the first report of that kind. Also, per what I see
in graphics/linux_dri{,-devel}, linuxish libGL* files go to usr/X11R6
(under LINUXBASE, I assume), while nvidia-driver installs them under
usr/lib.
I will dig that emulation@ message to take a closer look.
Thanks.
./danfe
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [x11/nvidia-driver] conflicts with linux dri ports
On Sun, 7 Jun 2009 11:34:12 + Alexey Dokuchaev wrote:
Boris Samorodov wrote:
I've just received a report at emulation@ about x11/nvidia-driver and
other linux dri ports to be in conflict.
If a linux dri port is installed x11/nvidia-driver seems to replace
libGL.so with a link to nvidia library. Not good. Is it right to
mark this port and other linux dri ports to be in conflict?
Weird, as this is the first report of that kind. Also, per what I see
in graphics/linux_dri{,-devel}, linuxish libGL* files go to usr/X11R6
(under LINUXBASE, I assume), while nvidia-driver installs them under
usr/lib.
Hm, you are right...
BTW, new linux dri ports:
. graphics/linux-f8-dri;
. graphics/linux-f10-dri;
. graphics/linux-dri74
istall libraries to usr/lib. Seems that those ports should be
added to CONFLICTS.
I will dig that emulation@ message to take a closer look.
Thanks, I'm also interested.
WBR
--
Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone Internet SP
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
___
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: [x11/nvidia-driver] conflicts with linux dri ports
On Sun, 07 Jun 2009 14:28:58 +0400 Boris Samorodov b...@ipt.ru wrote: Hi! I've just received a report at emulation@ about x11/nvidia-driver and other linux dri ports to be in conflict. If a linux dri port is installed x11/nvidia-driver seems to replace libGL.so with a link to nvidia library. Not good. Is it right to mark this port and other linux dri ports to be in conflict? The nvidia-driver port overwrites the libGL installed by the native Xorg. GLX doesn't work if this doesn't happen. Presumably it's doing something similar with the Linux version. ___ 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: [Call For Testing] VirtualBox for FreeBSD! take 4
Hello Martin! Wed, May 27, 2009 at 03:43:43PM +0200 you wrote: Howdy, First of all sorry for all unanswered mails, I got a stupid flu, but now i feel better... ok now back to vbox, time for a new call for testing :-) http://people.freebsd.org/~miwi/vbox/virtualbox_5.tgz I'm running -CURRENT (yesterday's kernel) on i386, single-processor. I've tried this out, it works OK (including a WinXP install + installation of VS2005 under it), but there's a problem when I try to shut down the VM: the host system reproducibly panics:(. Here's what I've managed to get: Unread portion of the kernel message buffer: panic: vm_page_dirty: page is invalid! (kgdb) bt #0 doadump () at pcpu.h:246 #1 0xc086270e in boot (howto=260) at /home/df/checkouts/freebsd/src/sys/kern/kern_shutdown.c:420 #2 0xc08629e2 in panic (fmt=Variable fmt is not available. ) at /home/df/checkouts/freebsd/src/sys/kern/kern_shutdown.c:576 #3 0xc0a9fdf2 in vm_page_dirty (m=0x0) at /home/df/checkouts/freebsd/src/sys/vm/vm_page.c:574 #4 0xc0b685ad in pmap_remove_pte (pmap=0xc87bb358, ptq=Variable ptq is not available. ) at /home/df/checkouts/freebsd/src/sys/i386/i386/pmap.c:2478 #5 0xc0b68f1a in pmap_remove (pmap=0xc87bb358, sva=2945187840, eva=2945318912) at /home/df/checkouts/freebsd/src/sys/i386/i386/pmap.c:2607 #6 0xc0a967bc in vm_map_delete (map=0xc87bb2ac, start=2945187840, end=2945318912) at /home/df/checkouts/freebsd/src/sys/vm/vm_map.c:2579 #7 0xc0a969c1 in vm_map_remove (map=0xc87bb2ac, start=2945187840, end=2945318912) at /home/df/checkouts/freebsd/src/sys/vm/vm_map.c:2608 #8 0xc19ef55c in rtR0MemObjNativeFree () from /boot/modules/vboxdrv.ko #9 0xc19edbb2 in RTR0MemObjFree () from /boot/modules/vboxdrv.ko #10 0xc19dc4ac in supdrvMemRelease () from /boot/modules/vboxdrv.ko #11 0xc19df52e in supdrvIOCtl () from /boot/modules/vboxdrv.ko #12 0xc19dadca in VBoxDrvFreeBSDIOCtl () from /boot/modules/vboxdrv.ko #13 0xc07e73f8 in devfs_ioctl_f (fp=0xc7c54508, com=3317652896, data=0xc5bf5da0, cred=0xc87c1800, td=0xc8257900) at /home/df/checkouts/freebsd/src/sys/fs/devfs/devfs_vnops.c:660 #14 0xc08a59ad in kern_ioctl (td=0xc8257900, fd=22, com=3223082507, data=0xc5bf5da0 birddrib\034) at file.h:262 #15 0xc08a5b34 in ioctl (td=0xc8257900, uap=0xe6d33cf8) at /home/df/checkouts/freebsd/src/sys/kern/sys_generic.c:677 #16 0xc0b6c853 in syscall (frame=0xe6d33d38) at /home/df/checkouts/freebsd/src/sys/i386/i386/trap.c:1073 #17 0xc0b4fab0 in Xint0x80_syscall () at /home/df/checkouts/freebsd/src/sys/i386/i386/exception.s:261 #18 0x0033 in ?? () Still, thanks a lot for your hard work! VirtualBox is such a nice thing... -- DoubleF No virus detected in this message. Ehrm, wait a minute... /kernel: pid 56921 (antivirus), uid 32000: exited on signal 9 Oh yes, no virus:) pgpubOEORzJJ3.pgp Description: PGP signature
Re: MAKE_JOBS_UNSAFE (some more ports)
David Naylor wrote: On Saturday 06 June 2009 22:56:47 Ion-Mihai Tetcu wrote: On Sat, 6 Jun 2009 18:05:14 +0200 David Naylor naylor.b.da...@gmail.com wrote: P.S. Is anyone interested in a list of ports that do not compile under tmpfs? Me. The following are on my blacklist for tmpfs build, where: # df -h | grep tmp tmpfs 8.3G 12M8.3G 0%/tmp # grep WRKDIRPREFIX /etc/make.conf WRKDIRPREFIX=/tmp editors/openoffice.org-3 (just to big for my computer to handle) security/gpgme* lang/ocaml** java/openjdk6*** * Confirmed build failure on 7.1p2 and -Current from December * Confirmed build success on -Current from Saturday ** I had a strange problems with math/facile that it wouldn't build if ocaml was built on tmpfs (didn't confirm this one) *** Cannot reproduce (although do remember it) From what I read it appeared that tmpfs had an internal locking problem however it appears to be fixed in current. Last I tried it, procmail did not build on tmpfs either, I didn't have time to report the full details. After getting a compile error, I looked into what was in the build directory and found two files with the same name!! I think when I deleted one, I think the size of the other showed a change. ___ 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
gnome-panel-2.26.2 build failure: cp: configure: No such file or directory
===Verifying install for panel-applet-2.0 in /usr/ports/x11/gnome-panel === gnome-panel-2.26.2 depends on executable: gmake - found [many depends deleted] === gnome-panel-2.26.2 depends on shared library: pango-1.0.0 - found === Configuring for gnome-panel-2.26.2 cp: configure: No such file or directory *** Error code 1 This is from a ports tree refreshed 6-6-09 regards -kim ___ 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
skype-out calls disconnect after 5 minute
My system: FreeBSD 7.2-RELEASE #0: Fri May 1 08:49:13 UTC 2009 r...@walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 Skype-out calls disconnect after about 5 minutes. I red that was problem with beta or pre release but looks like that is the problem here still. Version of Skype is 2.9.9.72. Do I need to put kern.hz=100 in loader.conf, please? Thanks in advace, -- Mitja - http://starikarp.redbubble.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: porting dash (the shell)
Eitan Adler wrote:
Boris Kochergin wrote:
Eitan Adler wrote:
if gcc -DBSD=1 -DSMALL -DSHELL -DGLOB_BROKEN -DFNMATCH_BROKEN
-DIFS_BROKEN -D__COPYRIGHT\(x\)= -D__RCSID\(x\)= -D_DIAGASSERT\(x\)= -I.
-I. -I.. -include ../config.h -g -O2 -Wall -MT exec.o -MD -MP -MF
.deps/exec.Tpo \
-c -o exec.o `test -f 'exec.c' || echo './'`exec.c; \
then mv -f .deps/exec.Tpo .deps/exec.Po; \
else rm -f .deps/exec.Tpo; exit 1; \
fi
exec.c: In function 'find_command':
exec.c:317: error: storage size of 'statb' isn't known
exec.c:326: warning: implicit declaration of function 'stat64'
exec.c:317: warning: unused eitan 'statb'
gmake[3]: *** [exec.o] Error 1
gmake[3]: Leaving directory `/home/eitan/dash-0.5.1/src'
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory `/home/eitan/dash-0.5.1/src'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/home/eitan/dash-0.5.1'
gmake: *** [all] Error 2
stat64() and the statb structure appear to be some kind of Linuxisms.
FreeBSD's stat() doesn't have any trouble with file sizes of over 2 GiB,
so try replacing the stat64() call with stat() and the statb structure
with a stat structure.
-Boris
After doing a global search and replace of stat64 to stat I get:
mystring.c: In function 'single_quote':
mystring.c:164: warning: implicit declaration of function 'strchrnul'
mystring.c:164: error: invalid operands to binary -
mystring.c:169: warning: implicit declaration of function 'mempcpy'
mystring.c:169: warning: incompatible implicit declaration of built-in
function 'mempcpy'
strchrnul() and mempcpy() are GNU extensions to libc. Here they are,
implemented in ISO C:
char *strchrnul(const char *s, int c) {
char *i;
for (i = (char*)s; *i != '\0'; ++i) {
if (*i == c) {
return i;
}
}
return i;
}
void *mempcpy(void *dst, const void *src, size_t len) {
return (void*)(((char*)memcpy(dst, src, len)) + len);
}
You can Google around (or read the Linux man page) for what a GNU
extension is supposed to do and implement it pretty easily. It's also a
good idea to test your resulting code against the actual glibc
implementation (I tested these on a friend's Linux machine).
-Boris
___
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/nvidia-driver] conflicts with linux dri ports
Hi! I've just received a report at emulation@ about x11/nvidia-driver and other linux dri ports to be in conflict. If a linux dri port is installed x11/nvidia-driver seems to replace libGL.so with a link to nvidia library. Not good. Is it right to mark this port and other linux dri ports to be in conflict? Why it's not good? I'm not sure I've understood, but I think it's more or less the same with the native counterpart: if you install x11/nvidia-driver, libGL.so from graphics/libGL get replaced (actually renamed). ___ 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
Port admission request
Hi, I would like to bring to your attention my project hosted here: http://www.rtmpd.com I know how Adobe is keep ignoring our request of having a flash player for FreeBSD. I though that at least we have another decent C++ implementation of a media server. This is an under development project but is usable in his current (trunk) state. Let me know if you can/want to add it in the ports Thank you for your time, Andrei ___ 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: [x11/nvidia-driver] conflicts with linux dri ports
On Sun, 7 Jun 2009 21:34:53 +0200 barbara wrote: I've just received a report at emulation@ about x11/nvidia-driver and other linux dri ports to be in conflict. If a linux dri port is installed x11/nvidia-driver seems to replace libGL.so with a link to nvidia library. Not good. Is it right to mark this port and other linux dri ports to be in conflict? Why it's not good? I'm not sure I've understood, but I think it's more or less the same with the native counterpart: if you install x11/nvidia-driver, libGL.so from graphics/libGL get replaced (actually renamed). Because if port B replaces a file from port A, then when port A is deinstalled, the file from the ports B is removed. WBR -- bsam ___ 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 admission request
On Sun, 7 Jun 2009 22:27:16 +0300 Eugen-Andrei Gavriloaie shir...@gmail.com wrote: Hi, I would like to bring to your attention my project hosted here: http://www.rtmpd.com I know how Adobe is keep ignoring our request of having a flash player for FreeBSD. I though that at least we have another decent C++ implementation of a media server. This is an under development project but is usable in his current (trunk) state. Let me know if you can/want to add it in the ports If you make a port for it I see no problem in adding it. I can give you a hand with writing the port. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
math/fftw3 distinfo incorrect
Hi, The latest bump to math/fftw3 from 3.2 to 3.2.1 missed the distinfo changes, which still references fftw-3.2.tar.gz. Cheers. -- Jonathan Chen j...@chen.org.nz -- When you don't know what you are doing, do it neatly. ___ 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: [x11/nvidia-driver] conflicts with linux dri ports
On Mon, 08 Jun 2009 00:06:56 +0400 Boris Samorodov b...@ipt.ru wrote: On Sun, 7 Jun 2009 21:34:53 +0200 barbara wrote: I've just received a report at emulation@ about x11/nvidia-driver and other linux dri ports to be in conflict. If a linux dri port is installed x11/nvidia-driver seems to replace libGL.so with a link to nvidia library. Not good. Is it right to mark this port and other linux dri ports to be in conflict? Why it's not good? I'm not sure I've understood, but I think it's more or less the same with the native counterpart: if you install x11/nvidia-driver, libGL.so from graphics/libGL get replaced (actually renamed). Because if port B replaces a file from port A, then when port A is deinstalled, the file from the ports B is removed. It's not ideal, but making nvidia-driver conflict with its own dependencies is a lot worse. ___ 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 build failed for 6.x
INDEX build failed with errors: Generating INDEX-6 - please wait..pkg_info: not found pkg_info: not found pkg_info: not found pkg_info: not found Done. make_index: epplets-0.12: no entry for /usr/ports/x11-wm/enlightenment make_index: epplets-0.12: no entry for /usr/ports/x11-wm/enlightenment make_index: enlightenment-docs-0.16.8.0.2: no entry for /usr/ports/x11-wm/enlightenment Committers on the hook: amdmi3 gahr pav pgollucci Most recent CVS update was: ports/MOVED ports/databases/rubygem-memcache-client/Makefile ports/databases/rubygem-memcache-client/distinfo ports/devel/rubygem-hoe/Makefile ports/devel/rubygem-hoe/distinfo ports/games/Makefile ports/games/flyhard/Makefile ports/games/flyhard/distinfo ports/games/flyhard/pkg-plist ports/lang/harbour/Makefile ports/mail/p5-qpsmtpd/Makefile ports/mail/p5-qpsmtpd/distinfo ports/math/fftw3/distinfo ports/x11-themes/e16-themes/Makefile ports/x11-themes/e16-themes/distinfo ports/x11-themes/e16-themes/pkg-plist ports/x11-wm/Makefile ports/x11-wm/e16/Makefile ports/x11-wm/e16/distinfo ports/x11-wm/e16/pkg-descr ports/x11-wm/e16/pkg-plist ___ 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: Is fetching source RPMs in linux ports really required?
* M. Warner Losh (i...@bsdimp.com) wrote: I don't think that GPLv2 section 3c applies because we've not received an section 3b offer to redistribute. Instead, the RPMs are provided under section 3a. The FSF made a big deal about this not being sufficient a while ago. Oh, after reading it more thoughtfully I think you're right, sorry for the noise. GPL3, however, still seems to not require this. -- 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
INDEX build failed for 6.x
INDEX build failed with errors: Generating INDEX-6 - please wait..pkg_info: not found pkg_info: not found pkg_info: not found pkg_info: not found Done. make_index: epplets-0.12: no entry for /usr/ports/x11-wm/enlightenment make_index: epplets-0.12: no entry for /usr/ports/x11-wm/enlightenment make_index: enlightenment-docs-0.16.8.0.2: no entry for /usr/ports/x11-wm/enlightenment Committers on the hook: amdmi3 lippe pgollucci Most recent CVS update was: ports/devel/apr/Makefile ports/devel/apr/distinfo ports/devel/apr/files/patch-apr_hints.m4 ports/devel/apr/pkg-plist ports/devel/p5-threads-shared/Makefile ports/devel/p5-threads-shared/distinfo ports/net-mgmt/rancid/Makefile ports/net-mgmt/rancid/distinfo ports/net-mgmt/rancid/files/patch-etc::Makefile.am ports/net-mgmt/rancid/files/patch-etc::Makefile.in ports/net-mgmt/rancid/pkg-plist ports/security/vuxml/vuln.xml ports/textproc/rubygem-nokogiri/Makefile ports/textproc/rubygem-nokogiri/distinfo ports/www/hiawatha/Makefile ports/www/hiawatha/distinfo ports/www/hiawatha/pkg-plist ___ 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
