pkg/59941: Pkg "static-tcsh" does not support UTF-8 input.
| Newsgroups | gmane.os.netbsd.devel.pkgsrc.bugs |
|---|---|
| Message-ID | <[email protected]> |
>Number: 59941 >Category: pkg >Synopsis: Pkg "static-tcsh" does not support UTF-8 input. >Confidential: no >Severity: non-critical >Priority: low >Responsible: pkg-manager >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Sun Jan 25 09:40:00 +0000 2026 >Originator: Lars-Johan Liman >Release: NetBSD 10.1/pkgsrc-10.1 (probably 1025Q4) >Organization: Cafax AB >Environment: NetBSD server.liman.net 10.1 NetBSD 10.1 (GENERIC) #0: Mon Dec 16 13:08:11 UTC 2024 [email protected]:/usr/src/sys/arch/amd64/compile/GENERIC amd64 (but it seems to be platform independent.) >Description: (I thought I had reported this, but I cannot find in the PR DB, so trying again ...) When using tcsh from the package "static-tcsh", the shell does not accept UTF-8 input on the command line. When using tcsh from the (dynamically linked) package "tcsh" it does. Something must be different in the build processes, but I don't know what. I've seen the problem for a loooong time (10 years? 20 years?). I thought it was a drawback with tcsh on NetBSD in general, but I just realised it's limited to the static-tcsh package. It is not platform-dependant. I see the same problem on my amd64 (PC) and evbarm (Raspberry Pi) machines. >How-To-Repeat: # tail -1 /usr/pkg/etc/pkgin/repositories.conf <--- checking pkgin config http://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/10.1/All # setenv LANG en_US.UTF-8 (... or "LANG=en_US.UTF-8; export LANG", if starting from a Bourne-type shell) # pkgin install tcsh ... ... # /usr/pkg/bin/tcsh # öäååöÖÄÅÄÖ <--- typing random UTF-8 characters, works fine öäååöÖÄÅÄÖ: Command not found. <--- as expected! # exit exit # pkgin rm tcsh ... ... # /usr/pkg/bin/tcsh <--- verifying that tcsh has been removed /usr/pkg/bin/tcsh: Command not found. # pkgin install static-tcsh ... ... # /usr/pkg/bin/tcsh # <--- trying to type the same as above, nothing happens. # exit exit >Fix: Nope. Sorry.