Re: FreeBSD Port: smalltalk-3.0.5
per...@pluto.rain.com wrote: Given the backwards compatibility issues, might it be worthwhile to create a new smalltalk31 or smalltalk-devel port, or rename the current port to something like smalltalk30x, so that the older version can remain available for use with older programs? Well, 3.1 is not really a development branch: it is clearly intended to be the next stable branch. The first release might not have been perfect, but the author has made it clear that 3.1 is 'the way forward' and that the 3.0 branch will be discontinued. I will happily make a separate branch if there is even one smalltalk user who wants to keep 3.0.x around (if you read this: please respond). But otherwise I'm inclined to just drop 3.0 in the near future and let people convert their programs. For those interested, check out the 'Incompatible changes' section on http://smalltalk.gnu.org/news/gnu-smalltalk-3-1 Regards, Johan pgp25jcxuIOOp.pgp Description: PGP signature
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: 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: 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: none. 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/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: editors/xml2rfc-xxe broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=editorsportname=xml2rfc-xxe 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: 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: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=pixieplus portname: graphics/ray++ broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=ray%2B%2B portname: japanese/okphone broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=japaneseportname=okphone portname: japanese/oleo broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=japaneseportname=oleo portname: japanese/tkstep80 broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=japaneseportname=tkstep80 portname: java/openjit broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=javaportname=openjit portname: java/tya broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=javaportname=tya portname:
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/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/muine broken because: doesn't build and is apparently unmaintained build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=muine 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.bz2 (_Mar_26_08:21:12_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=cadportname=alliance portname: chinese/gbk2uni broken because: does not fetch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=gbk2uni 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/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: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=erserver portname: databases/libgda4-jdbc broken because: does not configure build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=libgda4-jdbc portname: databases/libpbl broken because: does not work with databases ~200 MB (see ports/130236) build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=libpbl 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: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=agide portname: devel/cocktail broken because: Segfault during build on FreeBSD = 7.0 build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.7.20090711083149/cocktail-9309_1.log.bz2 (_Jun__3_14:04:39_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=cocktail portname: devel/fampp broken because: FAM system mismatch: gamin is installed, while desired FAM system is fam 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: devel/p5-Algorithm-MDiff description:Perl interface to calculate m-difference between two objects maintainer: po...@freebsd.org deprecated because: the module was removed from CPAN expiration date:2009-09-09 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=p5-Algorithm-MDiff portname: devel/p5-Data-Postponed description:Delay the evaluation of expressions to allow changes to variables maintainer: po...@freebsd.org deprecated because: the module was removed from CPAN expiration date:2009-09-09 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=p5-Data-Postponed portname: games/amy description:A chess program for playing and analyzing games maintainer: po...@freebsd.org status: BROKEN deprecated because: mastersite disappeared, does not build on recent version expiration date:2009-07-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=gamesportname=amy portname: lang/tinycobol description:A tiny COBOL compiler for IA32 platforms maintainer: po...@freebsd.org status: BROKEN deprecated because: no longer being developed; consider using lang/open-cobol instead expiration date:2009-07-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=langportname=tinycobol portname: math/freefem++ description:An implementation of a language dedicated to the finite element method maintainer: po...@freebsd.org deprecated because: fails to compile with up-to-date compilers, nobody really interested expiration date:2009-08-20 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=mathportname=freefem%2B%2B portname: math/it++ description:Mathematical, signal processing and communication library maintainer: po...@freebsd.org deprecated because: fails to compile with up-to-date compilers, nobody really interested to maintain this expiration date:2009-08-20 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=mathportname=it%2B%2B portname: net-mgmt/net-snmp4 description:An extendable SNMP implementation maintainer: po...@freebsd.org 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-mgmtportname=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-mgmtportname=p5-SNMP portname: security/hashish description:GUI file and string hashing utility maintainer: po...@freebsd.org status: BROKEN deprecated because: does not compile expiration date:2009-07-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=securityportname=hashish 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=wwwportname=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
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: databases/firebird-client description:The open-source InterBase(tm) 6.0 spin-off (client) maintainer: s...@freebsd.org status: IGNORE deprecated because: no longer under development, please consider using Firebird2 expiration date:2009-02-24 build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.6.20090708085814/firebird-client-1.5.5.log.bz2 (_May_29_05:56:50_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=firebird-client portname: databases/firebird-server description:The open-source InterBase(tm) 6.0 spin-off (Classic version) maintainer: s...@freebsd.org status: IGNORE deprecated because: no longer under development, please consider using Firebird2 expiration date:2009-02-24 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=firebird-server portname: devel/p5-Algorithm-MDiff description:Perl interface to calculate m-difference between two objects maintainer: po...@freebsd.org deprecated because: the module was removed from CPAN expiration date:2009-09-09 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=p5-Algorithm-MDiff portname: devel/p5-Data-Postponed description:Delay the evaluation of expressions to allow changes to variables maintainer: po...@freebsd.org deprecated because: the module was removed from CPAN expiration date:2009-09-09 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=p5-Data-Postponed portname: games/amy description:A chess program for playing and analyzing games maintainer: po...@freebsd.org status: BROKEN deprecated because: mastersite disappeared, does not build on recent version expiration date:2009-07-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=gamesportname=amy portname: lang/tinycobol description:A tiny COBOL compiler for IA32 platforms maintainer: po...@freebsd.org status: BROKEN deprecated because: no longer being developed; consider using lang/open-cobol instead expiration date:2009-07-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=langportname=tinycobol portname: math/freefem++ description:An implementation of a language dedicated to the finite element method maintainer: po...@freebsd.org deprecated because: fails to compile with up-to-date compilers, nobody really interested expiration date:2009-08-20 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=mathportname=freefem%2B%2B portname: math/it++ description:Mathematical, signal processing and communication library maintainer: po...@freebsd.org deprecated because: fails to compile with up-to-date compilers, nobody really interested to maintain this expiration date:2009-08-20 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=mathportname=it%2B%2B portname: net-mgmt/net-snmp4 description:An extendable SNMP implementation maintainer: po...@freebsd.org 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-mgmtportname=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:
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=miscportname=compat3x 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: 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: net/isc-dhcp30-client forbidden because: http://vuxml.FreeBSD.org/c444c8b7-7169-11de-9ab7-000c29a67389.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=netportname=isc-dhcp30-client 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
Re: libmapi new port request
Could someone please make a port for libmapi? http://www.openchange.org http://downloads.sourceforge.net/openchange/libmapi-0.8.2-ROMULUS.tar.gz Sandra I got it almost ready for commit :) Just wait a little bit while I find time to clean it up. You're still working on it? Sandra ___ 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
Unable to build /x11/kdelibs3 with updated jpeg-7 port
It appears that the /x11/kdelibs3 ports insists on using the older libjpeg.so.9 library. Since updating to jpeg-7, this library is no-longer available. Therefore, I cannot build this port. A complete copy of the build log is available here: http://filebin.ca/yrdvkw/kdelibs.log -- Jerry ges...@yahoo.com Quigley's Law: Whoever has any authority over you, no matter how small, will attempt to use 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: Unable to build /x11/kdelibs3 with updated jpeg-7 port
On Tuesday 21 July 2009 12:40:34 Jerry wrote: It appears that the /x11/kdelibs3 ports insists on using the older libjpeg.so.9 library. Since updating to jpeg-7, this library is no-longer available. Therefore, I cannot build this port. A complete copy of the build log is available here: http://filebin.ca/yrdvkw/kdelibs.log There is notice in UPDATING, section 20090719, I found temporary workaround ln -s /usr/local/lib/libjpeg.so.10 /usr/local/lib/libjpeg.so.9 After that, all my ports seems to work again. I am rebuilding kdelibs, kdebase and kdepim right now (most used apps in my case). Regards, Milan ___ 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
misc/e2fsprogs-libuuid should be MAKE_JOBS_UNSAFE
I think that misc/e2fsprogs-libuuid should be MAKE_JOBS_UNSAFE. If I build the latest version of this port (tree updated yesterday) with default options (no special variables in make.conf) on a multi-CPU machine, then it fails with error similar to the following: cd ./util ; gmake subst gmake[1]: Entering directory `/usr/obj/ports/usr/ports/misc/e2fsprogs-libuuid/work/e2fsprogs-1.41.8/util' CC subst.c ... gmake[2]: Entering directory `/usr/obj/ports/usr/ports/misc/e2fsprogs-libuuid/work/e2fsprogs-1.41.8/util' LD subst subst.o: file not recognized: File truncated gmake[2]: *** [subst] Error 1 ... If I specify DISABLE_MAKE_JOBS=1 then the build proceeds. P.S. Makefile of misc/e2fsprogs-libuuid doesn't have an explicit MAINTAINER line, so I assume that it has the same maintainer as its master port misc/e2fsprogs. -- Andriy Gapon ___ 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: error updating Postfix
On Tue, Jul 21, 2009 at 12:00:47AM -0400, Sahil Tandon wrote:
On Tue, 21 Jul 2009, Per olof Ljungmark wrote:
Wesley Shields wrote:
On Tue, Jul 21, 2009 at 12:23:16AM +0200, Per olof Ljungmark wrote:
cc -DDEF_CONFIG_DIR=\/usr/local/etc/postfix\
-DDEF_DAEMON_DIR=\/usr/local/libexec/postfix\
-DDEF_COMMAND_DIR=\/usr/local/sbin\
-DDEF_SENDMAIL_PATH=\/usr/local/sbin/sendmail\
-DDEF_NEWALIAS_PATH=\/usr/local/bin/newaliases\
-DDEF_MAILQ_PATH=\/usr/local/bin/mailq\
-DDEF_MANPAGE_DIR=\/usr/local/man\
-DDEF_README_DIR=\/usr/local/share/doc/postfix\
-DDEF_HTML_DIR=\/usr/local/share/doc/postfix\
-DDEF_QUEUE_DIR=\/var/spool/postfix\
-DDEF_DATA_DIR=\/var/db/postfix\ -DDEF_MAIL_OWNER=\postfix\
-DDEF_SGID_GROUP=\maildrop\ -DHAS_PCRE -I/usr/local/include
-DUSE_SASL_AUTH -DUSE_CYRUS_SASL -I/usr/local/include
-I/usr/local/include/sasl -DUSE_TLS -I/usr/include -O2
-fno-strict-aliasing -pipe -I. -DFREEBSD7 -c attr_clnt.c
In file included from attr_clnt.c:77:
/usr/include/unistd.h:329: error: conflicting types for 'closefrom'
./sys_defs.h:1404: error: previous declaration of 'closefrom' was here
*** Error code 1
It was fixed on 2009/07/09. Make sure you have the latest ports tree.
Hm, I updated an hour ago... from cvsup.FreeBSD.org, the makefile is
dated July 17th when the system was also updated.
7.2-STABLE FreeBSD 7.2-STABLE #0: Fri Jul 17 17:27:43 CEST 2009
Just for the sake of it I cvsupped again just now to be sure but no
change. What was fixed in the 9th.? I obviously need to check if
something went wrong when I updated the system.
On 9 Jul 2009, ports/136599 fixed build on 8.0 systems. Now that the
closefrom() system call has been MFC'd to -STABLE, a similar patch is
required for mail/postfix. This was broached on cvs-ports@ on 17 Jul 2009
and keramida@ was testing a patch over the weekend. I've copied him on
this message. For context (and an example of all that is really needed in
${WRKSRC}/src/util/sys_defs.h), see:
Ah, I didn't realize the fix had been MFC'ed and that the machine in
question was RELENG_7. That explains it. Hopefully keramida@ has time to
commit it.
Sorry for the noise.
-- WXS
___
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: Cacti installation error
On Tue, 2009-07-21 at 20:14 +0800, Romeo Paras wrote: I already free some spaces and when I tried it again by running ' make install clean' i received these errors; cacti-0.8.7e depends on file: /usr/local/lib/php/20060613/session.so - found === cacti-0.8.7e depends on file: /usr/local/lib/php/20060613/sockets.so - found === cacti-0.8.7e depends on file: /usr/local/lib/php/20060613/snmp.so - found === cacti-0.8.7e depends on file: /usr/local/lib/php/20060613/xml.so - found === cacti-0.8.7e depends on shared library: mysqlclient.15 - found cacti:*:107: You already have a group cacti, so I will use it. pw: user 'cacti' already exists Adding user cacti failed... *** Error code 1 stop at /usr/ports/net-mgmt/cacti what will I do next? thanks Try freebsd-ports@, this doesn't seem to be related to X11 at all. The error message seems to be that it failed to add the user because it already exists - perhaps try removing the user and retrying the installation. Cheers Tom ___ 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: error updating Postfix
On Tue, 21 Jul 2009 09:26:50 -0400, Wesley Shields w...@freebsd.org wrote:
On 9 Jul 2009, ports/136599 fixed build on 8.0 systems. Now that the
closefrom() system call has been MFC'd to -STABLE, a similar patch is
required for mail/postfix. This was broached on cvs-ports@ on 17 Jul
2009 and keramida@ was testing a patch over the weekend. I've copied
him on this message. For context (and an example of all that is
really needed in ${WRKSRC}/src/util/sys_defs.h), see:
Ah, I didn't realize the fix had been MFC'ed and that the machine in
question was RELENG_7. That explains it. Hopefully keramida@ has time
to commit it.
I can commit it _now_. I just haven't had a chance to build on a very
recent stable/7 system (my 'build machine' is a Celeron and it has taken
already 2 days to build RELENG_7). If someone else has a recent
7-STABLE system and can test the patch please do. The latest version of
7.X I have access to right now is ref7.freebsd.org with:
FreeBSD 7.2-STABLE (REF7-AMD64) #6 r194101M: Sat Jun 13 09:51:42 UTC 2009
___
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: misc/e2fsprogs-libuuid should be MAKE_JOBS_UNSAFE
* Andriy Gapon (a...@icyb.net.ua) wrote: I think that misc/e2fsprogs-libuuid should be MAKE_JOBS_UNSAFE. If I build the latest version of this port (tree updated yesterday) with default options (no special variables in make.conf) on a multi-CPU machine, then it fails with error similar to the following: cd ./util ; gmake subst gmake[1]: Entering directory `/usr/obj/ports/usr/ports/misc/e2fsprogs-libuuid/work/e2fsprogs-1.41.8/util' CC subst.c ... gmake[2]: Entering directory `/usr/obj/ports/usr/ports/misc/e2fsprogs-libuuid/work/e2fsprogs-1.41.8/util' LD subst subst.o: file not recognized: File truncated gmake[2]: *** [subst] Error 1 ... A fix for this was recently added. Does the updated port show the same bahavior? P.S. Makefile of misc/e2fsprogs-libuuid doesn't have an explicit MAINTAINER line, so I assume that it has the same maintainer as its master port misc/e2fsprogs. Yes it is, you can `make -VMAINTAINER` there. -- 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: error updating Postfix
On Tue, Jul 21, 2009 at 05:56:29PM +0300, Giorgos Keramidas wrote:
On Tue, 21 Jul 2009 09:26:50 -0400, Wesley Shields w...@freebsd.org wrote:
On 9 Jul 2009, ports/136599 fixed build on 8.0 systems. Now that the
closefrom() system call has been MFC'd to -STABLE, a similar patch is
required for mail/postfix. This was broached on cvs-ports@ on 17 Jul
2009 and keramida@ was testing a patch over the weekend. I've copied
him on this message. For context (and an example of all that is
really needed in ${WRKSRC}/src/util/sys_defs.h), see:
Ah, I didn't realize the fix had been MFC'ed and that the machine in
question was RELENG_7. That explains it. Hopefully keramida@ has time
to commit it.
I can commit it _now_. I just haven't had a chance to build on a very
recent stable/7 system (my 'build machine' is a Celeron and it has taken
already 2 days to build RELENG_7). If someone else has a recent
7-STABLE system and can test the patch please do. The latest version of
7.X I have access to right now is ref7.freebsd.org with:
FreeBSD 7.2-STABLE (REF7-AMD64) #6 r194101M: Sat Jun 13 09:51:42 UTC 2009
If you send me the patch I'll test it on a RELENG_7 tinderbox jail built
a day or two ago.
-- WXS
___
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/boost: request for an exp-run
Hi Pav! Did you manage to start an exp-run? I'd like to start fixing issues as soon as possible, if there are any. Looks like we have chances for the boost-1.39 to be included in 8.0. Sincerely, Alexander Churanov 2009/7/15 Pav Lucistnik p...@freebsd.org: Okay Alexander Churanov píše v st 15. 07. 2009 v 19:58 +0400: Folks, I've created an updated version of boost ports that fixes almost all issues reported after an exp-run. Please, make another exp-run, if possible. The updated diff is at http://alexanderchuranov.com/boost-port/boost-2009-07-14-15-33.diff The updated tarball is at http://alexanderchuranov.com/boost-port/boost-ports-20090710.tar.bz2 The procedure is as follows: 1) Download the tarball and unpack under /usr/ports/devel 2) Go to /usr/ports, download and apply the patch 3) Remove 'devel/boost' and 'devel/boost-python' ports 4) Rebuild ports Sincerely, Alexander Churanov, maintainer of devel/boost-* -- Pav Lucistnik p...@oook.cz p...@freebsd.org Orfax's hip flask contained Old Janx Spirit, a mixture of potions of stupidity, paralysis, naivery, ruination, lose memories, confusion, and slime mold juice, with a twist of lemon. - from a post on Angband Community Forum ___ 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 Port: mplayer-0.99.11_14
Is there an update available for mplayer? The current version at http://www.mplayerhq.hu seems to imply a 1.0 version. We're having problems with this error, that is likely corrected in a version greater than 0.99.11_14: vmbsd02# /usr/local/bin/mencoder rtsp://root:p...@172.28.10.65/mpeg4/media.amp -ovc copy -o /tmp/mike.mpeg4 MEncoder 1.0rc2-4.2.1 (C) 2000-2007 MPlayer Team CPU: Intel(R) Xeon(R) CPU X5570 @ 2.93GHz (Family: 6, Model: 26, Stepping: 8) CPUflags: Type: 6 MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 1 Compiled with runtime CPU detection. Connecting to server 172.28.10.65[172.28.10.65]: 554... librtsp: server responds: 'RTSP/1.0 401 Unauthorized' rtsp_session: unsupported RTSP server. Server type is 'unknown'. STREAM_LIVE555, URL: rtsp://root:p...@172.28.10.65/mpeg4/media.amp success: format: 21 data: 0x0 - 0x0 Stream not seekable! file format detected. Initiated video/MP4V-ES RTP subsession on port 51198 VIDEO: [mp4v] 0x0 0bpp 6.000 fps0.0 kbps ( 0.0 kbyte/s) [V] filefmt:21 fourcc:0x7634706D size:0x0 fps: 6.00 ftime:=0.1667 videocodec: framecopy (0x0 0bpp fourcc=7634706d) MultiFramedRTPSource::doGetNextFrame1(): The total received frame size exceeds the client's buffer size (5). 1100 bytes of trailing data will be dropped! Saw an input frame too large (=5). Increase MAX_RTP_FRAME_SIZE in demux_rtp.cpp. Writing header... ODML: Aspect information not (yet?) available or unspecified, not writing vprp header. Writing header... ODML: Aspect information not (yet?) available or unspecified, not writing vprp header. MultiFramedRTPSource::doGetNextFrame1(): The total received frame size exceeds the client's buffer size (5). 1100 bytes of trailing data will be dropped! Saw an input frame too large (=5). Increase MAX_RTP_FRAME_SIZE in demux_rtp.cpp. MultiFramedRTPSource::doGetNextFrame1(): The total received frame size exceeds the client's buffer size (5). 1100 bytes of trailing data will be dropped! Saw an input frame too large (=5). Increase MAX_RTP_FRAME_SIZE in demux_rtp.cpp. MultiFramedRTPSource::doGetNextFrame1(): The total received frame size exceeds the client's buffer size (5). 1100 bytes of trailing data will be dropped! Saw an input frame too large (=5). Increase MAX_RTP_FRAME_SIZE in demux_rtp.cpp. MultiFramedRTPSource::doGetNextFrame1(): The total received frame size exceeds the client's buffer size (5). 1100 bytes of trailing data will be dropped! Saw an input frame too large (=5). Increase MAX_RTP_FRAME_SIZE in demux_rtp.cpp. Any suggestions would be appreciated. Thanks! Michael D. Stackhouse SAMSA, Inc. 989-790-0507 Saginaw, MI USA www.samsa.com samsaisgreat ___ 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: error updating Postfix
Giorgos Keramidas wrote:
On Tue, 21 Jul 2009 09:26:50 -0400, Wesley Shields w...@freebsd.org wrote:
On 9 Jul 2009, ports/136599 fixed build on 8.0 systems. Now that the
closefrom() system call has been MFC'd to -STABLE, a similar patch is
required for mail/postfix. This was broached on cvs-ports@ on 17 Jul
2009 and keramida@ was testing a patch over the weekend. I've copied
him on this message. For context (and an example of all that is
really needed in ${WRKSRC}/src/util/sys_defs.h), see:
Ah, I didn't realize the fix had been MFC'ed and that the machine in
question was RELENG_7. That explains it. Hopefully keramida@ has time
to commit it.
I can commit it _now_. I just haven't had a chance to build on a very
recent stable/7 system (my 'build machine' is a Celeron and it has taken
already 2 days to build RELENG_7). If someone else has a recent
7-STABLE system and can test the patch please do. The latest version of
7.X I have access to right now is ref7.freebsd.org with:
FreeBSD 7.2-STABLE (REF7-AMD64) #6 r194101M: Sat Jun 13 09:51:42 UTC 2009
I can test it as well...
___
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/boost: request for an exp-run
Hi Alexander, unfortunately no, as pointyhat has been busy with other patches. Suddenly everyone wants to get their changes in before 8.0-RELEASE. Alexander Churanov píše v út 21. 07. 2009 v 19:50 +0400: Hi Pav! Did you manage to start an exp-run? I'd like to start fixing issues as soon as possible, if there are any. Looks like we have chances for the boost-1.39 to be included in 8.0. Sincerely, Alexander Churanov 2009/7/15 Pav Lucistnik p...@freebsd.org: Okay Alexander Churanov píše v st 15. 07. 2009 v 19:58 +0400: Folks, I've created an updated version of boost ports that fixes almost all issues reported after an exp-run. Please, make another exp-run, if possible. The updated diff is at http://alexanderchuranov.com/boost-port/boost-2009-07-14-15-33.diff The updated tarball is at http://alexanderchuranov.com/boost-port/boost-ports-20090710.tar.bz2 The procedure is as follows: 1) Download the tarball and unpack under /usr/ports/devel 2) Go to /usr/ports, download and apply the patch 3) Remove 'devel/boost' and 'devel/boost-python' ports 4) Rebuild ports Sincerely, Alexander Churanov, maintainer of devel/boost-* -- Pav Lucistnik p...@oook.cz p...@freebsd.org Orfax's hip flask contained Old Janx Spirit, a mixture of potions of stupidity, paralysis, naivery, ruination, lose memories, confusion, and slime mold juice, with a twist of lemon. - from a post on Angband Community Forum -- Pav Lucistnik p...@oook.cz p...@freebsd.org Pain clots and unformed lice pat this train. signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: Cacti installation error
Tom Evans пишет:
On Tue, 2009-07-21 at 20:14 +0800, Romeo Paras wrote:
I already free some spaces and when I tried it again by running ' make
install clean' i received these errors;
cacti-0.8.7e depends on file: /usr/local/lib/php/20060613/session.so - found
=== cacti-0.8.7e depends on file: /usr/local/lib/php/20060613/sockets.so -
found
=== cacti-0.8.7e depends on file: /usr/local/lib/php/20060613/snmp.so -
found
=== cacti-0.8.7e depends on file: /usr/local/lib/php/20060613/xml.so -
found
=== cacti-0.8.7e depends on shared library: mysqlclient.15 - found
cacti:*:107:
You already have a group cacti, so I will use it.
pw: user 'cacti' already exists
Adding user cacti failed...
*** Error code 1
stop at /usr/ports/net-mgmt/cacti
what will I do next? thanks
Try freebsd-ports@, this doesn't seem to be related to X11 at all.
The error message seems to be that it failed to add the user because it
already exists - perhaps try removing the user and retrying the
installation.
It should be happened really:
if ${PW} user show ${CACTIUSER} 2/dev/null; then
echo You already have a user \${CACTIUSER}\, so I
will use it
.
else
if ${PW} useradd ${CACTIUSER} -u ${UID} -g
${CACTIGROUP} -h - \
-d /nonexistent -s /sbin/nologin -c Cacti
Sandbox
then
echo Added user \${CACTIUSER}\.
else
echo Adding user \${CACTIUSER}\ failed...
exit 1
fi
fi
What FreeBSD version you use?
--
Dixi.
Sem.
___
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
Future of portupgrade
Hi. As you probably know, I've maintained portupgrade for the last three years. Unfortunately my free time dramatically decreased and about half year I did for portupgrade really little. I did not want to leave portupgrade unmaintained and after a discussion with stas@ I've decided to pass maintainership to ruby@ team. Thanks all for your patches, wishes and questions you sent me to make portupgrade better. I hope our ruby team will able care about it. -- Dixi. Sem. ___ 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 : Future of portupgrade
Thanx D. Sem. and we hope you will do more than portupgrade some next time if available. cheers, Coko Tracy MIRINDI M. IT Consultant/CTO BSDcongo mobiles: +250 78 349 5797 RWANDA, +243 81 413 6055 RDC --- En date de : Mar 21.7.09, Sergey Matveychuk s...@freebsd.org a écrit : De: Sergey Matveychuk s...@freebsd.org Objet: Future of portupgrade À: po...@freebsd.org Cc: r...@freebsd.org Date: Mardi 21 Juillet 2009, 22h44 Hi. As you probably know, I've maintained portupgrade for the last three years. Unfortunately my free time dramatically decreased and about half year I did for portupgrade really little. I did not want to leave portupgrade unmaintained and after a discussion with stas@ I've decided to pass maintainership to ruby@ team. Thanks all for your patches, wishes and questions you sent me to make portupgrade better. I hope our ruby team will able care about it. -- Dixi. Sem. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: error updating Postfix
Giorgos Keramidas wrote: I can commit it _now_. I just haven't had a chance to build on a very recent stable/7 system (my 'build machine' is a Celeron and it has taken already 2 days to build RELENG_7). If someone else has a recent 7-STABLE system and can test the patch please do. The latest version of 7.X I have access to right now is ref7.freebsd.org with: FreeBSD 7.2-STABLE (REF7-AMD64) #6 r194101M: Sat Jun 13 09:51:42 UTC 2009 Those of you with slower machines, have you considered ccache? I cant imagine a 2 day build time, a k6-2 450 I still use takes about 8-9 hours without cache to build 6.stable, is that like a celeron 266 with like 64 megs of ram or sumthin? Brian ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: mplayer-0.99.11_14
On Tue, Jul 21, 2009 at 12:51 PM, Michael D. Stackhouse mstackho...@samsa.com wrote: Is there an update available for mplayer? The current version at http://www.mplayerhq.hu seems to imply a 1.0 version. We're having problems with this error, that is likely corrected in a version greater than 0.99.11_14: vmbsd02# /usr/local/bin/mencoder rtsp://root:p...@172.28.10.65/mpeg4/media.amp -ovc copy -o /tmp/mike.mpeg4 MEncoder 1.0rc2-4.2.1 (C) 2000-2007 MPlayer Team CPU: Intel(R) Xeon(R) CPU X5570 @ 2.93GHz (Family: 6, Model: 26, Stepping: 8) CPUflags: Type: 6 MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 1 Compiled with runtime CPU detection. Connecting to server 172.28.10.65[172.28.10.65]: 554... librtsp: server responds: 'RTSP/1.0 401 Unauthorized' rtsp_session: unsupported RTSP server. Server type is 'unknown'. STREAM_LIVE555, URL: rtsp://root:p...@172.28.10.65/mpeg4/media.amp success: format: 21 data: 0x0 - 0x0 Stream not seekable! file format detected. Initiated video/MP4V-ES RTP subsession on port 51198 VIDEO: [mp4v] 0x0 0bpp 6.000 fps0.0 kbps ( 0.0 kbyte/s) [V] filefmt:21 fourcc:0x7634706D size:0x0 fps: 6.00 ftime:=0.1667 videocodec: framecopy (0x0 0bpp fourcc=7634706d) MultiFramedRTPSource::doGetNextFrame1(): The total received frame size exceeds the client's buffer size (5). 1100 bytes of trailing data will be dropped! Saw an input frame too large (=5). Increase MAX_RTP_FRAME_SIZE in demux_rtp.cpp. Writing header... ODML: Aspect information not (yet?) available or unspecified, not writing vprp header. Writing header... ODML: Aspect information not (yet?) available or unspecified, not writing vprp header. MultiFramedRTPSource::doGetNextFrame1(): The total received frame size exceeds the client's buffer size (5). 1100 bytes of trailing data will be dropped! Saw an input frame too large (=5). Increase MAX_RTP_FRAME_SIZE in demux_rtp.cpp. MultiFramedRTPSource::doGetNextFrame1(): The total received frame size exceeds the client's buffer size (5). 1100 bytes of trailing data will be dropped! Saw an input frame too large (=5). Increase MAX_RTP_FRAME_SIZE in demux_rtp.cpp. MultiFramedRTPSource::doGetNextFrame1(): The total received frame size exceeds the client's buffer size (5). 1100 bytes of trailing data will be dropped! Saw an input frame too large (=5). Increase MAX_RTP_FRAME_SIZE in demux_rtp.cpp. MultiFramedRTPSource::doGetNextFrame1(): The total received frame size exceeds the client's buffer size (5). 1100 bytes of trailing data will be dropped! Saw an input frame too large (=5). Increase MAX_RTP_FRAME_SIZE in demux_rtp.cpp. Any suggestions would be appreciated. Thanks! Michael D. Stackhouse SAMSA, Inc. 989-790-0507 Saginaw, MI USA www.samsa.com samsaisgreat ___ 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 Considering that mplayer no longer does stable releases you would have to switch the makefile to use svn to get an updated mplayer ___ 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
