Date: Wed, 19 Apr 2017 13:05:40 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 218752] net/asterisk11 - Problem with the asterisk console when linked to the latest version of libedit Message-ID: <bug-218752-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218752 Bug ID: 218752 Summary: net/asterisk11 - Problem with the asterisk console when linked to the latest version of libedit Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: madpilot@FreeBSD.org Reporter: yani@pi-greece.eu Assignee: madpilot@FreeBSD.org Flags: maintainer-feedback?(madpilot@FreeBSD.org) Created attachment 181896 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D181896&action= =3Dedit Patch to use the internal libedit library Hello, I'm getting some strange console behaviour when asterisk is linked to the latest version of the libedit library (3.1.20170329_2,1). Typing any comman= d in the console (asterisk -r) displays unicode codes instead of the actual input (e.g. typing "c" echoes "\U+AD263"). The same problem was reported in Digiu= m's forum about a year ago: https://community.asterisk.org/t/cli-gibberish-prompt-and-input-appear-to-b= e-some-sort-of-unicode-characters/67382 The fix is to pass "--with-libedit=3Dinetrnal" to the configure script to u= se the internal libedit library. I'm attaching a Makefile patch. --=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-218752-13>