Date: Fri, 28 Mar 2014 00:11:02 +0100 From: John Marino <freebsd.contact@marino.st> To: Dimitry Andric <dim@FreeBSD.org>, Mark R V Murray <markm@FreeBSD.org> Cc: ports@freebsd.org, pizzamig <luca.pizzamiglio@gmail.com> Subject: Re: Port devel/gdb broken on 11-CURRENT amd64. Message-ID: <5334B006.1070805@marino.st> In-Reply-To: <1040C8F5-CA6A-4CC3-840A-64EB213C95EE@FreeBSD.org> References: <73962E64-42F0-4042-8647-2DE7C78005AB@FreeBSD.org> <a4182c74-d44d-449f-ae75-c8a1db0b5d86@email.android.com> <4AC81949-35A8-4760-BEFC-315DB278E41E@FreeBSD.org> <1040C8F5-CA6A-4CC3-840A-64EB213C95EE@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/27/2014 23:09, Dimitry Andric wrote: > On 24 Mar 2014, at 22:32, Mark R V Murray <markm@FreeBSD.org> wrote: >> >> On 24 Mar 2014, at 15:34, pizzamig <luca.pizzamiglio@gmail.com> wrote: >>> I've already got a report about that, but I'm on holiday, without a CURRENT system, I cannot work on it right now... >>> I guess CURRENT has a new clang version… >> >> Yup! It’s Clang v3.4. I’ve done a local dirty fix of ‘CFLAGS+=-Wno-error’ in the Port Makefile. I suspect it will need rather more than this to cover all the CLANG and GCC versions that are around. > > IMHO it is fairly ridiculous the port is compiled with -Werror. If we > were gdb developers, I could understand, but for contributed software it > does not make much sense. Maybe the maintainer can apply the following > patch, which I have literally had for years in my ports tree now. > agreed. FWIW, I applied a very similar patch to devel/gdb66 on 18 Nov 2013 because it was broken on head too. All gdb ports should disable this absurd build default. John
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5334B006.1070805>