Re: testing the value of ${CXX} in ports Makefile

2015-01-30 Thread Tijl Coosemans
On Thu, 29 Jan 2015 22:46:32 -0800 (PST) Don Lewis wrote: > gcc46, gcc47, gcc48, and probably gcc5 (haven't tested that one yet) all > work. gcc49 requires a source patch. Can't you make the patch work with all versions of gcc? ___ freebsd-ports@freebs

FreeBSD ports you maintain which are out of date

2015-01-30 Thread portscout
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

Re: testing the value of ${CXX} in ports Makefile

2015-01-30 Thread Jimmy Kelley
On Fri, Jan 30, 2015 at 09:40:46AM +0100, Tijl Coosemans wrote: > On Thu, 29 Jan 2015 22:46:32 -0800 (PST) Don Lewis > wrote: > > gcc46, gcc47, gcc48, and probably gcc5 (haven't tested that one yet) all > > work. gcc49 requires a source patch. > > Can't you make the patch work with all versions

Re: testing the value of ${CXX} in ports Makefile

2015-01-30 Thread Chris H
On Thu, 29 Jan 2015 22:46:32 -0800 (PST) Don Lewis wrote > On 29 Jan, Chris H wrote: > > On Thu, 29 Jan 2015 19:43:38 -0800 (PST) Don Lewis > > wrote > >> I need to test the value of ${CXX} in the Makefile for a port and am > >> getting unexpected results. Here is a simplified version of the >

Re: testing the value of ${CXX} in ports Makefile

2015-01-30 Thread Dominic Fandrey
On 30/01/2015 07:28, Don Lewis wrote: > On 29 Jan, Elizabeth Myers wrote: >> On 01/29/15 21:43, Don Lewis wrote: >>> I need to test the value of ${CXX} in the Makefile for a port and am >>> getting unexpected results. Here is a simplified version of the >>> Makefile: >>> >>> ... >>> USE_GCC=4.

FreeBSD Port: www/pound

2015-01-30 Thread Richard Clayton
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Could I draw your attention to the fact that Pound has (at very long last) pushed out v2.7 ... ... this has "disable proto" directives so it's finally possible to fix the "Poodle" SSL issue without using an exotic build.

Re: testing the value of ${CXX} in ports Makefile

2015-01-30 Thread Chris H
On Fri, 30 Jan 2015 06:30:10 -0800 "Chris H" wrote > On Thu, 29 Jan 2015 22:46:32 -0800 (PST) Don Lewis > wrote > > > On 29 Jan, Chris H wrote: > > > On Thu, 29 Jan 2015 19:43:38 -0800 (PST) Don Lewis > > > wrote > > >> I need to test the value of ${CXX} in the Makefile for a port and am > >

INDEX build failed for 8.x

2015-01-30 Thread Ports Index build
INDEX build failed with errors: Generating INDEX-8 - please wait..--- describe.accessibility --- --- describe.arabic --- --- describe.archivers --- --- describe.astro --- --- describe.audio --- --- describe.benchmarks --- --- describe.biology --- --- describe.cad --- --- describe.chinese --- --- de

Re: testing the value of ${CXX} in ports Makefile

2015-01-30 Thread Shane Ambler
On 30/01/2015 14:13, Don Lewis wrote: I need to test the value of ${CXX} in the Makefile for a port and am getting unexpected results. Here is a simplified version of the Makefile: PORTNAME= junk PORTVERSION=0.0.0 CATEGORIES= devel DISTFILES= MAINTAINER= truck...@freebsd.org

INDEX now builds successfully on 8.x

2015-01-30 Thread Ports Index build
___ 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: testing the value of ${CXX} in ports Makefile

2015-01-30 Thread Don Lewis
On 30 Jan, Dominic Fandrey wrote: > On 30/01/2015 07:28, Don Lewis wrote: >> On 29 Jan, Elizabeth Myers wrote: >>> On 01/29/15 21:43, Don Lewis wrote: I need to test the value of ${CXX} in the Makefile for a port and am getting unexpected results. Here is a simplified version of the

libmspack build error, unrecognized command line option "-Wno-unused-result"

2015-01-30 Thread Gary Aitken
Is anyone else seeing this error building archivers/libmspack cc1: error: unrecognized command line option "-Wno-unused-result" ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any

Re: testing the value of ${CXX} in ports Makefile

2015-01-30 Thread Don Lewis
On 31 Jan, Shane Ambler wrote: > On 30/01/2015 14:13, Don Lewis wrote: >> I need to test the value of ${CXX} in the Makefile for a port and am >> getting unexpected results. Here is a simplified version of the >> Makefile: >> >> PORTNAME=junk >> PORTVERSION= 0.0.0 >> CATEGORIES= devel >> DIST

Re: testing the value of ${CXX} in ports Makefile

2015-01-30 Thread Don Lewis
On 30 Jan, Tijl Coosemans wrote: > On Thu, 29 Jan 2015 22:46:32 -0800 (PST) Don Lewis > wrote: >> gcc46, gcc47, gcc48, and probably gcc5 (haven't tested that one yet) all >> work. gcc49 requires a source patch. > > Can't you make the patch work with all versions of gcc? Well, I could, but what

Re: www/squid does not shutdown via rc

2015-01-30 Thread Kevin Oberman
On Wed, Jan 28, 2015 at 6:58 AM, Dr. Peter Voigt wrote: > On Tue, 27 Jan 2015 11:51:51 +0100 > Marko Cupać wrote: > > > On Tue, 27 Jan 2015 07:11:10 + > > Matthew Seaman wrote: > > > > > On 2015/01/27 03:52, Kurt Jaeger wrote: > > > > Doesn't installing a custom kernel break freebsd-update

Re: testing the value of ${CXX} in ports Makefile

2015-01-30 Thread Jan Beich
Don Lewis writes: > PORTNAME= junk > PORTVERSION= 0.0.0 > CATEGORIES= devel > DISTFILES= > > MAINTAINER= truck...@freebsd.org > COMMENT= junk > > USE_GCC= 4.9+ > > .include > > post-patch: > echo CXX=${CXX} > .if ${CXX} == g++49 This idiom may lead to crashes. According

[Bug 18552] Port Upgradee: boxes-1.0.1

2015-01-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=18552 --- Comment #2 from commit-h...@freebsd.org --- A commit references this bug: Author: jgh Date: Sat Jan 31 07:14:50 UTC 2015 New revision: 378192 URL: https://svnweb.freebsd.org/changeset/ports/378192 Log: - update to 5.45 - pet portlin

Re: testing the value of ${CXX} in ports Makefile

2015-01-30 Thread Shane Ambler
On 31/01/2015 15:30, Jan Beich wrote: Also, the following wouldn't work .if ${CHOSEN_COMPILER_TYPE} == "gcc" && ${COMPILER_VERSION} == 49 because COMPILER_VERSION or COMPILER_FEATURES are evaluated against COMPILER_TYPE, not CHOSEN_COMPILER_TYPE. That is a good point, it appears we curre

Re: testing the value of ${CXX} in ports Makefile

2015-01-30 Thread Shane Ambler
On 31/01/2015 10:55, Don Lewis wrote: On 31 Jan, Shane Ambler wrote: On 30/01/2015 14:13, Don Lewis wrote: post-patch: @echo CXX=${CXX} @echo GCC_DEFAULT=${GCC_DEFAULT} .if ${CHOSEN_COMPILER_TYPE} == gcc and ${COMPILER_VERSION} == 49 @echo g++49 was detected .else