Date: Tue, 14 Jul 2020 17:45:47 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 247976] pkg-config produces icorrect linkage information about libncursesw Message-ID: <bug-247976-7788-oMLg3huiPZ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-247976-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-247976-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D247976 Yuri Pankov <yuripv@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |yuripv@FreeBSD.org --- Comment #1 from Yuri Pankov <yuripv@FreeBSD.org> --- FWIW, pkg-config output is correct as the base ncurses does not provide a .= pc file and you get correct paths for the ports library. Also, on -CURRENT I have the "=D0=9F=D1=80x" result linking with ncursesw i= n base, which seems to be correct as you insert 2 characters from the word "=D0=9F=D1=80= =D0=B8=D0=B2=D0=B5=D1=82", that is, "=D0=9F=D1=80", and same result linking with ncursesw from ports. The issue seems to be in the base ncursesw library on the release that you = are running -- which one, BTW? BTW, the answer you got on stackoverflow is incorrect -- the 'n' argument to mbstowcs() specificies the number of *wide* characters to be stored, not the number of bytes to consume from multibyte string. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-247976-7788-oMLg3huiPZ>