Date: Sat, 04 Jul 2015 20:39:26 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 201341] devel/rocksdb: define BROKEN_DragonFly Message-ID: <bug-201341-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201341 Bug ID: 201341 Summary: devel/rocksdb: define BROKEN_DragonFly Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: marino@FreeBSD.org I don't have time for these games: https://lists.freebsd.org/pipermail/svn-ports-all/2015-July/098544.html Three consecutive versions of this port have failed on gcc because it generates warnings on modern GCC and -Werror is set. Clearly upstream does not test their product on modern GCC, so -Werror is even a worse idea than normal. I don't want to get involved in a commit war or yet another proposal to strength the policy against horrible -Werror, so please just set "Broken_DragonFly= will not build on GCC with -Werror" This s/w has broken 3 consecutive times so as long as -Werror is set (against recommendations) then let's just mask it to forget about it. -- 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-201341-13>