On 4/22/20 11:55 PM, Wolf wrote:
> On 2020-04-22 21:35:24 +0200, Tito wrote:
>> out of curiosity what are the mount options of your building directory?
>
> I'm building in ~/devel/busybox, which is directly on root partition (I
> do not have separate /home):
>
> + $ mount | grep ' / '
>
Hi,
Christophe
Le 23/04/2020 à 03:13, Chris Packham a écrit :
Hi,
I'm just in the process of updating our products to Linux v5.6 and one
of them produces a new warning message from the kernel about busybox
(v1.31.1)
kernel: process '/bin/busybox' started with executable stack
Got
Hi,
I'm just in the process of updating our products to Linux v5.6 and one
of them produces a new warning message from the kernel about busybox
(v1.31.1)
kernel: process '/bin/busybox' started with executable stack
The target in question is a mips64 (octeon3). We have other targets
(mips32,
On 2020-04-22 21:35:24 +0200, Tito wrote:
> out of curiosity what are the mount options of your building directory?
I'm building in ~/devel/busybox, which is directly on root partition (I
do not have separate /home):
+ $ mount | grep ' / '
/dev/mapper/storage-root on / type btrfs
On 4/22/20 5:00 PM, Tito wrote:
>
>
> On 4/22/20 4:17 PM, Wolf wrote:
>> Hello,
>>
>> I would like to ask about some tips for developing the busybox.
>> Currently I just
>>
>> make defconfig
>> make -j8
>>
>> which seems to work fine and produces busybox binary. However, making
>> tiny
On 4/22/2020 11:36 AM, Leesoo Ahn wrote:
hence we save a few cycles while parsing
But you are also suggesting adding bytes, right? This is the second
time you have proposed a patch that adds bulk to busybox to save a
little performance at runtime, which is the opposite of the goal of the
Hi,
Im currently trying to run parts of busybox (e.g. ash) on-top of VxWorks.
I made some progress and can run multiple apps.
With the newest version of VxWorks the clang compiler version 9.0.1.1 is
used
and now I face the same immediate segfault as described below.
I wonder why the
Line comments with '#' mark at the beginning are compared to
on every 'if' statement although those lines could be notified
as comments at the early stage.
It better skips them, hence we save a few cycles while parsing.
These tests are passed,
# comment type 1
# comment type 2
# comment
On 4/22/20 4:17 PM, Wolf wrote:
> Hello,
>
> I would like to ask about some tips for developing the busybox.
> Currently I just
>
> make defconfig
> make -j8
>
> which seems to work fine and produces busybox binary. However, making
> tiny change to findutils/grep.c (in my case)
Hello,
I would like to ask what is correct way to push forward patch in the
busybox project. I've posted patch to this mailing list, even attached
it to the bug report it fixes. And after 3 months I still did not hear
anything.
It would be nice to at least get some kind of reaction. If the patch
Hello,
I would like to ask about some tips for developing the busybox.
Currently I just
make defconfig
make -j8
which seems to work fine and produces busybox binary. However, making
tiny change to findutils/grep.c (in my case) and running the make again,
it rebuilds *lots* of
On 21 April 2020 14:14:50 CEST, Yannik Sembritzki wrote:
>I'm glad my message ended the unncessary github discussion.
>
>However, I'd still like to know who is in charge of maintaining
>git.busybox.net, so I can forward this suggestion to the right person.
We are doing this as time permits. I
The message comes up with ./busybox tc qdisc show dev
$ grch "command line is not complete"
./networking/libiproute/utils.c:233:
bb_simple_error_msg_and_die("command line is not complete, try \"help\"");
Leesoo
20. 4. 22. 오후 2:37에 Tito 이(가) 쓴 글:
On 4/21/20 11:18 PM, Tom Lee wrote:
`tc:
13 matches
Mail list logo
