[pkgsrc/trunk]: pkgsrc/devel/glibmm glibmm: Drop GCC_REQD from buildlink3.mk

[gdt <gdt%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/f057f6f75479
branches:  trunk
changeset: 373340:f057f6f75479
user:      gdt <gdt%pkgsrc.org@localhost>
date:      Sat Dec 30 17:12:51 2017 +0000

description:
glibmm: Drop GCC_REQD from buildlink3.mk

As a hack for 2017Q4, I added GCC_REQD+=4.9 to glibmm's buildlink3.mk,
to make some fraction of glibmm-depending packages build on the
branch.  This commit reverts the bl3 addition (but leaves
GCC_REQD+=4.9 for glibmm itself).

The result will be that someone building pkgsrc with a compiler older
than gcc 4.9 will be able to build glibmm (via forcing 4.9), and
depending packages will fail.  This is much like the situation before
the previous commit, except that glibmm will build.

diffstat:

 devel/glibmm/buildlink3.mk |  7 +------
 1 files changed, 1 insertions(+), 6 deletions(-)

diffs (20 lines):

diff -r a6e4a6d59b84 -r f057f6f75479 devel/glibmm/buildlink3.mk
--- a/devel/glibmm/buildlink3.mk        Sat Dec 30 15:17:52 2017 +0000
+++ b/devel/glibmm/buildlink3.mk        Sat Dec 30 17:12:51 2017 +0000
@@ -1,15 +1,10 @@
-# $NetBSD: buildlink3.mk,v 1.16 2017/12/29 23:06:14 gdt Exp $
+# $NetBSD: buildlink3.mk,v 1.17 2017/12/30 17:12:51 gdt Exp $
 
 BUILDLINK_TREE+=       glibmm
 
 .if !defined(GLIBMM_BUILDLINK3_MK)
 GLIBMM_BUILDLINK3_MK:=
 
-# It is necessary to use the same compiler to link against libmm as it
-# was built with.  This is hacky, but enables at least
-# gnome-system-monitor to build.
-GCC_REQD+=             4.9
-
 BUILDLINK_API_DEPENDS.glibmm+= glibmm>=2.24.2
 BUILDLINK_ABI_DEPENDS.glibmm+= glibmm>=2.32.1nb1
 BUILDLINK_PKGSRCDIR.glibmm?=   ../../devel/glibmm