Unable to install new dialog for ports on FreeBsd 7.0
Hi all, After updating portsnap I tried to install php5. Now make config fails with following error: === Building for dialog4ports-0.1 Warning: Object directory not changed from original /usr/ports/ports-mgmt/dialog4ports/wor k/dialog4ports-0.1 cc -O2 -fno-strict-aliasing -pipe -I/usr/ports/ports-mgmt/dialog4ports/work/dialog-1.1-20 120706 -D_XOPEN_SOURCE_EXTENDED -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unu sed-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -o dialog4ports dialog4ports.o mixedlist.o arrows.o buttons.o dlg_keys. o help.o inputstr.o mouse.o mousewget.o textbox.o rc.o trace.o ui_getc.o util.o version.o -lncursesw util.o(.text+0x2e02): In function `dlg_auto_size': : undefined reference to `sqrt' *** Error code 1 1 error *** Error code 1 Stop in /usr/ports/ports-mgmt/dialog4ports. If I set NO_DIALOG=yes in /etc/make.conf, I am getting: === Skipping 'config' as NO_DIALOG is defined How can solve this problem? Any way to fix this error or using old make config dialog. Please help. -- Thanks Vikas Mahajan ___ 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 install new dialog for ports on FreeBsd 7.0
On Thu, Mar 21, 2013 at 11:39:07AM +0530, Vikas Mahajan wrote: Hi all, After updating portsnap I tried to install php5. Now make config fails with following error: === Building for dialog4ports-0.1 Warning: Object directory not changed from original /usr/ports/ports-mgmt/dialog4ports/wor k/dialog4ports-0.1 cc -O2 -fno-strict-aliasing -pipe -I/usr/ports/ports-mgmt/dialog4ports/work/dialog-1.1-20 120706 -D_XOPEN_SOURCE_EXTENDED -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unu sed-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -o dialog4ports dialog4ports.o mixedlist.o arrows.o buttons.o dlg_keys. o help.o inputstr.o mouse.o mousewget.o textbox.o rc.o trace.o ui_getc.o util.o version.o -lncursesw util.o(.text+0x2e02): In function `dlg_auto_size': : undefined reference to `sqrt' *** Error code 1 1 error *** Error code 1 Stop in /usr/ports/ports-mgmt/dialog4ports. If I set NO_DIALOG=yes in /etc/make.conf, I am getting: === Skipping 'config' as NO_DIALOG is defined How can solve this problem? Any way to fix this error or using old make config dialog. Please help. Try replacing the ports-mgmt/pkg/files/patch-Makefile by this one: http://people.freebsd.org/~bapt/patch-Makefile And tell me if it works. But please notice that 7.x is EOLed 28 feb, more and more the ports tree will get incompatible, and if we want to follow the direction for FreeBSD 10 (replace our make by bmake) we will need to a day or another break totally compatibility with 7. Consider upgrading your boxes. regards, Bapt pgpComOWAPYWI.pgp Description: PGP signature
Re: Unable to install new dialog for ports on FreeBsd 7.0
On Thu, 21 Mar 2013 08:56:34 +0100 Baptiste Daroussin b...@freebsd.org wrote: On Thu, Mar 21, 2013 at 11:39:07AM +0530, Vikas Mahajan wrote: Hi all, After updating portsnap I tried to install php5. Now make config fails with following error: === Building for dialog4ports-0.1 Warning: Object directory not changed from original /usr/ports/ports-mgmt/dialog4ports/wor k/dialog4ports-0.1 cc -O2 -fno-strict-aliasing -pipe -I/usr/ports/ports-mgmt/dialog4ports/work/dialog-1.1-20 120706 -D_XOPEN_SOURCE_EXTENDED -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unu sed-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -o dialog4ports dialog4ports.o mixedlist.o arrows.o buttons.o dlg_keys. o help.o inputstr.o mouse.o mousewget.o textbox.o rc.o trace.o ui_getc.o util.o version.o -lncursesw util.o(.text+0x2e02): In function `dlg_auto_size': : undefined reference to `sqrt' *** Error code 1 1 error *** Error code 1 Stop in /usr/ports/ports-mgmt/dialog4ports. If I set NO_DIALOG=yes in /etc/make.conf, I am getting: === Skipping 'config' as NO_DIALOG is defined How can solve this problem? Any way to fix this error or using old make config dialog. Please help. Try replacing the ports-mgmt/pkg/files/patch-Makefile by this one: http://people.freebsd.org/~bapt/patch-Makefile And tell me if it works. But please notice that 7.x is EOLed 28 feb, more and more the ports tree will get incompatible, and if we want to follow the direction for FreeBSD 10 (replace our make by bmake) we will need to a day or another break totally compatibility with 7. Consider upgrading your boxes. but ports/tags/RELEASE_7_EOL will not be broken for 7.x ? regards, Bapt -- wbr, tiger ___ 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 install new dialog for ports on FreeBsd 7.0
On 21 Mar 2013 06:09, Vikas Mahajan vikas.mahaja...@gmail.com wrote: Hi all, After updating portsnap I tried to install php5. Now make config fails with following error: === Building for dialog4ports-0.1 Warning: Object directory not changed from original /usr/ports/ports-mgmt/dialog4ports/wor k/dialog4ports-0.1 cc -O2 -fno-strict-aliasing -pipe -I/usr/ports/ports-mgmt/dialog4ports/work/dialog-1.1-20 120706 -D_XOPEN_SOURCE_EXTENDED -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unu sed-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -o dialog4ports dialog4ports.o mixedlist.o arrows.o buttons.o dlg_keys. o help.o inputstr.o mouse.o mousewget.o textbox.o rc.o trace.o ui_getc.o util.o version.o -lncursesw util.o(.text+0x2e02): In function `dlg_auto_size': : undefined reference to `sqrt' *** Error code 1 1 error *** Error code 1 Stop in /usr/ports/ports-mgmt/dialog4ports. If I set NO_DIALOG=yes in /etc/make.conf, I am getting: === Skipping 'config' as NO_DIALOG is defined How can solve this problem? Any way to fix this error or using old make config dialog. Please help. You're not really running 7.0, are you? You probably mean 7.4. Look at using OPTIONS_SET=OPT1 OPT2 in /etc/make.conf. Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
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 7.x/8.x/9.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: benchmarks/mdtest broken because: checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=benchmarksportname=mdtest portname: chinese/big5con broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=big5con portname: chinese/bitchx broken because: patch reject build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=bitchx portname: chinese/hztty broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=hztty portname: databases/msql broken because: Broken on FreeBSD 9+ build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=msql portname: deskutils/simpleagenda broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=deskutilsportname=simpleagenda portname: devel/dsss broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=dsss portname: devel/libYGP broken because: Does not build with recent boost build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=libYGP portname: devel/linux-js broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-js portname: devel/linuxthreads broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linuxthreads portname: devel/p5-Dialog broken because: Does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=p5-Dialog portname: devel/py-extended_threading broken because: checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=py-extended_threading portname: devel/ros-common broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=ros-common portname: devel/ros_comm broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=ros_comm portname: devel/subcommander2 broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=subcommander2 portname: dns/opendd broken because: segfaults upon use build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=dnsportname=opendd portname: editors/xemacs-devel-mule broken because: does not build on FreeBSD 9.X build errors: none. overview:
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 7.x/8.x/9.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: accessibility/yasr broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=accessibilityportname=yasr portname: audio/gdam broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=gdam portname: audio/hydrogen broken because: does not install build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=hydrogen portname: audio/milkytracker broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=milkytracker portname: audio/py-tagpy broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=py-tagpy portname: benchmarks/mdtest broken because: checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=benchmarksportname=mdtest portname: benchmarks/polygraph31 broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=benchmarksportname=polygraph31 portname: cad/meshlab broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=cadportname=meshlab portname: chinese/big5con broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=big5con portname: chinese/bitchx broken because: patch reject build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=bitchx portname: chinese/cxterm broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=cxterm portname: chinese/hztty broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=hztty portname: comms/hso-kmod broken because: does not build with USB2, please try comms/uhso-kmod instead build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=commsportname=hso-kmod portname: comms/ib-kmod broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=commsportname=ib-kmod portname: comms/uticom broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=commsportname=uticom portname: databases/glom broken because: bad-plist build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=glom portname: databases/gomysql broken because: Does not compile with go1 build errors: none. overview:
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: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-tiff portname: security/sudosh3 forbidden because: Secunia Advisory SA38292, ISS X-Force sudosh-replay-bo (55903), replay() function buffer overflow. build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=securityportname=sudosh3 portname: www/linux-flashplugin9 forbidden because: CVE-2010-1297 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=linux-flashplugin9 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkitsportname=linux-pango ___ 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 install new dialog for ports on FreeBsd 7.0
On Thu, Mar 21, 2013 at 11:02:33AM +0300, Sergey V. Dyatko wrote: On Thu, 21 Mar 2013 08:56:34 +0100 Baptiste Daroussin b...@freebsd.org wrote: On Thu, Mar 21, 2013 at 11:39:07AM +0530, Vikas Mahajan wrote: Hi all, After updating portsnap I tried to install php5. Now make config fails with following error: === Building for dialog4ports-0.1 Warning: Object directory not changed from original /usr/ports/ports-mgmt/dialog4ports/wor k/dialog4ports-0.1 cc -O2 -fno-strict-aliasing -pipe -I/usr/ports/ports-mgmt/dialog4ports/work/dialog-1.1-20 120706 -D_XOPEN_SOURCE_EXTENDED -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unu sed-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -o dialog4ports dialog4ports.o mixedlist.o arrows.o buttons.o dlg_keys. o help.o inputstr.o mouse.o mousewget.o textbox.o rc.o trace.o ui_getc.o util.o version.o -lncursesw util.o(.text+0x2e02): In function `dlg_auto_size': : undefined reference to `sqrt' *** Error code 1 1 error *** Error code 1 Stop in /usr/ports/ports-mgmt/dialog4ports. If I set NO_DIALOG=yes in /etc/make.conf, I am getting: === Skipping 'config' as NO_DIALOG is defined How can solve this problem? Any way to fix this error or using old make config dialog. Please help. Try replacing the ports-mgmt/pkg/files/patch-Makefile by this one: http://people.freebsd.org/~bapt/patch-Makefile And tell me if it works. But please notice that 7.x is EOLed 28 feb, more and more the ports tree will get incompatible, and if we want to follow the direction for FreeBSD 10 (replace our make by bmake) we will need to a day or another break totally compatibility with 7. Consider upgrading your boxes. but ports/tags/RELEASE_7_EOL will not be broken for 7.x ? It cannot be broken, since it is not going to change. It's a tag, not a branch. A tag is a snapshot of the tree at a specific point in time, mainly for reference purposes later. A branch is a copy of the main part of the tree (the trunk, which also happens to be a branch, even if the main one) that can - and probably will - be updated by further commits. RELEASE_7_EOL is just a snapshot of the last version of the ports tree that was guaranteed to work with FreeBSD 7.x. It is not suitable as a csup/cvsup/svn up target - once you check it out, there is absolutely no point in updating to it later, since it is not going to ever change. G'luck, Peter -- Peter Pentchev r...@ringlet.net r...@freebsd.org p.penc...@storpool.com PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 This sentence was in the past tense. signature.asc Description: Digital signature
Re: Unable to install new dialog for ports on FreeBsd 7.0
On 21 March 2013 13:26, Baptiste Daroussin b...@freebsd.org wrote: Try replacing the ports-mgmt/pkg/files/patch-Makefile by this one: http://people.freebsd.org/~bapt/patch-Makefile There was no file named patch-Makefile. I created new file with contents as given by you, but still getting same error. And tell me if it works. But please notice that 7.x is EOLed 28 feb, more and more the ports tree will get incompatible, and if we want to follow the direction for FreeBSD 10 (replace our make by bmake) we will need to a day or another break totally compatibility with 7. Consider upgrading your boxes. I repeated same steps on March 13th on some other box and everything works. Introduction of new dialog created problem. Steps, I followed to get latest ports: # portsnap fetch # mv /usr/ports /usr/ports_old # portsnap extract -- Regards Vikas Mahajan ___ 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 install new dialog for ports on FreeBsd 7.0
On Thu, Mar 21, 2013 at 03:06:43PM +0530, Vikas Mahajan wrote: On 21 March 2013 13:26, Baptiste Daroussin b...@freebsd.org wrote: Try replacing the ports-mgmt/pkg/files/patch-Makefile by this one: http://people.freebsd.org/~bapt/patch-Makefile There was no file named patch-Makefile. I created new file with contents as given by you, but still getting same error. And tell me if it works. But please notice that 7.x is EOLed 28 feb, more and more the ports tree will get incompatible, and if we want to follow the direction for FreeBSD 10 (replace our make by bmake) we will need to a day or another break totally compatibility with 7. Consider upgrading your boxes. I repeated same steps on March 13th on some other box and everything works. Introduction of new dialog created problem. Steps, I followed to get latest ports: # portsnap fetch # mv /usr/ports /usr/ports_old # portsnap extract -- Regards Vikas Mahajan I just tested on a 7.x it works out of the box. I don't know what is happening on your system. or maybe portsnap for unknown reason is giving a wrong old version. regards, Bapt pgpzl7jcsze4i.pgp Description: PGP signature
Re: Unable to install new dialog for ports on FreeBsd 7.0
On 21 March 2013 15:19, Baptiste Daroussin b...@freebsd.org wrote: I just tested on a 7.x it works out of the box. I don't know what is happening on your system. or maybe portsnap for unknown reason is giving a wrong old version. Portsnap is updated to latest. # portsnap update Ports tree is already up to date. Further, it is providing php-5.4.13, that means new version of php. Is there a way to use old make config dialog with latest ports? Or how can I select options by disabling dialog in make.conf ? May be some commandline way to select options. -- Regards Vikas Mahajan ___ 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 install new dialog for ports on FreeBsd 7.0
On Thu, Mar 21, 2013 at 10:49:29AM +0100, Baptiste Daroussin wrote: On Thu, Mar 21, 2013 at 03:06:43PM +0530, Vikas Mahajan wrote: On 21 March 2013 13:26, Baptiste Daroussin b...@freebsd.org wrote: Try replacing the ports-mgmt/pkg/files/patch-Makefile by this one: http://people.freebsd.org/~bapt/patch-Makefile There was no file named patch-Makefile. I created new file with contents as given by you, but still getting same error. And tell me if it works. But please notice that 7.x is EOLed 28 feb, more and more the ports tree will get incompatible, and if we want to follow the direction for FreeBSD 10 (replace our make by bmake) we will need to a day or another break totally compatibility with 7. Consider upgrading your boxes. I repeated same steps on March 13th on some other box and everything works. Introduction of new dialog created problem. Steps, I followed to get latest ports: # portsnap fetch # mv /usr/ports /usr/ports_old # portsnap extract -- Regards Vikas Mahajan I just tested on a 7.x it works out of the box. I don't know what is happening on your system. or maybe portsnap for unknown reason is giving a wrong old version. regards, Bapt I get the sqrt error while trying to install dialog4ports on all my servers that are still running 7.4. I try installing it like this: portsnap fetch portsnap update portmaster ports-mgmt/dialog4ports I did this yesterday and also right now, same error: cc -O2 -fno-strict-aliasing -pipe -I/usr/ports/ports-mgmt/dialog4ports/work/dialog-1.1-20120706 -D_XOPEN_SOURCE_EXTENDED -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -o dialog4ports dialog4ports.o mixedlist.o arrows.o buttons.o dlg_keys.o help.o inputstr.o mouse.o mousewget.o textbox.o rc.o trace.o ui_getc.o util.o version.o -lncursesw util.o(.text+0x2ead): In function `dlg_auto_size': : undefined reference to `sqrt' *** Error code 1 1 error *** Error code 1 And, for the record, I'm really pi**ed off about the way that this clear POLA violation was introduced without mention in ports UPDATING. I ran portmaster upgrades in several servers (7.4, 8.3 and 9.0) yesterday, and all of them just skipped every config dialog with this error: env: /usr/local/bin/dialog4ports: No such file or directory Peter Olsson ___ 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 install new dialog for ports on FreeBsd 7.0
On 3/21/2013 5:21 AM, Peter Olsson wrote: On Thu, Mar 21, 2013 at 10:49:29AM +0100, Baptiste Daroussin wrote: On Thu, Mar 21, 2013 at 03:06:43PM +0530, Vikas Mahajan wrote: On 21 March 2013 13:26, Baptiste Daroussin b...@freebsd.org wrote: Try replacing the ports-mgmt/pkg/files/patch-Makefile by this one: http://people.freebsd.org/~bapt/patch-Makefile There was no file named patch-Makefile. I created new file with contents as given by you, but still getting same error. And tell me if it works. But please notice that 7.x is EOLed 28 feb, more and more the ports tree will get incompatible, and if we want to follow the direction for FreeBSD 10 (replace our make by bmake) we will need to a day or another break totally compatibility with 7. Consider upgrading your boxes. I repeated same steps on March 13th on some other box and everything works. Introduction of new dialog created problem. Steps, I followed to get latest ports: # portsnap fetch # mv /usr/ports /usr/ports_old # portsnap extract -- Regards Vikas Mahajan I just tested on a 7.x it works out of the box. I don't know what is happening on your system. or maybe portsnap for unknown reason is giving a wrong old version. regards, Bapt I get the sqrt error while trying to install dialog4ports on all my servers that are still running 7.4. I try installing 7.4 is EOL. If you want to continue using it you will need to use RELEASE_7_EOL. head is not supported. it like this: portsnap fetch portsnap update portmaster ports-mgmt/dialog4ports I did this yesterday and also right now, same error: cc -O2 -fno-strict-aliasing -pipe -I/usr/ports/ports-mgmt/dialog4ports/work/dialog-1.1-20120706 -D_XOPEN_SOURCE_EXTENDED -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -o dialog4ports dialog4ports.o mixedlist.o arrows.o buttons.o dlg_keys.o help.o inputstr.o mouse.o mousewget.o textbox.o rc.o trace.o ui_getc.o util.o version.o -lncursesw util.o(.text+0x2ead): In function `dlg_auto_size': : undefined reference to `sqrt' *** Error code 1 1 error *** Error code 1 And, for the record, I'm really pi**ed off about the way that this clear POLA violation was introduced without mention in ports UPDATING. I ran portmaster upgrades in several servers (7.4, 8.3 and 9.0) yesterday, and all of them just skipped every config dialog with this error: env: /usr/local/bin/dialog4ports: No such file or directory UPDATING is for *manual port changes needed for upgrading*. This *was* documented in CHANGES which is for ports infrastructure updates. It's not fair to call a bug a POLA violation. It should be fixed now. Peter Olsson -- Regards, Bryan Drewery bdrewery@freenode/EFNet signature.asc Description: OpenPGP digital signature
cad/meshlab: never working?
Is there any chance that port cad/meshlab will ever work on FreeBSD? signature.asc Description: This is a digitally signed message part
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ biology/seaview | 4.4.0 | 4.4.1 +-+ games/alienwave | 0.3.0 | 0.4.0 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt If wish to stop receiving portscout reminders, please contact portsc...@portscout.freebsd.org Thanks. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Unable to install new dialog for ports on FreeBsd 7.0
On Thu, Mar 21, 2013 at 07:17:12AM -0500, Bryan Drewery wrote: On 3/21/2013 5:21 AM, Peter Olsson wrote: On Thu, Mar 21, 2013 at 10:49:29AM +0100, Baptiste Daroussin wrote: On Thu, Mar 21, 2013 at 03:06:43PM +0530, Vikas Mahajan wrote: On 21 March 2013 13:26, Baptiste Daroussin b...@freebsd.org wrote: Try replacing the ports-mgmt/pkg/files/patch-Makefile by this one: http://people.freebsd.org/~bapt/patch-Makefile There was no file named patch-Makefile. I created new file with contents as given by you, but still getting same error. And tell me if it works. But please notice that 7.x is EOLed 28 feb, more and more the ports tree will get incompatible, and if we want to follow the direction for FreeBSD 10 (replace our make by bmake) we will need to a day or another break totally compatibility with 7. Consider upgrading your boxes. I repeated same steps on March 13th on some other box and everything works. Introduction of new dialog created problem. Steps, I followed to get latest ports: # portsnap fetch # mv /usr/ports /usr/ports_old # portsnap extract -- Regards Vikas Mahajan I just tested on a 7.x it works out of the box. I don't know what is happening on your system. or maybe portsnap for unknown reason is giving a wrong old version. regards, Bapt I get the sqrt error while trying to install dialog4ports on all my servers that are still running 7.4. I try installing 7.4 is EOL. If you want to continue using it you will need to use RELEASE_7_EOL. head is not supported. I know that, and I don't care about this error in my servers. They are scheduled for upgrade to 8 or 9. I just replied to Bapt's comment that he got it to work in 7.x, because I had seen the same problem as Vikas. I should have made this clear in my reply. And, for the record, I'm really pi**ed off about the way that this clear POLA violation was introduced without mention in ports UPDATING. I ran portmaster upgrades in several servers (7.4, 8.3 and 9.0) yesterday, and all of them just skipped every config dialog with this error: env: /usr/local/bin/dialog4ports: No such file or directory UPDATING is for *manual port changes needed for upgrading*. This *was* documented in CHANGES which is for ports infrastructure updates. It's not fair to call a bug a POLA violation. It should be fixed now. So this env problem was just a bug in portmaster? Ok, I didn't know that, I thought it was a general problem with dialog4ports. Then I'm sorry I called it a POLA violation. However I still think that this change in the ports environment could have justified a mention in UPDATING, since CHANGES is aimed at developers and committers, not ordinary users like myself. Peter Olsson ___ 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
qt-3.3 conflicts with qt4-webkit
Hello. Up to today, I've had the two ports in subject installed without any problem. Today, while making some upgrades, I see they conflict... Why do they suddenly do this? I've looked in /usr/ports/x11-toolkits/qt33/Makefile: it CONFLICTS with linguist-0.* qt-2.* qt-3.0.* qt-3.1.* qt-3.2.* qt-designer-2.* xfmail-1.5.[0-5] xfmail-1.5.5_[1-2], but not with qt4-*. In /usr/ports/www/qt4-webkit/Makefile, there is no CONFLICT at all, so I guessed this could come from /usr/ports/Mk/bsd.qt.mk. There I find: .if defined(QT_DIST) ... CONFLICTS_BUILD=qt-3.* qt-copy-3.* This was introduced on March 15. So, provided I need both as slaves ports of other applications (and I don't think I'm alone), is there any way I can fix this? Why was this conflict set up in the first place? What is QT_DIST? bye Thanks av. ___ 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 install new dialog for ports on FreeBsd 7.0
On 3/21/2013 8:42 AM, Peter Olsson wrote: On Thu, Mar 21, 2013 at 07:17:12AM -0500, Bryan Drewery wrote: On 3/21/2013 5:21 AM, Peter Olsson wrote: On Thu, Mar 21, 2013 at 10:49:29AM +0100, Baptiste Daroussin wrote: On Thu, Mar 21, 2013 at 03:06:43PM +0530, Vikas Mahajan wrote: On 21 March 2013 13:26, Baptiste Daroussin b...@freebsd.org wrote: Try replacing the ports-mgmt/pkg/files/patch-Makefile by this one: http://people.freebsd.org/~bapt/patch-Makefile There was no file named patch-Makefile. I created new file with contents as given by you, but still getting same error. And tell me if it works. But please notice that 7.x is EOLed 28 feb, more and more the ports tree will get incompatible, and if we want to follow the direction for FreeBSD 10 (replace our make by bmake) we will need to a day or another break totally compatibility with 7. Consider upgrading your boxes. I repeated same steps on March 13th on some other box and everything works. Introduction of new dialog created problem. Steps, I followed to get latest ports: # portsnap fetch # mv /usr/ports /usr/ports_old # portsnap extract -- Regards Vikas Mahajan I just tested on a 7.x it works out of the box. I don't know what is happening on your system. or maybe portsnap for unknown reason is giving a wrong old version. regards, Bapt I get the sqrt error while trying to install dialog4ports on all my servers that are still running 7.4. I try installing 7.4 is EOL. If you want to continue using it you will need to use RELEASE_7_EOL. head is not supported. I know that, and I don't care about this error in my servers. They are scheduled for upgrade to 8 or 9. I just replied to Bapt's comment that he got it to work in 7.x, because I had seen the same problem as Vikas. I should have made this clear in my reply. And, for the record, I'm really pi**ed off about the way that this clear POLA violation was introduced without mention in ports UPDATING. I ran portmaster upgrades in several servers (7.4, 8.3 and 9.0) yesterday, and all of them just skipped every config dialog with this error: env: /usr/local/bin/dialog4ports: No such file or directory UPDATING is for *manual port changes needed for upgrading*. This *was* documented in CHANGES which is for ports infrastructure updates. It's not fair to call a bug a POLA violation. It should be fixed now. So this env problem was just a bug in portmaster? Ok, I didn't know that, I thought it was a general problem with dialog4ports. Then I'm sorry I called it a POLA violation. The problems with it building and missing should both be fixed now. Those were bugs with the dialog4ports support. However I still think that this change in the ports environment could have justified a mention in UPDATING, since CHANGES is aimed at developers and committers, not ordinary users like myself. That's a fair point. I'll add an entry. Peter Olsson -- Regards, Bryan Drewery bdrewery@freenode/EFNet signature.asc Description: OpenPGP digital signature
Re: Unable to install new dialog for ports on FreeBsd 7.0
On 21 March 2013 19:31, Bryan Drewery bdrew...@freebsd.org wrote: The problems with it building and missing should both be fixed now. Those were bugs with the dialog4ports support. So, now can I install dialog4ports on FreeBsd 7.x using head ? Further, how to get RELEASE_7_EOL using portsnap ? -- Regards Vikas Mahajan ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: CFT: texlive ports
On 02/28/13 14:44, Hiroki Sato wrote: Hiroto Kagotani hiroto.kagot...@gmail.com wrote in cac_w2oem6ndybdmxrocsuup1w0dj20sfmjbednrd-cmdsaf...@mail.gmail.com: hi 2013/2/28 Hiroki Sato h...@freebsd.org hi hi hihttp://people.allbsd.org/~hrs/FreeBSD/texlive-20130228-1.tar.gz hi hi Please try this instead. hi hi hi I tried this version and succeeded to install on 9.1R. hi But I miss symlinks etex and lualatex in /usr/local/bin, hi which was installed by the portshaker version. Thank you. The following tarball should fix it: http://people.allbsd.org/~hrs/FreeBSD/texlive-20130301-1.tar.gz -- Hiroki Any chance to get these patches in the tree? -Nathan ___ 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 install new dialog for ports on FreeBsd 7.0
On 2013-03-21 15:57, Vikas Mahajan wrote: On 21 March 2013 19:31, Bryan Drewery bdrew...@freebsd.org wrote: The problems with it building and missing should both be fixed now. Those were bugs with the dialog4ports support. So, now can I install dialog4ports on FreeBsd 7.x using head ? Further, how to get RELEASE_7_EOL using portsnap ? portsnap is always HEAD! With portsnap there is no way to specify a tag (RELEASE_7_EOL) or a branch. RELEASE_7_EOL was tagged on svn rev. 313527 (Wed Mar 6 17:10:52 2013 UTC, ~two weeks ago), meanwhile svn and portsnap is on rev. 314847. ___ 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 install new dialog for ports on FreeBsd 7.0
Ok. Got it. Thanks, Vikas On 21 March 2013 20:59, olli hauer oha...@gmx.de wrote: On 2013-03-21 15:57, Vikas Mahajan wrote: On 21 March 2013 19:31, Bryan Drewery bdrew...@freebsd.org wrote: The problems with it building and missing should both be fixed now. Those were bugs with the dialog4ports support. So, now can I install dialog4ports on FreeBsd 7.x using head ? Further, how to get RELEASE_7_EOL using portsnap ? portsnap is always HEAD! With portsnap there is no way to specify a tag (RELEASE_7_EOL) or a branch. RELEASE_7_EOL was tagged on svn rev. 313527 (Wed Mar 6 17:10:52 2013 UTC, ~two weeks ago), meanwhile svn and portsnap is on rev. 314847. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
-current breaking (some?) ports, how to detect which?
From Jan Beich (gecko@): *quote* In file included from /usr/include/sys/stat.h:99:0, from /usr/local/include/fontconfig/fontconfig.h:29, from configure:25673: /usr/include/sys/time.h:134:17: error: unknown type name 'sbintime_t' /usr/include/sys/time.h:141:1: error: unknown type name 'sbintime_t' /usr/include/sys/time.h: In function 'bttosbt': /usr/include/sys/time.h:144:12: error: 'sbintime_t' undeclared (first use in this function) /usr/include/sys/time.h:144:12: note: each undeclared identifier is reported only once for each function it appears in /usr/include/sys/time.h:144:23: error: expected ')' before 'bt' /usr/include/sys/time.h: At top level: /usr/include/sys/time.h:148:9: error: unknown type name 'sbintime_t' /usr/include/sys/time.h:206:9: error: unknown type name 'sbintime_t' /usr/include/sys/time.h:216:1: error: unknown type name 'sbintime_t' /usr/include/sys/time.h: In function 'tstosbt': /usr/include/sys/time.h:219:12: error: 'sbintime_t' undeclared (first use in this function) /usr/include/sys/time.h:219:23: error: expected ')' before 'ts' /usr/include/sys/time.h: At top level: /usr/include/sys/time.h:224:9: error: unknown type name 'sbintime_t' /usr/include/sys/time.h:234:1: error: unknown type name 'sbintime_t' /usr/include/sys/time.h: In function 'tvtosbt': /usr/include/sys/time.h:237:12: error: 'sbintime_t' undeclared (first use in this function) /usr/include/sys/time.h:237:23: error: expected ')' before 'tv' This is common error when headers modified by gcc are not in sync with those under /usr/include. For example, after http://svnweb.freebsd.org/changeset/base/247476 make sure you have sbintime_t in sys/types.h copy $ fgrep sbintime /usr/local/lib/gcc47/gcc/x86_64-portbld-freebsd10.0/4.7.3/include-fixed/sys/types.h typedef __int64_t sbintime_t; If you don't have then rebuild lang/gcc47. *end quote* So I'm rebuilding gcc47 now, but how do I know that other ports are unaffected? Or how do I find which other ports are affected? Is this something that current@ should communicate to ports@ more explicitly? Is this something that should be noted in ports/UPDATING? Thanks Anton ___ 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: net-mgmt/argus-monitor
Gentle people, Please be aware that this software has stolen its name from Carnegie Mellon University's and QoSient, LLC's open source network monitor, Argus. http://qosient.com/argus. The original argus, first developed in 1988 and released as open source in1993, is an advanced network flow monitor, discussed in the IETF, and the US NIST, used by 10,000's of sites for network performance and security monitoring, is referenced in 100's of academic journals. It is used by many Gov'ts, Institutions and Corporations, and is in the top 100 security tools used in the internet (sectools.org). Thank you for your consideration, Carter Carter Bullard CEO/President QoSient, LLC 150 E 57th Street Suite 12D New York, New York 10022 +1 212 588-9133 Phone +1 212 588-9134 Fax smime.p7s Description: S/MIME cryptographic signature
Re: dia fails to start after recent upgrade
Le Wed, 20 Mar 2013 20:46:02 -0400 (EDT), AN a...@neu.net a écrit : FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #38 r248401: Sat Mar 16 21:39:04 CDT 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 After a recent portupgrade (graphics/dia (dia-gnome-0.97.1_3,1 - dia-0.97.2,1) dia is broken. Will not start from the gnome menu, starting from the command line causes the splash screen to appear for about 1 second and then it disappears. There is no error produced on the command line, or in the system log. I see this too (fresh 9.1-stable/amd64) ___ 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
Hosted Exchange Alana Notebook Hediye
Hosted Exchange Hizmetine Notebook Hediye Exchange Kobi: - 1-75 Kullanıcı arası - 5 GB Mailbox alanı - 1 adet Database - Ortak Adres Defteri - 5 Adet Dağıtım Grubu - Symantec Brightmail Premium Anti-Spam - Exchange Server 2010 - 50 MB Standart Web Hosting Hizmeti - Microsoft Outlook, Mac, IPAD, Windows Phone ve Blackberry desteği - Mailbox/Ay: 5TL+KDV Exchange Pro : - 75 Kullanıcı üzeri - 10 GB Mailbox alanı - 5 adet Database - Ortak Adres Defteri - 50 Adet Dağıtım Grubu - Symantec Brightmail Premium Anti-Spam - Exchange Server 2010 - 100 MB Standart Web Hosting Hizmeti - Microsoft Outlook, Mac, IPAD, Windows Phone ve Blackberry desteği - Mailbox/Ay: 10TL+KDV Kampanya Hakkında Yukarıda belirtilen fiyatlar 2013 Nisan ayı sonuna kadar geçerlidir.. SSD Disk performansı 6Gbit veriyolu ve 60.000 IoPs değerleri ile mart2013 nesil sunucular ve yüksek kapasiteler ile hizmet veriyoruz. Farklı config talepleriniz için bi...@enguclu.com adresine mail ile bildirimde bulunabilirsiniz. *Hediye ürünler 2 yıllık taahhüt süresince 1 yıllık ödemesinin peşin yapılması durumda geçerlidir. Hediye ürünlerin teknik özellikleri , alınacak hizmet kapasitesine göre değişir. Hediye ürünlerin detaylı bilgileri teklif aşamasında tarafınıza iletilecektir. Bu kampanyamız bireysel müşterilerimizi kapsamamaktadır. Teklif almak için bi...@enguclu.com adresinden mail ile veya 0850 333 65 66 numaralı telefonumuzdan bizimle iletişim kurabilirsiniz. www.EnGuclu.com EnGüçlü Bilişim İnternet Hizmetleri Tüm Hakları Saklıdır 2013 | Hakkımızda | İletişim Mail listesinden çıkmak istiyorsanız lütfen bu maili boş cevaplanıyınız. ___ 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
rsvg-cairo.h:33:10: fatal error: 'cairo.h' file not found
Trying to install Gnome2 in a Vbox virtual machine fails with: cc: warning: unknown warning option '-Wunsafe-loop-optimizations'; did you mean '-Wout-of-line-declaration'? warning: unknown warning option '-Wunsafe-loop-optimizations'; did you mean '-Wout-of-line-declaration'? [-Wunknown-warning-option] rsvg-convert.c:248:9: warning: 'rsvg_handle_set_size_callback' is deprecated [-Wdeprecated-declarations] rsvg_handle_set_size_callback (rsvg, rsvg_cairo_size_callback, dimensions, NULL); ^ ./rsvg.h:201:6: note: 'rsvg_handle_set_size_callback' declared here void rsvg_handle_set_size_callback (RsvgHandle * handle, ^ 2 warnings generated. CC rsvg_convert-rsvg-size-callback.o cc: warning: unknown warning option '-Wunsafe-loop-optimizations'; did you mean '-Wout-of-line-declaration'? warning: unknown warning option '-Wunsafe-loop-optimizations'; did you mean '-Wout-of-line-declaration'? [-Wunknown-warning-option] 1 warning generated. CCLD rsvg-convert cc: warning: unknown warning option '-Wunsafe-loop-optimizations'; did you mean '-Wout-of-line-declaration'? GISCAN Rsvg-2.0.gir In file included from stdin:4: In file included from /usr/ports/graphics/librsvg2/work/librsvg-2.36.4/rsvg.h:239: ./rsvg-cairo.h:33:10: fatal error: 'cairo.h' file not found #include cairo.h ^ 1 error generated. Error while processing the source. gmake[2]: *** [Rsvg-2.0.gir] Error 1 gmake[2]: Leaving directory `/usr/ports/graphics/librsvg2/work/librsvg-2.36.4' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/graphics/librsvg2/work/librsvg-2.36.4' gmake: *** [all] Error 2 *** [do-build] Error code 1 Stop in /usr/ports/graphics/librsvg2. *** [lib-depends] Error code 1 Stop in /usr/ports/x11/gnome-panel. *** [install] Error code 1 Stop in /usr/ports/x11/gnome-panel. *** [lib-depends] Error code 1 Stop in /usr/ports/x11/gnome-applets. *** [install] Error code 1 Stop in /usr/ports/x11/gnome-applets. *** [run-depends] Error code 1 Stop in /usr/ports/x11/gnome2. *** [install] Error code 1 Stop in /usr/ports/x11/gnome2. FreeBSD FBSD-10 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r247825: Mon Mar 4 20:13:02 CST 2013 root@FBSD-10:/usr/obj/usr/src/sys/GENERIC amd64 Ports tree is up to date. Any help is appreciated, thanks in advance. ___ 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: trouble with ffmpeg1
On Thu, Mar 21, 2013 at 3:54 PM, joerg_surmann joerg_surm...@snafu.de wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi all, whats wrong with ffmpeg1? can't update this port: snip install: /usr/ports/multimedia/ffmpeg1/work/ffmpeg-1.0.5/doc/*.html: No such file or directory *** [post-install] Error code 71 Stop in /usr/ports/multimedia/ffmpeg1. *** [install] Error code 1 Stop in /usr/ports/multimedia/ffmpeg1. Thanks for help. Suri As a certain annoying computer may someday say: Insufficient data for a meaningful response. The generation of the HTML files didn't happen for some reason. It should have been near the end of the build. Either it didn't happen or it want somewhere wrong, but you did not provide that information. There should be about 10 lines starting with HTML. There is a normal error message for fate.texi, but that should be it. -- R. Kevin Oberman, Network Engineer E-mail: rkober...@gmail.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: FreeBSD Port: net-mgmt/argus-monitor
On Thu, Mar 21, 2013 at 9:29 AM, Carter Bullard car...@qosient.com wrote: Gentle people, Please be aware that this software has stolen its name from Carnegie Mellon University's and QoSient, LLC's open source network monitor, Argus. http://qosient.com/argus. The original argus, first developed in 1988 and released as open source in1993, is an advanced network flow monitor, discussed in the IETF, and the US NIST, used by 10,000's of sites for network performance and security monitoring, is referenced in 100's of academic journals. It is used by many Gov'ts, Institutions and Corporations, and is in the top 100 security tools used in the internet (sectools.org). Thank you for your consideration, Carter Carter Bullard CEO/President QoSient, LLC 150 E 57th Street Suite 12D New York, New York 10022 +1 212 588-9133 Phone +1 212 588-9134 Fax While the CMU Argus goes back to 1998, the one in the ports tree as argus-monitor is somewhat older, having originated in 1996. It is also an open source tool and, as such, the name Argus is a fairly obvious one. I worked with the Argus Security Monitor, a physical security management software package at Lawrence Livermore National Laboratory back in the 1980s, so the use of the Argus name for security software pre-dates both of these projects. The LLNL Argus was used by a number of government facilities and may well still be in use. So, while the CMU developed Argus may be very popular, it is quite unlikely that the name was stolen by either project and, since the other Argus is older, it seems the CMU Argus could be the only one to steal the name. I might also mention that an Argus prefix highjack monitor also exists. It was developed in China. I first heard of the one FreeBSD lists as argus-monitor back at a North American Network Operators meeting a great many years ago and it is also quite popular in the networking community. I suspect that both may be counted in the survey du to the unfortunate name collision. N.B. I have no involvement with either Argus and both are in the FreeBSD ports. The CMU developed one is net-mgmt/argus3. I am also not involved with the FreeBSD ports other than as a user and volunteer. -- R. Kevin Oberman, Network Engineer E-mail: rkober...@gmail.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
INDEX now builds successfully on 8.x
___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: net-mgmt/argus-monitor
Hey Kevin, 1988, not 1998. Oh there is no question that the tcp for me guy has been undermining the original Georgia Tech / CMU argus, since he started. Yes I was aware of the Lawrence Livermore group, because of the work I had done while at Georgia Tech, but that project was not a network security tool. Our use of the name argus, started in 1986 at Georgia Tech, and was used on the NSFnet backbone, which I managed as a part of Suranet, starting in 1987. It was reference by NIST between 1994-2002, as the only network auditing (Red Book style) tool, those pages are long gone, but was definitely there. The first reference to argus at NANOG was my argus, when I was in their security group, and the first presentation at the IETF RMON group in 1993, on network flow monitoring was this argus. All use of argus as a network security flow monitor in the US DoD, DARPA, DISA, IC, DHS and State Dept, are my argus, as much as I can tell, as my argus is in the only one currently in the FOSS (federal open source system), and on sourceforge.mil. And yes the Chinese group that presented their BGP paper this year, asked us if we would change our name, since they had been using the name for 6 months, and thought it hard to change their DNS entry. Had no Idea that we have been using the name for almost 20 years. It will take me a while to get that addressed as well. It is very hard to hold onto your image as a project, when there is so much confusion, and blatant piracy. I know that is a strong word, but when you've got a guy changing your Wikipedia entries, sectools.org entries to put his home page on your project, it's just a major pain. It would be nice if the community could be more supportive. Carter Carter Bullard CEO/President QoSient, LLC 150 E 57th Street Suite 12D New York, New York 10022 +1 212 588-9133 Phone +1 212 588-9134 Fax On Mar 21, 2013, at 9:26 PM, Kevin Oberman rkober...@gmail.com wrote: On Thu, Mar 21, 2013 at 9:29 AM, Carter Bullard car...@qosient.com wrote: Gentle people, Please be aware that this software has stolen its name from Carnegie Mellon University's and QoSient, LLC's open source network monitor, Argus. http://qosient.com/argus. The original argus, first developed in 1988 and released as open source in1993, is an advanced network flow monitor, discussed in the IETF, and the US NIST, used by 10,000's of sites for network performance and security monitoring, is referenced in 100's of academic journals. It is used by many Gov'ts, Institutions and Corporations, and is in the top 100 security tools used in the internet (sectools.org). Thank you for your consideration, Carter Carter Bullard CEO/President QoSient, LLC 150 E 57th Street Suite 12D New York, New York 10022 +1 212 588-9133 Phone +1 212 588-9134 Fax While the CMU Argus goes back to 1998, the one in the ports tree as argus-monitor is somewhat older, having originated in 1996. It is also an open source tool and, as such, the name Argus is a fairly obvious one. I worked with the Argus Security Monitor, a physical security management software package at Lawrence Livermore National Laboratory back in the 1980s, so the use of the Argus name for security software pre-dates both of these projects. The LLNL Argus was used by a number of government facilities and may well still be in use. So, while the CMU developed Argus may be very popular, it is quite unlikely that the name was stolen by either project and, since the other Argus is older, it seems the CMU Argus could be the only one to steal the name. I might also mention that an Argus prefix highjack monitor also exists. It was developed in China. I first heard of the one FreeBSD lists as argus-monitor back at a North American Network Operators meeting a great many years ago and it is also quite popular in the networking community. I suspect that both may be counted in the survey du to the unfortunate name collision. N.B. I have no involvement with either Argus and both are in the FreeBSD ports. The CMU developed one is net-mgmt/argus3. I am also not involved with the FreeBSD ports other than as a user and volunteer. -- R. Kevin Oberman, Network Engineer E-mail: rkober...@gmail.com smime.p7s Description: S/MIME cryptographic signature
