From owner-freebsd-bugs@FreeBSD.ORG Thu Oct 16 16:06:49 2014 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2FDADA6B for ; Thu, 16 Oct 2014 16:06:49 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 16664A9F for ; Thu, 16 Oct 2014 16:06:49 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s9GG6m5E087066 for ; Thu, 16 Oct 2014 16:06:48 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 194401] bsd.port.mk's OSVERSION change interferes with option WITHOUT_TOOLCHAIN in src.conf Date: Thu, 16 Oct 2014 16:06:49 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 10.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: brooks@FreeBSD.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Oct 2014 16:06:49 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194401 --- Comment #2 from Brooks Davis --- Sorry, missed your examples in the first message. I apologize for not reading carefully. The first two cases seem like the sort of thing we'd like to note support as they could be harmful to the project. It really don't make sense to update a port if you can't build it. The error message suggests a perfectly functional workaround. Why is that not acceptable? Just add: OSVERSION!=sysctl -n kern.osreldate to your make.conf or put in your environment. -- You are receiving this mail because: You are the assignee for the bug.