I made some patches for this to fix a few bugs, but I never have the time to format them in a way that would get approved for submission to the ports tree.
Chris KQ6UP
Sent from my iPhone
> On Nov 15, 2025, at 11:33 AM, Ramiro Aceves <ea1abz%gmail.com@localhost> wrote:
>
>
>
>> El 15/11/25 a las 18:51, David H. Gutteridge escribió:
>>
>> The dillo issue is because of deliberate changes made in NetBSD 11,
>> please see for example this thread:
>> https://mail-index.netbsd.org/tech-pkg/2025/10/04/msg031586.html
>> Really it would need to be patched to fix those bugs. (Along with
>> many other packages, I suspect...)
>> Regards,
>> Dave
>
> Hi David:
>
> Yesss,
>
>
> packardbell_netbsd$ LIBC_ALLOWCTYPEABUSE="TRUE" dillo
>
>
> and dillo works now on www.netbsd.org WEB page!
>
> It says those messages on the console:
>
> ctype(3) isspace: invalid input: -62
> ctype(3) isspace: invalid input: -69
> ctype(3) isspace: invalid input: -62
> ctype(3) isspace: invalid input: -96
> ctype(3) isspace: invalid input: -62
> ctype(3) isspace: invalid input: -69
> ctype(3) isspace: invalid input: -62
> ctype(3) isspace: invalid input: -96
> ctype(3) isspace: invalid input: -62
> ctype(3) isspace: invalid input: -62
> ctype(3) isspace: invalid input: -96
> ctype(3) isspace: invalid input: -62
> ctype(3) isspace: invalid input: -85
> ctype(3) isspace: invalid input: -62
> ctype(3) isspace: invalid input: -69
> ctype(3) isspace: invalid input: -62
> ctype(3) isspace: invalid input: -96
> ctype(3) isspace: invalid input: -62
> ctype(3) isspace: invalid input: -69
> ctype(3) isspace: invalid input: -62
> ctype(3) isspace: invalid input: -87
> ctype(3) isspace: invalid input: -62
> ctype(3) isspace: invalid input: -82
> ^[[6~
>
>
>
> Thanks so much for the workaround.
>
> Ramiro.
>
>