Date: Mon, 22 Mar 2021 09:47:59 -0700 From: John Baldwin <jhb@FreeBSD.org> To: Guido Falsi <mad@madpilot.net>, "Hartmann, O." <ohartmann@walstatt.org>, FreeBSD Ports <freebsd-ports@freebsd.org> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: On 14-CURRENT: no ports options anymore? Message-ID: <0e0c17f6-a3ad-a8a0-492e-25e3c8688c70@FreeBSD.org> In-Reply-To: <8a39cc8f-df2b-8a43-54c4-44eebb4b12de@madpilot.net> References: <20210313201702.5f9dfa9b@hermann.fritz.box> <8a39cc8f-df2b-8a43-54c4-44eebb4b12de@madpilot.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/13/21 12:58 PM, Guido Falsi via freebsd-current wrote: > On 13/03/21 20:17, Hartmann, O. wrote: >> Since I moved on to 14-CURRENT, I face a very strange behaviour when trying to set >> options via "make config" or via poudriere accordingly. I always get "===> Options >> unchanged" (when options has been already set and I'd expect a dialog menu). >> This misbehaviour is throughout ALL 14-CURRENT systems (the oldest is at FreeBSD >> 14.0-CURRENT #49 main-n245422-cecfaf9bede9: Fri Mar 12 16:08:09 CET 2021 amd64). >> >> I do not see such a behaviour with 13-STABLE, 12-STABLE, 12.2-RELENG. >> >> How to fix this? What happened? > > I encountered something similar, some base shared library has changed, > guess this is related with the ncurses changes in base. > > If I remember correctly force reinstalling dialog4ports package fixed > it. Make sure you reinstall a freshly rebuilt one. > > Most probably anything using ncurses will require rebuild/reinstall. > > The cause is dialog4ports failing to start and the system sees no option > changed. > > If that's not enough try > > # ldd -v /usr/local/bin/dialog4ports > > And see if it reports some useful information. There was an ABI breakage for ncurses that broke 12.x dialog4ports binaries. The shared library versions for everything that depended on ncurses were bumped for 13 and 14 after the branch of stable/13.0 (commit 6e1fe6d26ea2). After that commit, if you upgraded from 12 to 13 you should have been fine, but if you had updated before that, the 12.x dialog4ports was still going to fail as the 12.x version of those libraries were already broken. I haven't checked to see if the affected libraries have been added to misc/compat12x. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0e0c17f6-a3ad-a8a0-492e-25e3c8688c70>