Date: Sun, 07 Jul 2013 17:30:33 +0400 From: Ilya A. Arkhipov <rum1cro@yandex.ru> To: O. Hartmann <ohartman@zedat.fu-berlin.de>, Marco Steinbach <coco@executive-computing.de> Cc: FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: make config: doesn't work - reports ===> Options unchanged : no options menu popping up Message-ID: <36691373203833@web19h.yandex.ru> In-Reply-To: <20130707151733.23f5e735@thor.walstatt.dyndns.org> References: <20130707122551.0a6bca03@thor.walstatt.dyndns.org> <51D960D5.5060503@executive-computing.de> <20130707151733.23f5e735@thor.walstatt.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
07.07.2013, 17:17, "O. Hartmann" <ohartman@zedat.fu-berlin.de>: > On Sun, 07 Jul 2013 14:36:37 +0200 > Marco Steinbach <coco@executive-computing.de> wrote: > >> šO. Hartmann wrote on 07.07.2013 12:25: >>> šOn boxes running recent /usr/ports and recent soutces( FreeBSD >>> š10.0-CURRENT #0 r252885: Sat Jul š6 16:09:09 CEST 2013) I'm unable >>> što configure some ports, for instance www/firefox: >>> >>> š/usr/ports/www/firefox # make config >>> š===> Options unchanged >>> >>> šEven performing "make rmconfig" and repeating above procedure >>> šdoesn't change anything. I can not change options anymore! >>> >>> šPlease CC me, I'm not subsrcribing the list. >> š[...] >> >> šI've seen this kind of behaviour with dialog4ports in various >> šsituations, but since dialog4ports-0.1.1 or so, I've never >> šencountered this again. >> >> šHere's a few shots in the dark: >> >> š- Maybe you're running an outdated version of dialog4ports. šRemove >> šdialog4ports, then make config in www/firefox again. šThis will >> štrigger installation of whatever the most recent version of >> šdialog4ports is in your ports tree. >> š- Check your environment. šUnset DIALOG4PORTS or DIALOG, if they're >> šset, then try make config again. >> >> šMfG CoCo > > Thanks for the hint. > > rebuilding dialog4ports made the problem go away. > > It is strange. I usually have up to date ports, even dialog4ports. But > since this happens on CURRENT (I didn't see this on 9.1-STBALE yet) I > guess it is due to CURRENT is a moving target ... > > Regards, > Oliver Hi Oliver, Seems it was related with update libdialog in current after that was broken ABI... rebuild d4p will fix this problem. -- With Best Regards, Ilya A. Arkhipov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?36691373203833>