bug-ncurses
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

SOLVED: Help wanted with bkgd() rookie mistake


From: G. Branden Robinson
Subject: SOLVED: Help wanted with bkgd() rookie mistake
Date: Sun, 5 Jan 2025 13:39:19 -0600

At 2025-01-05T13:30:06-0600, G. Branden Robinson wrote:
> Yes--I forgot, if I ever knew, that my ncurses builds don't create an
> "ncurses6-config" program...just "ncurses6w-config".  The former is
> found in /usr/bin, and the latter both in /usr/bin and
> $HOME/ncurses-HEAD/bin, with the latter winning because $PATH.
> 
> So when I test "narrow" ncurses, I've only ever been testing Debian's
> ncurses5 packages.  Oh great.  Well, I know now.

And yup--that was it.

bkgd.c works as expected now, with no changes.

The issue here was not a programming goof, but a system configuration
management problem.  When measuring the behavior of a library, it helps
to evaluate the version of interest instead of a 4-year old specimen.

> I'm thinking what I probably want to do is use the same compiler flags
> for all of my test scripts, and distinguish them only by the API they
> elect to use.  It's not like libncursesw.so.6 is missing the narrow
> entry points.

Because the previous one was so embarrassing, I'm attaching my new
Makefile.  Now with 73.9% less derp.

Thanks, Thomas and Bill, for steering me away from incorrect
explanations.

Regards,
Branden

Attachment: Makefile
Description: Makefile

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]