Date: Mon, 24 Apr 2017 19:55:45 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 218856] devel/valgrind devel/valgrind-devel: Properly detect clang 5.0.0 Message-ID: <bug-218856-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218856 Bug ID: 218856 Summary: devel/valgrind devel/valgrind-devel: Properly detect clang 5.0.0 Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: bdrewery@FreeBSD.org Reporter: dim@FreeBSD.org Assignee: bdrewery@FreeBSD.org Flags: maintainer-feedback?(bdrewery@FreeBSD.org) Created attachment 182055 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D182055&action= =3Dedit Fix clang 5 detection for valgrind I'm doing preliminary tests with clang 5.0.0 in the projects/clang500-import branch, and it turned out that devel/valgrind and devel/valgrind-devel fail= to detect the version. This is because of a case statement with: clang-2.9|clang-3.*|clang-4.*) Here's a patch that adds clang-5.* for now (upstream might want to think ab= out extending this to any correct numerical version). It also drops the USE_GCC from the Makefiles, which is apparently something added by Baptiste to supp= ort FreeBSD 8, so it is no longer necessary. --=20 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-218856-13>