Thomas Dickey dixit:
>I created the macro after dealing with users who would put C preprocessor
>options in $CC
I think that, if you even want to detect it, you should only warn for it.
We sell rope so the user can shoot himself into the foot, after all.
> (which for lynx will cause it to not
>> Specifically, when I run it with CC set to cc -g, [...]
> I created the macro after dealing with users who would put C
> preprocessor options in $CC (which for lynx will cause it to not
> build the configuration summary page as expected, for ncurses will
> cause interesting build failures, etc)
On Thu, Feb 03, 2022 at 03:26:34PM -0500, Mouse wrote:
> I wrote, earlier today, of trying to rebuild a past lynx install,
> saying
>
> > This led me to rediscover that the configure script for that version
> > appears to be broken.
>
> I fetched the current .tar.bz2, which unpacked into
