From owner-freebsd-current@freebsd.org Sat Jan 23 23:14:14 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1EB7C4E1B64 for ; Sat, 23 Jan 2021 23:14:14 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (phouka1.phouka.net [107.170.196.116]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "phouka.net", Issuer "Go Daddy Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DNX511vNmz3Lwp for ; Sat, 23 Jan 2021 23:14:12 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (localhost [127.0.0.1]) by phouka1.phouka.net (8.16.1/8.16.1) with ESMTPS id 10NNCtRR040092 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sat, 23 Jan 2021 15:12:55 -0800 (PST) (envelope-from warlock@phouka1.phouka.net) Received: (from warlock@localhost) by phouka1.phouka.net (8.16.1/8.16.1/Submit) id 10NNCtTR040091; Sat, 23 Jan 2021 15:12:55 -0800 (PST) (envelope-from warlock) Date: Sat, 23 Jan 2021 15:12:55 -0800 From: John Kennedy To: Kostya Berger Cc: FreeBSD Current Subject: Re: 13-alpha2 libncurses removal breaks ports build Message-ID: References: <992972141.8836030.1611441657314.ref@mail.yahoo.com> <992972141.8836030.1611441657314@mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <992972141.8836030.1611441657314@mail.yahoo.com> X-Rspamd-Queue-Id: 4DNX511vNmz3Lwp X-Spamd-Bar: / X-Spamd-Result: default: False [-0.45 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[107.170.196.116:from]; NEURAL_SPAM_SHORT(0.35)[0.352]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[phouka.net]; AUTH_NA(1.00)[]; SPAMHAUS_ZRD(0.00)[107.170.196.116:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[no SPF record]; FREEMAIL_TO(0.00)[yahoo.co.uk]; FORGED_SENDER(0.30)[warlock@phouka.net,warlock@phouka1.phouka.net]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:14061, ipnet:107.170.192.0/18, country:US]; FROM_NEQ_ENVFROM(0.00)[warlock@phouka.net,warlock@phouka1.phouka.net]; MAILMAN_DEST(0.00)[freebsd-current]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Jan 2021 23:14:14 -0000 On Sat, Jan 23, 2021 at 10:40:57PM +0000, Kostya Berger wrote: > Hi everyone,I don't seem to find any mentioning in the /usr/ports/UPDATING about how one should handle the removal of libncurses.so.9 from base. > Source UPDATING only says:ncurses installation has been modified to only keep the widechar >         enabled version.  Incremental build is broken for that change, so it >         requires a clean build. > If that means to just build all ports anew, then it doesn't work as ports don't seem to incorporate any change related to this one. It would seem default configuration should take into account this, but it doesn't. So you found the right note, but yes, it sort of buried the lead. I've found with that and a few other libraries that I tend to get burned when you hit the "make delete-old-libs" phase of kernel installation, where the first clean-room poudriere port build still has them available for the ports to find. I usually end up re-rebuilding the kernel+world (so everything is now rebuilt without those removed libraries), updating poudriere with that, and doing a full ports recompile. If you're not rebuilding your own ports (probably really dodgy during this part of the release schedule) then you're probably just going to have to wait.