[QAT] r334638: 1x leftovers, 2x finished, 1x success
- Update to 0.6.6 - Build ID: 20131123060418-10332 Job owner: t...@freebsd.org Buildtime: 3 hours Enddate: Sat, 23 Nov 2013 08:34:18 GMT Revision: r334638 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=334638 - Port:math/R-cran-igraph 0.6.6 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~t...@freebsd.org/20131123060418-10332-230532/R-cran-igraph-0.6.6.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~t...@freebsd.org/20131123060418-10332-230533/R-cran-igraph-0.6.6.log Buildgroup: 9.2-QAT/amd64 Buildstatus: FINISHED Buildgroup: 9.2-QAT/i386 Buildstatus: FINISHED -- Buildarchive URL: https://qat.redports.org/buildarchive/20131123060418-10332 redports https://qat.redports.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
[QAT] r334643: 1x leftovers, 2x finished, 1x success
- Update to 0.3.920.3 - Build ID: 20131123060606-40844 Job owner: t...@freebsd.org Buildtime: 3 hours Enddate: Sat, 23 Nov 2013 08:43:50 GMT Revision: r334643 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=334643 - Port:math/R-cran-RcppArmadillo 0.3.920.3 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~t...@freebsd.org/20131123060606-40844-230552/R-cran-RcppArmadillo-0.3.920.3.log Buildgroup: 8.4-QAT/i386 Buildstatus: FINISHED Buildgroup: 9.2-QAT/amd64 Buildstatus: FINISHED Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~t...@freebsd.org/20131123060606-40844-230555/R-cran-RcppArmadillo-0.3.920.3.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20131123060606-40844 redports https://qat.redports.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
[QAT] r334640: 1x leftovers, 2x finished, 1x success
- Update to 0.10.6 - Build ID: 20131123060452-2559 Job owner: t...@freebsd.org Buildtime: 3 hours Enddate: Sat, 23 Nov 2013 08:52:49 GMT Revision: r334640 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=334640 - Port:devel/R-cran-Rcpp 0.10.6 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~t...@freebsd.org/20131123060452-2559-230540/R-cran-Rcpp-0.10.6.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~t...@freebsd.org/20131123060452-2559-230541/R-cran-Rcpp-0.10.6.log Buildgroup: 9.2-QAT/amd64 Buildstatus: FINISHED Buildgroup: 9.2-QAT/i386 Buildstatus: FINISHED -- Buildarchive URL: https://qat.redports.org/buildarchive/20131123060452-2559 redports https://qat.redports.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
[QAT] r334644: 1x leftovers, 2x finished, 1x success
- Update to 0.8-12 - Build ID: 20131123060620-58912 Job owner: t...@freebsd.org Buildtime: 3 hours Enddate: Sat, 23 Nov 2013 09:03:15 GMT Revision: r334644 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=334644 - Port:graphics/R-cran-rgdal 0.8.12 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~t...@freebsd.org/20131123060620-58912-230556/R-cran-rgdal-0.8.12.log Buildgroup: 8.4-QAT/i386 Buildstatus: FINISHED Buildgroup: 9.2-QAT/amd64 Buildstatus: FINISHED Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~t...@freebsd.org/20131123060620-58912-230559/R-cran-rgdal-0.8.12.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20131123060620-58912 redports https://qat.redports.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
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 +-+ java/eclipse-findbugs | 1.3.2.20080222 | 2.0.3.20131122-15020 +-+ 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...@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: Upgrading Perl... Somebody just shoot me and put me out of my misery!
+--On 22 novembre 2013 12:40:07 -0800 Ronald F. Guilmette r...@tristatelogic.com wrote: |1) Change the option in lang/perl5.16: | make -C /usr/ports/lang/perl5.16 config | | HUH?? I don't understand this at all. What exactly is the option that | we are changing here? And what does it matter to anything? Like it is written in the paragraph before, the default option for perl has changed, *if* you want to switch from non threaded to threaded, you also need to change your perl configuration. -- Mathieu Arnold ___ 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: Upgrading Perl... Somebody just shoot me and put me out of my misery!
On Saturday 23 November 2013 11:54:27 Mathieu Arnold wrote: +--On 22 novembre 2013 12:40:07 -0800 Ronald F. Guilmette r...@tristatelogic.com wrote: |1) Change the option in lang/perl5.16: | make -C /usr/ports/lang/perl5.16 config | | HUH?? I don't understand this at all. What exactly is the option that | we are changing here? And what does it matter to anything? Like it is written in the paragraph before, the default option for perl has changed, *if* you want to switch from non threaded to threaded, you also need to change your perl configuration. I have threaded option on all the time. Do I need to rebuild than? It is confused for me. -- Mitja --- http://www.redbubble.com/people.lumiwa ___ 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: Upgrading Perl... Somebody just shoot me and put me out of my misery!
On Friday 22 November 2013 21:40:07 Ronald F. Guilmette wrote: Now, one last little thing... The note in the UPDATING file dated 20131120 gives essentially the same instructions as the one dated 20131023, *however* it also contains this: 1) Change the option in lang/perl5.16: make -C /usr/ports/lang/perl5.16 config HUH?? I don't understand this at all. What exactly is the option that we are changing here? And what does it matter to anything? It would be Nice if this were entierly less opaque. $ man ports [...] config Configure OPTIONS for this port using dialog4ports(1). And what does it matter to anything? Gives you a choice to re-think your existing/chosen port options. For example, a new default is now THREADS, but you may not like it, as it somewhat increases the memory usage and requires to rebuild all perl modules. Mark ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Upgrading Perl... Somebody just shoot me and put me out of my misery!
+--On 23 novembre 2013 06:13:33 -0500 Ajtim lum...@gmail.com wrote: | On Saturday 23 November 2013 11:54:27 Mathieu Arnold wrote: | +--On 22 novembre 2013 12:40:07 -0800 Ronald F. Guilmette | r...@tristatelogic.com wrote: | |1) Change the option in lang/perl5.16: | | make -C /usr/ports/lang/perl5.16 config | | | | HUH?? I don't understand this at all. What exactly is the option | | that we are changing here? And what does it matter to anything? | | Like it is written in the paragraph before, the default option for perl | has changed, *if* you want to switch from non threaded to threaded, you | also need to change your perl configuration. | | I have threaded option on all the time. Do I need to rebuild than? It | is confused for me. Then, you're not changing anything, you don't need to rebuild anything. You only need to rebuild everything if you're changing that. -- Mathieu Arnold ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
INDEX build failed for 8.x
INDEX build failed with errors: Generating INDEX-8 - please wait..GhostScript not found in PATH Makefile, line 23: warning: /bin/sh /home/indexbuild/tindex/ports/russian/koi8r-ps/files/find-fontmap.sh returned non-zero status Done. make_index: /home/indexbuild/tindex/ports/x11/mate-base: no entry for /home/indexbuild/tindex/ports/sysutils/mate-control-center Committers on the hook: antoine bapt gerald koobs kwm osa pawel sunpoet Most recent SVN update was: Updating '.': Aarchivers/mate-file-archiver Aarchivers/mate-file-archiver/pkg-plist Aarchivers/mate-file-archiver/Makefile Aarchivers/mate-file-archiver/distinfo Aarchivers/mate-file-archiver/pkg-descr Aarchivers/mate-file-archiver/files Aarchivers/mate-file-archiver/files/patch-src_fr-command-tar.c Aarchivers/mate-file-archiver/files/patch-src_fr-command-lrzip.c Aarchivers/mate-file-archiver/files/patch-src_fr-command-zip.c Uarchivers/Makefile Adevel/p5-Devel-FindPerl Adevel/p5-Devel-FindPerl/pkg-plist Adevel/p5-Devel-FindPerl/Makefile Adevel/p5-Devel-FindPerl/distinfo Adevel/p5-Devel-FindPerl/pkg-descr Udevel/Makefile Adevel/libesedb Adevel/libesedb/pkg-plist Adevel/libesedb/Makefile Adevel/libesedb/distinfo Adevel/libesedb/pkg-descr Udevel/p5-MooseX-App-Cmd/Makefile UU devel/p5-MooseX-App-Cmd/distinfo Adevel/mate-common Adevel/mate-common/pkg-plist Adevel/mate-common/Makefile Adevel/mate-common/distinfo Adevel/mate-common/pkg-descr Adevel/mate-common/files Adevel/mate-common/files/patch-macros_mate-autogen Ddevel/libhtp/files UU devel/libhtp/pkg-plist Udevel/libhtp/Makefile UU devel/libhtp/distinfo Aaudio/mate-media Aaudio/mate-media/files Aaudio/mate-media/files/patch-gst-mixer-applet_applet.c Aaudio/mate-media/pkg-plist Aaudio/mate-media/Makefile Aaudio/mate-media/distinfo Aaudio/mate-media/pkg-descr Uaudio/Makefile Udeskutils/Makefile Adeskutils/mate-file-manager-open-terminal Adeskutils/mate-file-manager-open-terminal/pkg-plist Adeskutils/mate-file-manager-open-terminal/Makefile Adeskutils/mate-file-manager-open-terminal/distinfo Adeskutils/mate-file-manager-open-terminal/pkg-descr Adeskutils/mate-notification-daemon Adeskutils/mate-notification-daemon/pkg-plist Adeskutils/mate-notification-daemon/Makefile Adeskutils/mate-notification-daemon/distinfo Adeskutils/mate-notification-daemon/pkg-descr Adeskutils/mate-character-map Adeskutils/mate-character-map/pkg-plist Adeskutils/mate-character-map/Makefile Adeskutils/mate-character-map/distinfo Adeskutils/mate-character-map/pkg-descr Adeskutils/mate-menu-editor Adeskutils/mate-menu-editor/pkg-plist Adeskutils/mate-menu-editor/Makefile Adeskutils/mate-menu-editor/distinfo Adeskutils/mate-menu-editor/pkg-descr Adeskutils/mate-menu-editor/files Adeskutils/mate-menu-editor/files/patch-Mozo_util.py Adeskutils/mate-utils Adeskutils/mate-utils/Makefile Adeskutils/mate-utils/distinfo Adeskutils/mate-utils/pkg-descr Adeskutils/mate-utils/files Adeskutils/mate-utils/files/patch-logview_logview-utils.c Adeskutils/mate-utils/files/patch-gsearchtool_gsearchtool-support.c Adeskutils/mate-utils/files/patch-logview_logview-manager.c Adeskutils/mate-utils/pkg-plist UKeywords/info.yaml Ax11-fm/mate-file-manager Ax11-fm/mate-file-manager/Makefile Ax11-fm/mate-file-manager/distinfo Ax11-fm/mate-file-manager/pkg-descr Ax11-fm/mate-file-manager/files A x11-fm/mate-file-manager/files/patch-src_file-manager_fm-properties-window.c Ax11-fm/mate-file-manager/pkg-plist Ux11-fm/Makefile Unet/Makefile Unet/tcpflow/distinfo Dnet/tcpflow/files/patch-src__tcpdemux.h Dnet/tcpflow/files/patch-src__be13_api__plugin.cpp Anet/tcpflow/files/patch-src__wifipcap__wifipcap.cpp Unet/tcpflow/Makefile Anet/libmateweather Anet/libmateweather/pkg-plist Anet/libmateweather/Makefile Anet/libmateweather/distinfo Anet/libmateweather/pkg-descr Asysutils/mate-settings-daemon Asysutils/mate-settings-daemon/pkg-plist Asysutils/mate-settings-daemon/Makefile Asysutils/mate-settings-daemon/distinfo Asysutils/mate-settings-daemon/pkg-descr Usysutils/Makefile Asysutils/mate-power-manager Asysutils/mate-power-manager/pkg-plist Asysutils/mate-power-manager/Makefile Asysutils/mate-power-manager/distinfo Asysutils/mate-power-manager/pkg-descr Asysutils/mate-power-manager/files Asysutils/mate-power-manager/files/patch-src_gpm-load.c Asysutils/mate-power-manager/files/patch-applets_brightness_Makefile.am Asysutils/mate-power-manager/files/patch-autogen.sh Asysutils/mate-power-manager/files/patch-src_Makefile.am Asysutils/mate-power-manager/files/patch-configure.ac A
[QAT] r334573: 2x leftovers, 2x success
Do not mute INSTALL_xxx actions Reported by:danfe - Build ID: 20131122113200-17833 Job owner: marty...@freebsd.org Buildtime: 25 hours Enddate: Sat, 23 Nov 2013 12:08:17 GMT Revision: r334573 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=334573 - Port:devel/raknet 3.9.2_2,1 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~marty...@freebsd.org/20131122113200-17833-230092/raknet-3.9.2_2,1.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~marty...@freebsd.org/20131122113200-17833-230093/raknet-3.9.2_2,1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~marty...@freebsd.org/20131122113200-17833-230094/raknet-3.9.2_2,1.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~marty...@freebsd.org/20131122113200-17833-230095/raknet-3.9.2_2,1.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20131122113200-17833 redports https://qat.redports.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: Packages missing after Re-installation with portmaster
Fabian Keil freebsd-lis...@fabiankeil.de wrote: I'm occasionally missing packages after trying to rebuild them with portmaster. For example I just lost liferea: And somewhat related: ## fk@r500 ~ $portmaster /usr/ports/lang/python3 === Port directory: /usr/ports/lang/python3 === Gathering distinfo list for installed ports === SU Running 'make config-conditional' Password: === Gathering dependency list for lang/python3 from ports === Starting dependency check === Checking dependency: lang/python33 === Launching child to install lang/python33 === lang/python3 lang/python33 (1/1) === Port directory: /usr/ports/lang/python33 === Launching 'make checksum' for lang/python33 in background === SU Running 'make config-conditional' === Gathering dependency list for lang/python33 from ports === Starting dependency check === Checking dependency: devel/gmake === Checking dependency: ports-mgmt/pkg === Initial dependency check complete for lang/python33 === Continuing initial dependency check for lang/python3 === Checking dependency: ports-mgmt/pkg === Initial dependency check complete for lang/python3 === lang/python3 (1) === The following actions will be taken if you choose to proceed: Install lang/python3 Install lang/python33 === Proceed? y/n [y] === Starting build for lang/python3 === === Starting check for build dependencies === Gathering dependency list for lang/python3 from ports === Starting dependency check === Checking dependency: ports-mgmt/pkg === Dependency check complete for lang/python3 === python3-3 depends on file: /usr/local/sbin/pkg - found === Fetching all distfiles required by python3-3 for building === Extracting for python3-3 === Patching for python3-3 === Configuring for python3-3 === Starting check for runtime dependencies === Gathering dependency list for lang/python3 from ports === Starting dependency check === Checking dependency: lang/python33 === Launching child to install lang/python33 === lang/python3 lang/python33 (1/1) === Port directory: /usr/ports/lang/python33 === Starting check for build dependencies === Gathering dependency list for lang/python33 from ports === Starting dependency check === Checking dependency: devel/gmake === Checking dependency: ports-mgmt/pkg === Dependency check complete for lang/python33 === lang/python3 lang/python33 (1/1) === Starting check for runtime dependencies === Gathering dependency list for lang/python33 from ports === No dependencies for lang/python33 === SU Running make install === SU Installing /var/db/pkg/python33-3.3.2_4/distfiles === Running 'make clean' in the background === Installation of lang/python33 (python33-3.3.2_4) succeeded === Keeping distfile, valid for another port: Python-2.7.5.tar.xz === Keeping current distfile: python/Python-3.3.2.tar.xz === Distfile cleaning complete === Returning to dependency check for lang/python3 === Dependency check complete for lang/python3 === SU Running make install === Installing for python3-3 === Generating temporary packing list === Checking if lang/python3 already installed /bin/ln -sf /usr/local/bin/python3.3 /usr/local/bin/python3 /bin/ln -sf /usr/local/bin/python-shared3.3 /usr/local/bin/python-shared3 /bin/ln -sf /usr/local/bin/2to3-3.3 /usr/local/bin/2to3-3 /bin/ln -sf /usr/local/bin/idle3-3.3 /usr/local/bin/idle3 /bin/ln -sf /usr/local/bin/pydoc3-3.3 /usr/local/bin/pydoc3 /bin/ln -sf /usr/local/bin/python3.3-config /usr/local/bin/python3-config /bin/ln -sf /usr/local/bin/python-shared3.3-config /usr/local/bin/python-shared3-config === Registering installation for python3-3 Installing python3-3... done === Running 'make clean' in the background === Removing empty directories from WRKDIRPREFIX === The following actions were performed: Installation of lang/python33 (python33-3.3.2_4) Installation of lang/python3 (python3-3) === Exiting ## Note that lang/python33 hasn't actually been installed. The second attempt (with lang/python3 already installed) worked as expected. Fabian signature.asc Description: PGP signature
Re: lang/php5 - separate apache module from php5 port
On 12/07/2013 14:57, Florent Peterschmitt wrote: Le 10/07/2013 23:54, olli hauer a écrit : Here it would be ap22-mod_php5 and ap24-mod_php5. Thats what I thought with your first mail and I suspect this is a good idea. Yep, it was what I meant. So do you think I should contact the maintainer ? I second this, as php-fpm is more and more used, with apache, nginx, lighttpd... There are also cases where only php-cli is needed (at least we use that too) I like the way debian handle this: php-cli/php-fpm/php-cgi/php-module are packaged independently (and in freebsd we could have ap22-mod-php and ap24-mod-php). The difficulty may be that it would make some more ports to maintain for Alex, who may need some help (?) My 2 cts... ps: re-using this thread as I didn't find (missed?) any more recent discussion about this... -- geoffroy desvernay C.R.I - Administration systèmes et réseaux Ecole Centrale de Marseille signature.asc Description: OpenPGP digital signature
Re: lang/php5 - separate apache module from php5 port
On 23/11/13 13:20, geoffroy desvernay wrote: On 12/07/2013 14:57, Florent Peterschmitt wrote: Le 10/07/2013 23:54, olli hauer a écrit : Here it would be ap22-mod_php5 and ap24-mod_php5. Thats what I thought with your first mail and I suspect this is a good idea. Yep, it was what I meant. So do you think I should contact the maintainer ? I second this, as php-fpm is more and more used, with apache, nginx, lighttpd... There are also cases where only php-cli is needed (at least we use that too) I like the way debian handle this: php-cli/php-fpm/php-cgi/php-module are packaged independently (and in freebsd we could have ap22-mod-php and ap24-mod-php). The difficulty may be that it would make some more ports to maintain for Alex, who may need some help (?) My 2 cts... ps: re-using this thread as I didn't find (missed?) any more recent discussion about this... Yeah, Debian's package split is nice (and not only for PHP but everything else). But I'm not sure if we want to make x packages we have to make x ports. I mean, it is very useful when distributing packages and I'm not sure the port system cannot make x packages from 1 only port. -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail. +33 (0)6 64 33 97 92 | * Send PDF for documents. http://florent.peterschmitt.fr | * Trim your quotations. Really. Proudly powered by Open Source | Thank you :) signature.asc Description: OpenPGP digital signature
Re: problem with clamav
On 23/11/2013 1:56 PM, Shawn Webb wrote: On Fri, Nov 22, 2013 at 8:57 PM, AN a...@neu.net wrote: FreeBSD .rootbsd.net 11.0-CURRENT FreeBSD 11.0-CURRENT #3 r258260M: Sun Nov 17 13:01:19 EST 2013 rootbsd.net:/usr/obj/usr/src/sys/GENERIC amd64 # portupgrade -va --- Session started at: Fri, 22 Nov 2013 20:46:56 -0500 [Reading data from pkg(8) ... - 81 packages found - done] ** Port marked as IGNORE: security/clamav: Unknown version of GCC specified (USE_GCC=any) --- Listing the results (+:done / -:ignored / *:skipped / !:failed) - security/clamav (marked as IGNORE) --- Packages processed: 0 done, 1 ignored, 0 skipped and 0 failed --- Session ended at: Fri, 22 Nov 2013 20:47:00 -0500 (consumed 00:00:03) # pkg info |grep gcc gcc-4.6.4 GNU Compiler Collection 4.6 gcc-ecj-4.5Eclipse Java Compiler used to build GCC Java # pkg info |grep clam clamav-0.98_2 Command line virus scanner written entirely in C Is clamav broken on current? Any suggestions on how to proceed? Thanks in advance. The problem wouldn't be with ClamAV, but with the port entry. ClamAV currently doesn't build with clang on 11-CURRENT, but it does indeed work with gcc (I'm building manually from source checked out via git, and am using gcc/g++ 4.6.4 from ports). Maybe the port maintainer has some input. Thanks, Shawn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org Unfortunately, I have the same problem on 9.2Stable (built/installed today), using default gcc only. cd /usr/ports/security/clamav make -DBATCH package === clamav-0.98_2 Unknown version of GCC specified (USE_GCC=any). *** [all] Error code 1 Stop in /usr/ports/security/clamav. And the Makefile contains the line: USE_GCC=any The only reference to gcc in make.conf is: FAVORITE_COMPILER=gcc And for completeness # cd /usr/ports/security/clamav/ make -DBATCH __MAKE_CONF=/dev/null package === clamav-0.98_2 Unknown version of GCC specified (USE_GCC=any). *** [package] Error code 1 Stop in /usr/ports/security/clamav. and # gcc -v Using built-in specs. Target: i386-undermydesk-freebsd Configured with: FreeBSD/i386 system compiler Thread model: posix gcc version 4.2.1 20070831 patched [FreeBSD] Advice welcome? Regards, Dewayne. ___ 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: lang/php5 - separate apache module from php5 port
On 23/11/2013 13:02, Florent Peterschmitt wrote: Yeah, Debian's package split is nice (and not only for PHP but everything else). But I'm not sure if we want to make x packages we have to make x ports. I mean, it is very useful when distributing packages and I'm not sure the port system cannot make x packages from 1 only port. It can't. This sub-package functionality is coming, but it's not here yet. Conversion to staging is a pre-requisite, and I've a feeling that old-style pkg_tools aren't going to cut it; pkgng will[*] be required. Which means it's going to be problematic for older release branches. Cheers, Matthew [*] almost certainly. -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
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
Few missing packages from the new PKG repositories
Were these left out by accident or why aren’t they included? - x11/gnome2, x11/gnome2-lite is in the repo. - editors/vim, editors/vim-lite is in the repo as well. -Kimmo signature.asc Description: Message signed with OpenPGP using GPGMail
[QAT] r334674: 4x leftovers
- Do not overwrite CFLAGS PR: ports/184193 Submitted by: Lukas Slebodnik lukas.slebod...@intrak.sk (maintainer) - Build ID: 20131123151200-12517 Job owner: sunp...@freebsd.org Buildtime: 22 minutes Enddate: Sat, 23 Nov 2013 15:34:03 GMT Revision: r334674 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=334674 - Port:security/sssd 1.9.6 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~sunp...@freebsd.org/20131123151200-12517-230680/sssd-1.9.6.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~sunp...@freebsd.org/20131123151200-12517-230681/sssd-1.9.6.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~sunp...@freebsd.org/20131123151200-12517-230682/sssd-1.9.6.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~sunp...@freebsd.org/20131123151200-12517-230683/sssd-1.9.6.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20131123151200-12517 redports https://qat.redports.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: Few missing packages from the new PKG repositories
On Sat, Nov 23, 2013 at 3:27 PM, Kimmo Paasiala kpaas...@icloud.com wrote: Were these left out by accident or why aren’t they included? - x11/gnome2, x11/gnome2-lite is in the repo. - editors/vim, editors/vim-lite is in the repo as well. -Kimmo Do all the dependencies build with default options? I suspect that's why kde4 wasn't packaged last time I checked. (I guess we could take a look at the build logs from the new repository; I know they're out there somewhere.) -- Daniel Nebdal ___ 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: Few missing packages from the new PKG repositories
On 23-11-2013 18:13, Daniel Nebdal wrote: On Sat, Nov 23, 2013 at 3:27 PM, Kimmo Paasiala kpaas...@icloud.com wrote: Were these left out by accident or why aren’t they included? - x11/gnome2, x11/gnome2-lite is in the repo. - editors/vim, editors/vim-lite is in the repo as well. -Kimmo Do all the dependencies build with default options? I suspect that's why kde4 wasn't packaged last time I checked. (I guess we could take a look at the build logs from the new repository; I know they're out there somewhere.) To both of you, on which FreeBSD version and arch are these packages missing? That will help us narrow down where to look. -Koop --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.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: Few missing packages from the new PKG repositories
On 23.11.2013, at 20.29, Koop Mast k...@rainbow-runner.nl wrote: On 23-11-2013 18:13, Daniel Nebdal wrote: On Sat, Nov 23, 2013 at 3:27 PM, Kimmo Paasiala kpaas...@icloud.com wrote: Were these left out by accident or why aren’t they included? - x11/gnome2, x11/gnome2-lite is in the repo. - editors/vim, editors/vim-lite is in the repo as well. -Kimmo Do all the dependencies build with default options? I suspect that's why kde4 wasn't packaged last time I checked. (I guess we could take a look at the build logs from the new repository; I know they're out there somewhere.) To both of you, on which FreeBSD version and arch are these packages missing? That will help us narrow down where to look. -Koop --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com This is from http://pkg0.bme.freebsd.org/ that is one of the SRV mirrors of pkg.freebsd.org: x11/gnome2 is present in freebsd:8:x86:32 but is missing from freebsd:8:x86:64 It’s also missing from freebsd:9:x86:32 and missing from freebsd:9:x86:64. Also missing from freebsd:10:x86:32 and missing from freebsd:10:x86:64. So it looks like the x11/gnome2 package is only available for FreeBSD 8 i386. -Kimmo signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Few missing packages from the new PKG repositories
On Sat, Nov 23, 2013 at 7:29 PM, Koop Mast k...@rainbow-runner.nl wrote: On 23-11-2013 18:13, Daniel Nebdal wrote: On Sat, Nov 23, 2013 at 3:27 PM, Kimmo Paasiala kpaas...@icloud.com wrote: Were these left out by accident or why aren’t they included? - x11/gnome2, x11/gnome2-lite is in the repo. - editors/vim, editors/vim-lite is in the repo as well. -Kimmo Do all the dependencies build with default options? I suspect that's why kde4 wasn't packaged last time I checked. (I guess we could take a look at the build logs from the new repository; I know they're out there somewhere.) To both of you, on which FreeBSD version and arch are these packages missing? That will help us narrow down where to look. -Koop On 10.0-BETA4 / amd64 (with pkg updated right now): pkg search gnome2 gnome2-office-2.32.1 gnome2-reference-2.20_1 pkg search kde bmkdep-20131009 kde-xdg-env-1.0_3,1 kde4-icons-oxygen-4.10.5 kde4-shared-mime-info-1.2 kde4-wallpapers-freebsd-1.0 kde4-xdg-env-1.0.1 kdehier4-1.1.1_1 pam_kde-1.0 -- Daniel Nebdal ___ 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: Upgrading Perl... Somebody just shoot me and put me out of my misery!
In message 17d096510a47c61858d55...@atuin.in.mat.cc, Mathieu Arnold m...@freebsd.org wrote: +--On 22 novembre 2013 12:40:07 -0800 Ronald F. Guilmette r...@tristatelogic.com wrote: |1) Change the option in lang/perl5.16: | make -C /usr/ports/lang/perl5.16 config | | HUH?? I don't understand this at all. What exactly is the option that | we are changing here? And what does it matter to anything? Like it is written in the paragraph before, the default option for perl has changed, *if* you want to switch from non threaded to threaded, you also need to change your perl configuration. OK, but please help me understand here. What is it, exactly, that is _now_ being threaded, that wasn't threaded before? Is it the guts of the Perl interpreter itself? Is it the Perl programs that get interpreted by the interpreter? (Part of what is confusing about this is that I was under the impression... perhaps naive... that Perl was already set up for threads support quite some long time ago.) ___ 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
Graphing installed ports
Has anyone ever used a graphing tool (such as GraphViz) to create a graph of all of the installed ports on a given system and their dependencies? I think that this would be interesting... and perhaps even useful... to do, but it seems like such an obvious idea that I have to guess that somebody else has already coded up a small script to do this exact thing. If so, I see no reason why I should re-invent this wheel. ___ 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
Graphing installed ports
The following script http://www.lpthe.jussieu.fr/~talon/check_pkg.py does the job you want plus other things, but it was written for the old package system (i.e. it looks under /var/db/pkg). By the way i noted that as soon as you have a fair number of ports installed, you get so many arrows in the diagram that you cannot see anything, rendering the idea quite useless. I hoped one could discover islands with little interconnections between them but in fact mostly everything becomes connected by dependency. -- Michel Talon ta...@lpthe.jussieu.fr smime.p7s Description: S/MIME cryptographic signature
Re: Few missing packages from the new PKG repositories
On 23.11.2013, at 20.29, Koop Mast k...@rainbow-runner.nl wrote: On 23-11-2013 18:13, Daniel Nebdal wrote: On Sat, Nov 23, 2013 at 3:27 PM, Kimmo Paasiala kpaas...@icloud.com wrote: Were these left out by accident or why aren’t they included? - x11/gnome2, x11/gnome2-lite is in the repo. - editors/vim, editors/vim-lite is in the repo as well. -Kimmo Do all the dependencies build with default options? I suspect that's why kde4 wasn't packaged last time I checked. (I guess we could take a look at the build logs from the new repository; I know they're out there somewhere.) To both of you, on which FreeBSD version and arch are these packages missing? That will help us narrow down where to look. -Koop --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com editors/vim seems to be in the repo for all versions and architectures after all, I assumed it was missing based on a thread on the FreeBSD forums. -Kimmo signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Upgrading Perl... Somebody just shoot me and put me out of my misery!
On Sat, Nov 23, 2013 at 12:17 PM, Ronald F. Guilmette r...@tristatelogic.com wrote: OK, but please help me understand here. What is it, exactly, that is _now_ being threaded, that wasn't threaded before? ... (Part of what is confusing about this is that I was under the impression... perhaps naive... that Perl was already set up for threads support quite some long time ago.) Perl _was_ set up to be threaded (although I have no idea what is actually threaded there), but the port option to enable it being threaded was not enabled by default. The implication is that if you compiled it with default options, it wasn't threaded. But now it (the option) has been changed to be enabled by default, and so the point of that UPDATING entry was that if you are running with default options, then your Perl will switch from non-threaded to threaded when you recompile it, and you will thus need to recompile all ports that depend on Perl. IF you already had this option enabled to begin with, I believe you don't need to recompile and reinstall anything (including Perl itself, but do note that the ports system will then keep thinking that Perl hasn't been upgraded - which isn't an issue, since the only thing changed here is the defaults and not any functionality, and so you can just wait to recompile it when something more serious changes; this is up to you though). Hope this clears it up a bit. 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
Re: Graphing installed ports
In message d5ad0e8d-2bb8-48cc-9ed6-52933d321...@lpthe.jussieu.fr, Michel Talon ta...@lpthe.jussieu.fr wrote: The following script http://www.lpthe.jussieu.fr/~talon/check_pkg.py does the job you want plus other things, Thank you! but it was written for the old package system (i.e. it looks under /var/db/pkg). That's OK. I am still using that. By the way i noted that as soon as you have a fair number of ports = installed, you get so many arrows in the diagram that you cannot see anything, rendering = the idea quite useless. Well, that is interesting. I have a dim recollection that there is/was s theorem in the fields of software science to the effect that the greater the number of interconnections (e.g. between functions) within a given program, the more likely it was to have bugs. I'll have to go and do some googling now and refresh my memory about that. Regards, rfg ___ 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: Upgrading Perl... Somebody just shoot me and put me out of my misery!
In message caeahp2iw+hd4rnnzk0rvd6imnr+badevatgf0fqwblpikmp...@mail.gmail.com Anton Afanasyev aas...@gmail.com wrote: On Sat, Nov 23, 2013 at 12:17 PM, Ronald F. Guilmette r...@tristatelogic.com wrote: OK, but please help me understand here. What is it, exactly, that is _now_ being threaded, that wasn't threaded before? ... (Part of what is confusing about this is that I was under the impression... perhaps naive... that Perl was already set up for threads support quite some long time ago.) Perl _was_ set up to be threaded (although I have no idea what is actually threaded there), but the port option to enable it being threaded was not enabled by default. (One might well ask why not? but we will leave that question aside for the moment.) The implication is that if you compiled it with default options, it wasn't threaded. But now it (the option) has been changed to be enabled by default, and so the point of that UPDATING entry was that if you are running with default options, then your Perl will switch from non-threaded to threaded when you recompile it, OK, that part, at least is clear. and you will thus need to recompile all ports that depend on Perl. This is the part that is still utterly baffling. Why would _anything_ that is in any way dependent upon the Perl interpreter need to be rebuilt? In this switch to threads=on, has the language itself changed? And if not, shouldn't the change to multi-threading capability within the interpreter be utterly transparent to (and a non-event for) any and all pre-existing Perl code? Obviously, there's something that I'm missing, but I have no idea what it might be. IF you already had this option enabled to begin with, I believe you don't need to recompile and reinstall anything (including Perl itself, but do note that the ports system will then keep thinking that Perl hasn't been upgraded - which isn't an issue, since the only thing changed here is the defaults and not any functionality, and so you can just wait to recompile it when something more serious changes; this is up to you though). Hope this clears it up a bit. Well, I thank you for your attempt to help clear up the confusion, but I do confess that the need to rebuild... or the value of rebuilding... all of the stuff that _depends_ on Perl is still rather entirely mystifying. I'm *not* claiming that the maintainer didn't have a good reason for suggesting these rebuilds. I'm only saying that *I* personally still don't have a good understanding of what the need for this is/was. Regards, rfg ___ 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: Upgrading Perl... Somebody just shoot me and put me out of my misery!
On 23/11/2013 22:12, Ronald F. Guilmette wrote: and you will thus need to recompile all ports that depend on Perl. This is the part that is still utterly baffling. Why would _anything_ that is in any way dependent upon the Perl interpreter need to be rebuilt? In this switch to threads=on, has the language itself changed? And if not, shouldn't the change to multi-threading capability within the interpreter be utterly transparent to (and a non-event for) any and all pre-existing Perl code? Obviously, there's something that I'm missing, but I have no idea what it might be. Technically, you don't actually need to recompile something that's pure perl, or that only requires perl to run some scripts. However everything that has a binary interface with perl -- XS modules, software with embedded perl interpreters -- certainly will need recompiling to match the new threaded ABI that has now become the default. The advice to 'recompile everything that depends on perl' is overkill, but it's a simple way to be sure that you have in fact recompiled everything necessary. Picking out only those ports that really needed to be recompiled would require a procedure too unweildy to be usefully described in UPDATING. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: Upgrading Perl... Somebody just shoot me and put me out of my misery!
+--On 23 novembre 2013 14:12:12 -0800 Ronald F. Guilmette r...@tristatelogic.com wrote: | Perl _was_ set up to be threaded (although I have no idea what is | actually threaded there), but the port option to enable it being | threaded was not enabled by default. | | (One might well ask why not? but we will leave that question aside for | the moment.) Mainly because in early days, many software had problems with the changes that went into the interpreter when it had threads, like a smaller stack, which made amavis pretty unhappy, for instance. And from then, it stay off because nobody thought of changing it. | The implication is that if you compiled it with default | options, it wasn't threaded. But now it (the option) has been changed to | be enabled by default, and so the point of that UPDATING entry was that | if you are running with default options, then your Perl will switch from | non-threaded to threaded when you recompile it, | | OK, that part, at least is clear. Yeah, sorry, english is not my mother tongue, my explanations can be a bit off :-) | and you will thus need to recompile all ports that depend on Perl. | | This is the part that is still utterly baffling. | | Why would _anything_ that is in any way dependent upon the Perl | interpreter need to be rebuilt? In this switch to threads=on, has the | language itself changed? And if not, shouldn't the change to | multi-threading capability within the interpreter be utterly transparent | to (and a non-event for) any and all pre-existing Perl code? | | Obviously, there's something that I'm missing, but I have no idea what it | might be. Because, hum, quite a few things change when you enable threads, some headers bits change, some calls that are noop without become real call with, things like that. Now, it obviously is a non issue with ports that only use perl to run scripts, or p5- ports that are only scripts, but for ports that have XS files that get compiled into .so, they need to get recompiled, and the same goes for every bit of software that includes the interpreter. As there is no simple way to differentiate between those two categories of dependencies, I ask people to rebuild (or reinstall, if you're using binary packages) everything. I assure you, it does not make me happy at all to have people rebuild everything depending on Perl every two weeks (like it feels I've been doing that for a few months...) | IF you already had this option enabled to begin with, I believe you don't | need to recompile and reinstall anything (including Perl itself, but do | note that the ports system will then keep thinking that Perl hasn't been | upgraded - which isn't an issue, since the only thing changed here is the | defaults and not any functionality, and so you can just wait to recompile | it when something more serious changes; this is up to you though). | | Hope this clears it up a bit. | | Well, I thank you for your attempt to help clear up the confusion, but I | do confess that the need to rebuild... or the value of rebuilding... all | of the stuff that _depends_ on Perl is still rather entirely mystifying. | | I'm *not* claiming that the maintainer didn't have a good reason for | suggesting these rebuilds. I'm only saying that *I* personally still | don't have a good understanding of what the need for this is/was. As the maintainer, I hope my previous bit did explain that a bit better, if things are not that clear, do feel free to point them out and I'll try better. The thing is that all those explanations can't go into UPDATING, we try to keep it short not to confuse people. -- Mathieu Arnold ___ 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: Few missing packages from the new PKG repositories
+--On 23 novembre 2013 16:27:12 +0200 Kimmo Paasiala kpaas...@icloud.com wrote: | Were these left out by accident or why aren’t they included? | | - x11/gnome2, x11/gnome2-lite is in the repo. | | - editors/vim, editors/vim-lite is in the repo as well. The packages are built from the ports tree as it is at 1 UTC every Wednesday, so, if something is broken at that time, like openjpeg was (my fault) many dependencies are not included. You'll have to wait for next week. -- Mathieu Arnold ___ 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: problem with clamav
On 24/11/2013 12:13 AM, Dewayne Geraghty wrote: On 23/11/2013 1:56 PM, Shawn Webb wrote: On Fri, Nov 22, 2013 at 8:57 PM, AN a...@neu.net wrote: FreeBSD .rootbsd.net 11.0-CURRENT FreeBSD 11.0-CURRENT #3 r258260M: Sun Nov 17 13:01:19 EST 2013 rootbsd.net:/usr/obj/usr/src/sys/GENERIC amd64 # portupgrade -va --- Session started at: Fri, 22 Nov 2013 20:46:56 -0500 [Reading data from pkg(8) ... - 81 packages found - done] ** Port marked as IGNORE: security/clamav: Unknown version of GCC specified (USE_GCC=any) --- Listing the results (+:done / -:ignored / *:skipped / !:failed) - security/clamav (marked as IGNORE) --- Packages processed: 0 done, 1 ignored, 0 skipped and 0 failed --- Session ended at: Fri, 22 Nov 2013 20:47:00 -0500 (consumed 00:00:03) # pkg info |grep gcc gcc-4.6.4 GNU Compiler Collection 4.6 gcc-ecj-4.5Eclipse Java Compiler used to build GCC Java # pkg info |grep clam clamav-0.98_2 Command line virus scanner written entirely in C Is clamav broken on current? Any suggestions on how to proceed? Thanks in advance. The problem wouldn't be with ClamAV, but with the port entry. ClamAV currently doesn't build with clang on 11-CURRENT, but it does indeed work with gcc (I'm building manually from source checked out via git, and am using gcc/g++ 4.6.4 from ports). Maybe the port maintainer has some input. Thanks, Shawn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org Unfortunately, I have the same problem on 9.2Stable (built/installed today), using default gcc only. cd /usr/ports/security/clamav make -DBATCH package === clamav-0.98_2 Unknown version of GCC specified (USE_GCC=any). *** [all] Error code 1 Stop in /usr/ports/security/clamav. And the Makefile contains the line: USE_GCC=any The only reference to gcc in make.conf is: FAVORITE_COMPILER=gcc And for completeness # cd /usr/ports/security/clamav/ make -DBATCH __MAKE_CONF=/dev/null package === clamav-0.98_2 Unknown version of GCC specified (USE_GCC=any). *** [package] Error code 1 Stop in /usr/ports/security/clamav. and # gcc -v Using built-in specs. Target: i386-undermydesk-freebsd Configured with: FreeBSD/i386 system compiler Thread model: posix gcc version 4.2.1 20070831 patched [FreeBSD] Advice welcome? Regards, Dewayne. ___ 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 Thanks to Gerald for addressing this issue per http://svnweb.freebsd.org/ports/head/Mk/bsd.gcc.mk?sortby=dateview=log clamav now builds. Regards, Dewayne ___ 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
