From owner-freebsd-ports-bugs@freebsd.org  Sat Jan 14 13:29:18 2017
Return-Path: <owner-freebsd-ports-bugs@freebsd.org>
Delivered-To: freebsd-ports-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6E580CAF3C7
 for <freebsd-ports-bugs@mailman.ysv.freebsd.org>;
 Sat, 14 Jan 2017 13:29:18 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
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 504C61A87
 for <freebsd-ports-bugs@FreeBSD.org>; Sat, 14 Jan 2017 13:29:18 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v0EDTIVJ091951
 for <freebsd-ports-bugs@FreeBSD.org>; Sat, 14 Jan 2017 13:29:18 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-ports-bugs@FreeBSD.org
Subject: [Bug 216038] databases/sqlite3 fails to build undefined reference to
 `strchrnul'
Date: Sat, 14 Jan 2017 13:29:18 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Ports & Packages
X-Bugzilla-Component: Individual Port(s)
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: genie@geniechka.ru
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org
X-Bugzilla-Flags: maintainer-feedback?
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-216038-13-s87HGc4KJq@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-216038-13@https.bugs.freebsd.org/bugzilla/>
References: <bug-216038-13@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-ports-bugs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Ports bug reports <freebsd-ports-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports-bugs/>
List-Post: <mailto:freebsd-ports-bugs@freebsd.org>
List-Help: <mailto:freebsd-ports-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Jan 2017 13:29:18 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216038

--- Comment #2 from Eugene R <genie@geniechka.ru> ---
(1) Does a recent EoL of a legacy release ("Legacy releases are for users
wishing to stay with a more conservative upgrade strategy") means intention=
ally
breaking perfectly working installations? Sounds kinda Microsoftish to me.

(2) Even if we decide that a port now must not work in a previous release
anymore, should not this be handled by the 'required version', 'ignored' or
similar option rather than by breaking the build process?

--=20
You are receiving this mail because:
You are the assignee for the bug.=