From owner-freebsd-ports@FreeBSD.ORG Sat Jul 28 16:25:35 2012 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 59E40106566B; Sat, 28 Jul 2012 16:25:35 +0000 (UTC) (envelope-from thomas.e.zander@googlemail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 293568FC08; Sat, 28 Jul 2012 16:25:35 +0000 (UTC) Received: by pbbro2 with SMTP id ro2so7392138pbb.13 for ; Sat, 28 Jul 2012 09:25:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=NZdu4qe1/3Ei0HC/wORGCBu8M3ASmyj+gbOdjB4LtjI=; b=pn43kMp5Gk5A1u+47e3a3kRQAj0CVrj9oJxbZODJRaqnHi87q0zEcDJQNlocsVRjob Uv5BxqrzMeGF9Y2SatHTa3Isr20hI1hUQZIJ61FeYllR0MoGdhhMTpa79ayBZ3IbgSc8 IFW8RAwRncwuhEtXgkXaWfbssxKVZibPz+1wWBO8AK8nCeOwymNe35qDV3YuQPzl9xqQ yr3oED3kNLAbsda67T5ncq9c5YySpXg3Ovvc4FIbwubPV85NXTI0n5zHAQBC6kz4MMCT cvWCPWC9xPSx2YM2uJmtnm13L5p5g+BNe2JpDdPZgaGoYZWEiXHG4OBUvisHfSV+fO0H NoIQ== MIME-Version: 1.0 Received: by 10.68.217.37 with SMTP id ov5mr22529352pbc.12.1343492734408; Sat, 28 Jul 2012 09:25:34 -0700 (PDT) Received: by 10.68.194.66 with HTTP; Sat, 28 Jul 2012 09:25:34 -0700 (PDT) In-Reply-To: <4FD65C64.3080001@FreeBSD.org> References: <4FD65C64.3080001@FreeBSD.org> Date: Sat, 28 Jul 2012 18:25:34 +0200 Message-ID: From: Thomas Zander To: Andriy Gapon Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD Ports , "Mikhail T." Subject: Re: graphics/libfpx: use of bsd.lib.mk and warnings X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jul 2012 16:25:35 -0000 On Mon, Jun 11, 2012 at 11:00 PM, Andriy Gapon wrote: > I see that graphics/libfpx uses a custom FreeBSD-specific makefile which makes > use of bsd.lib.mk and sets WARNS to 3. > I think that this is an unsustainable approach. > First, the external libraries are not under our control and may adhere to some > different policy with respect to warnings. > Second, different compilers (gccXY, clang) may be used to compile ports and they > may produce new warnings-come-errors. It also causes the port to use clang when setting CC=clang in /etc/src.conf (!) which fails here. I am truly and utterly surprised that nobody seems to have this problem. Riggs