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:06:40 -0000 (UTC) [thread overview]
Message-ID: <ter3cg$lbs$1@ciao.gmane.io> (raw)
In-Reply-To: 20220901194825.GM68979@scaer
On 2022-09-01, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
>>> What about gesftpserver, that has been present since Buildroot 2013.02?
>> I currently can't select it in "menuconfig" because it requires a
>> toolchain with wchar support. I think my (exernal) toolchain does
>> have wchar support, but apparently buildroot hasn't been told about
>> it...
Rats. I was wrong. I assumed my toolchain had wchar support because
usr/include/wchar.h existed, but it's a stub:
$ cat ./arm-unknown-linux-uclibcgnueabi/sysroot/usr/include/wchar.h
/* This wchar.h is used if wchar support is disabled in uClibc.
* We still want to provide a few basic definitions as the basic
* C standard requires them. And it makes our lives easier with
* no additional overhead.
*/
...
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.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-09-01 20:06 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 [this message]
2022-09-01 20:32 ` Grant Edwards
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='ter3cg$lbs$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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.