From owner-freebsd-ports-bugs@FreeBSD.ORG Mon Nov 26 16:50:04 2007 Return-Path: Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0057916A46E for ; Mon, 26 Nov 2007 16:50:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E556413C46E for ; Mon, 26 Nov 2007 16:50:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id lAQGo3va048138 for ; Mon, 26 Nov 2007 16:50:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id lAQGo3ss048137; Mon, 26 Nov 2007 16:50:03 GMT (envelope-from gnats) Date: Mon, 26 Nov 2007 16:50:03 GMT Message-Id: <200711261650.lAQGo3ss048137@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org From: Mikhail Teterin Cc: Subject: Re: ports/118257: graphics/libfpx fails to comile X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mikhail Teterin List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Nov 2007 16:50:04 -0000 The following reply was made to PR ports/118257; it has been noted by GNATS. From: Mikhail Teterin To: bug-followup@freebsd.org, aryeh.friedman@gmail.com Cc: Subject: Re: ports/118257: graphics/libfpx fails to comile Date: Mon, 26 Nov 2007 11:42:13 -0500 > Many warnings (all treated as errors) if default CFLAGS are used in the > Makefile That's the point. The library builds with the default compiler on 6.x and 7.x. If it hits an unexpected warning, I want to know about it :) If the build breaks on 8.x, then stricter warning flags must be in use -- either on your machine or on 8.x in general. For more details I'll need to see the build log. For an immediate work-around, set NO_WERROR while building. -mi