From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Cc: buildroot@uclibc.org
Subject: Re: [Buildroot] sftp-server for use with dropbear?
Date: Thu, 1 Sep 2022 20:32:01 -0000 (UTC) [thread overview]
Message-ID: <ter4s1$s24$1@ciao.gmane.io> (raw)
In-Reply-To: ter3cg$lbs$1@ciao.gmane.io
On 2022-09-01, Grant Edwards <grant.b.edwards@gmail.com> wrote:
> There's no way I can justify rebuilding the toolchain with uClibc
> wchar support enabled for gesftpserver when nothing else in my system
> needs wchar support. I'll have to figure out a new test/development
> workflow that doesn't use "scp" to copy files onto the target.
It looks like the only place wchar support is used is in a couple
spots in sftpclient in the interactive output handling where somebody
is trying to keep things pretty by checking how many display columns
will be occupied by a filename before it's printed using
printf(). [For example in the output of the the "ls" command built in
to the client, it tries to figure out how many columns of filenames to
print, and how to pad them to keep things aligned.]
The server doesn't need wchar support at all.
So the easiest option for me is probably to change the .mk file to
just build/install the server and not the client. I suppose the proper
thing to do would be to change the Config.in file so that building the
client is optional and wchar support is only required when the client
is built.
Or I could patch the client so that if libc doesn't have wchar
support, it assumes that number_of_columns(filename) ==
strlen(filename). People without wchar support who use UTF8 filenames
would have to tolerate columns that don't line up in the output from
the "ls" command.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-09-01 20:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 18:41 [Buildroot] sftp-server for use with dropbear? Grant Edwards
2022-09-01 18:58 ` Yann E. MORIN
2022-09-01 19:25 ` Grant Edwards
2022-09-01 19:48 ` Yann E. MORIN
2022-09-01 20:06 ` Grant Edwards
2022-09-01 20:32 ` Grant Edwards [this message]
2022-09-01 22:02 ` Grant Edwards
2022-09-08 23:21 ` Grant Edwards
2022-09-01 20:51 ` Thomas Petazzoni via buildroot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ter4s1$s24$1@ciao.gmane.io' \
--to=grant.b.edwards@gmail.com \
--cc=buildroot@busybox.net \
--cc=buildroot@uclibc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox