Re: [PATCH v4] tree: new applet

On Mon, 2 May 2022 01:40:39 +0800 Kang-Che Sung wrote: > Hi Roger, > > May I suggest you add an option to draw the tree lines using ASCII > characters only, and make the Unicode support optional at build time? > > I just feel uncomfortable when I see source code contain

Re: [PATCH v4] tree: new applet

Hi Roger, May I suggest you add an option to draw the tree lines using ASCII characters only, and make the Unicode support optional at build time? I just feel uncomfortable when I see source code containing embedded UTF-8 characters and the strings have no ASCII alternative. The DOS tree

Re: [PATCH v4] tree: new applet

On Sun, 01 May 2022 12:51:16 + Roger Knecht wrote: > Add new applet which resembles the MS-DOS tree program to list directories > and files in a tree structure. > > function old new delta

[PATCH v2 2/2] tree-wide: use xopen_as

Typical saving per callsite (on x86-64) is 7 bytes, so net win at 3 conversions. function old new delta xopen_as - 18 +18 xargs_main 871 864

[PATCH 2/2] tree-wide: use xopen_fd

Typical saving per callsite (on x86-64) is 7 bytes, so net win at 3 conversions. function old new delta xopen_fd - 18 +18 xargs_main 871 864

Re: Out-of-tree build broken

lo busybox overlords, >> >> I have a fresh checkout of busybox version 1.31.1 (git hash >> bd754746394a382e04d116df02547f61b2026da9), and I’m trying to build it on >> Ubuntu 18.04 with gcc 7.4 with an out-of-tree build (per per >> https://github.com/jgunthorpe/busybox/

Re: Out-of-tree build broken

On Tue, Oct 29, 2019 at 1:49 AM Samuel Ainsworth wrote: > > Hello busybox overlords, > > I have a fresh checkout of busybox version 1.31.1 (git hash > bd754746394a382e04d116df02547f61b2026da9), and I’m trying to build it on > Ubuntu 18.04 with gcc 7.4 with an out-of-tree build

Re: Out-of-tree build broken

Correction: the actual out-of-tree building link is https://github.com/mirror/busybox/blob/master/INSTALL#L125 <https://github.com/mirror/busybox/blob/master/INSTALL#L125>. > On Oct 28, 2019, at 5:49 PM, Samuel Ainsworth wrote: > > Hello busybox overlords, > > I

Out-of-tree build broken

Hello busybox overlords, I have a fresh checkout of busybox version 1.31.1 (git hash bd754746394a382e04d116df02547f61b2026da9), and I’m trying to build it on Ubuntu 18.04 with gcc 7.4 with an out-of-tree build (per per https://github.com/jgunthorpe/busybox/blob/master/INSTALL#L95 <ht

Re: tree

On Wed, May 3, 2017 at 6:00 AM, Jethro Tull <heavyt...@hotmail.com> wrote: > why tree is not in busybox? Short answer: Because no one has been implementing it in Busybox yet. ___ busybox mailing list busybox@busybox.net http://lists.busybox.ne

tree

why tree is not in busybox? ___ busybox mailing list busybox@busybox.net http://lists.busybox.net/mailman/listinfo/busybox

Re: ash parse tree and stack boundaries

On Tue, Nov 30, 2010 at 1:57 PM, Phil Carmody ext-phil.2.carm...@nokia.com wrote: There's a problem in busybox ash, which is running out of stack when parsing very long input (funnily same bug also exists in bash), like $ for i in $(seq 10); do echo -n :;; done | busybox sh

Re: ash parse tree and stack boundaries

On Mon, Nov 29, 2010 at 2:47 PM, Alexander Shishkin virtu...@slind.org wrote: I'm thinking of how to go about solving it. 1) introduce recursion depth counter to all the eval*() functions; stack limits might differ, thus calculating the maximum depth might be tricky and error prone; How

ash parse tree and stack boundaries

Hi, There's a problem in busybox ash, which is running out of stack when parsing very long input (funnily same bug also exists in bash), like $ for i in $(seq 10); do echo -n :;; done | busybox sh Segmentation fault which happens in evaltree() calling itself for each : node. Now, I'm

Re: ash parse tree and stack boundaries

On Mon, Nov 29, 2010 at 2:47 PM, Alexander Shishkin virtu...@slind.org wrote: Hi, There's a problem in busybox ash, which is running out of stack when parsing very long input (funnily same bug also exists in bash), like $ for i in $(seq 10); do echo -n :;; done | busybox sh Segmentation

Re: [PATCH] Fix out-of-tree build's recursion

On Thursday 15 July 2010 16:39, Alexander Shishkin wrote: While doing O=build build I've noticed that it was getting gradually slower with each invocation. The reason turned out to be that the build directory was inside the source tree and got recreated inside itself with all its

[PATCH] Fix out-of-tree build's recursion

While doing O=build build I've noticed that it was getting gradually slower with each invocation. The reason turned out to be that the build directory was inside the source tree and got recreated inside itself with all its subdirectories. This patch changes the behavior so that only

Re: Failing out-of-tree build since r26139

On Saturday 18 April 2009 19:15, Bjørn Forsman wrote: Hi all, I have found that BusyBox SVN r26139 (and up to the latest r26151) breaks out-of-tree builds. r26138 works. Below is the log of my breaking r26139 build: busybox $ make O=../../build/busybox/ install Using /media/raid

Re: Failing out-of-tree build since r26139

2009/4/19 Denys Vlasenko vda.li...@googlemail.com On Saturday 18 April 2009 19:15, Bjørn Forsman wrote: Hi all, I have found that BusyBox SVN r26139 (and up to the latest r26151) breaks out-of-tree builds. r26138 works. Below is the log of my breaking r26139 build: busybox $ make O

Re: Failing out-of-tree build since r26139

with attached file? No, it still fails with the same error. Hmm # This trick decreases amount of rebuilds # if tree is merely renamed/copied ifeq ($(src),$(obj)) Can you replace this last line with ifeq ($(srctree),$(objtree)) and try again? -- vda srctree_slash = else srctree_slash

Re: Failing out-of-tree build since r26139

into this :-) Does it work if you replace applets/Kbuild with attached file? No, it still fails with the same error. Hmm # This trick decreases amount of rebuilds # if tree is merely renamed/copied ifeq ($(src),$(obj)) Can you replace this last line with ifeq ($(srctree

Failing out-of-tree build since r26139

Hi all, I have found that BusyBox SVN r26139 (and up to the latest r26151) breaks out-of-tree builds. r26138 works. Below is the log of my breaking r26139 build: busybox $ make O=../../build/busybox/ install Using /media/raid/bjornfor/documents/dev/os/linux/minibuildroot/src/busybox as source

RE: Current git tree broke busybox start-stop-daemon

-Original Message- From: Alexey Dobriyan [mailto:[EMAIL PROTECTED] Sent: den 16 april 2008 21:47 To: Al Viro Cc: Joakim Tjernlund; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Current git tree broke busybox start-stop-daemon On Wed, Apr 16, 2008 at 08:34:17PM +0100, Al Viro

Re: start-stop-daemon broke on linus tree

-stop-daemon broke on linus tree On Wednesday 16 April 2008 19:56, Joakim Tjernlund wrote: Just sent this to the kernel list, figured you might want a copy too, see last in this mail. One more note, stracing strace -s 120 start-stop-daemon --stop --exec /opt/appl/cuappl02a

Re: start-stop-daemon broke on linus tree

To: busybox@busybox.net; [EMAIL PROTECTED] Subject: Re: start-stop-daemon broke on linus tree On Wednesday 16 April 2008 19:56, Joakim Tjernlund wrote: Just sent this to the kernel list, figured you might want a copy too, see last in this mail. One more note, stracing

Re: start-stop-daemon broke on linus tree

On Wednesday 16 April 2008 19:56, Joakim Tjernlund wrote: Just sent this to the kernel list, figured you might want a copy too, see last in this mail. One more note, stracing strace -s 120 start-stop-daemon --stop --exec /opt/appl/cuappl02a-r11a-080416jt2/sbin/dropbear shows alot of

RE: start-stop-daemon broke on linus tree

-Original Message- From: Denys Vlasenko [mailto:[EMAIL PROTECTED] Sent: den 16 april 2008 20:47 To: busybox@busybox.net; [EMAIL PROTECTED] Subject: Re: start-stop-daemon broke on linus tree On Wednesday 16 April 2008 19:56, Joakim Tjernlund wrote: Just sent this to the kernel