Gregory Haerr

> Build finished just now. Over 2h. It sounds like its rebuilding the toolchain. If not, and you can somehow capture the log and post it, I can see what...

On my system (MacBook Pro 16G RAM): ``` time make kclean 3.5s time make 24.5s ```

> As far as I can tell, it's these dokcleans. Each takes a very long time, with low cpu usage. I do notice that that recursive dokclean does run "slow"...

Are you saying that running `make kclean` is taking hours?!?!! We definitely need to figure that out. Good news is that you don't actually have to run `make kclean` after...

It is also possible that your shell wildcard expansion is taking forever...: ``` for DIR in */ ; do \ if [ -f "$DIR/Makefile" -a "$DIR" != "tools" ]; then...

It sounds like there is something wrong with your `make`, `/bin/sh`, or possibly glob expansion. ELKS is using an older, but Linux kernel standard, make system. I am investigating this...

Try putting copying this to /tmp/rec.sh and then running `/tmp/rec.sh` from the elks home dir: ``` #!/bin/sh for DIR in */ ; do if [ -f "$DIR/Makefile" -a "$DIR" !=...

Get some sleep! When you wake up, consider: > This is slower than it should be, but not that slow. 1.4s to just wildcard expand a few directories and echo...

Hello @rvalles, Do you happen to have another NE2K-style network card around? I'm pretty sure the networking works well, but thought that direction might be easier given how long it...

Hello @AirmanKaluga, I am not entirely sure I understand your request - are you wanting to write an ELKS device driver, similar to the "direct floppy driver" which will access...