I ran into some problems, specifically with the size of things. There is
no shared library support in ELKS, so merging several tools to enable
code sharing makes a lot of sense in ELKS. Unfortunately, at the time,
ELKS had serious problems running even the most basic of command-line
programs properly, such that even logging in would sometimes fail
perpetually. Things should be much better today, but I didn't feel like
working on it any longer. It would work if someone with a little C
coding skill massaged it a bit. The biggest challenge is keeping the
binaries small enough.
On 2/4/2020 1:33 PM, Marc-F. Lucca-Daniau wrote:
Hello,
The 'busyelks' is try to apply the same recipe as BusyBox, from Jody
Bruchon.
It is currently unmaintained, and kept archived until someone would
like to to resume his work.
MFLD
Le 04/02/2020 à 14:15, Marcin Laszewski a écrit :
Yes, you are right!
I have compiled sucessfuly ELKS many times and it was my first
defeat... sorry for my confiusion.
I've noticed there were 'busyelks' directory. Is it used now?
2020-02-01 11:46 GMT+01:00, Marc-F. Lucca-Daniau <mfld.fr@xxxxxxxxx>:
(...)
You should rather type the command: ". tools/env.sh" (with a space
(...)
