Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 22 Apr 2015 07:03:34 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 199600] math/saga: unbreak build on platforms using libstdc++ (regressed by wxgtk30 change)
Message-ID:  <bug-199600-13-j9iliVSCJy@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-199600-13@https.bugs.freebsd.org/bugzilla/>
References:  <bug-199600-13@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199600

Jan Beich <jbeich@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|math/saga: unbreak build on |math/saga: unbreak build on
                   |platforms using gcc         |platforms using libstdc++
                   |                            |(regressed by wxgtk30
                   |                            |change)
             Blocks|                            |199177
           Keywords|                            |regression

--- Comment #3 from Jan Beich <jbeich@FreeBSD.org> ---
The port did build fine on FreeBSD before before r383466. Note, only
python27-2.7.9 -> python27-2.7.9_1 and wx30-gtk2-3.0.2_2 -> wx30-gtk2-3.0.2_3
happend between the following runs.
http://beefy1.isc.freebsd.org/data/93i386-default/383446/logs/saga-2.1.4.log
http://beefy1.isc.freebsd.org/data/93i386-default/383569/logs/errors/saga-2.1.4.log

I didn't notice all platforms use GCC because of USES=compiler:gcc-c++11-lib.
So, the reason the port builds fine on F10+ despite absence of -std=c++11 is
likely because of libc++.
http://beefy5.nyi.freebsd.org/data/101i386-default/384362/logs/saga-2.1.4.log

-- 
You are receiving this mail because:
You are the assignee for the bug.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-199600-13-j9iliVSCJy>