I was not using git clone https://gitlab.synchro.net/main/sbbs.git and it seems fixed there (I change hard disk since yesterday, but using Xubuntu 22.04, yesterday Ubuntu 22.04). I looked at the modified thread.h file and it seems ok: paul@kasparno:~/sbbs/3rdp/build$ git log cl-linux-yield.patch commit 53264f2b0f20d28508ecdc611b7dfba385e27350 Author: Rob Swindell rob@synchro.net Date: Tue Oct 19 12:55:56 2021 -0700 Use shed_yield() instead of pthread_yield() on Linux Per https://man7.org/linux/man-pages/man3/pthread_yield.3.html...
cryptlib 3.4.6 (release candidate) have: elif defined( linux ) / Under newer versions of Linux, once they got the threading model sorted out via the NPTL vs. earlier LinuxThreads and others, sched_yield() == pthread_yield() (that is, pthread_yield() is just a wrapper for sched_yield() in pthread_yield.c). In addition some newer distros mangle the wrapper in glibc so that linking fails if we use pthread_yield() but not if we use sched_yield(). To deal with this, if the OS version is new enough that...
I believe the problem is that for Linux with GNU, PTHREAD_YIELD is wrongly defined as pthread_yield, but man pthread_yield say it is deprecated, and sched_yield() should be used instead. As explained in the thread.h of cl (cryptlib), sched_yield is the right choice after the standard confusion (two parralel versions, they were unsure which would be standardized). /syncterm-1.1/3rdp/src/cl/kernel/thread.h:3015 have: else #if defined( linux ) && !defined( __USE_GNU ) void pthread_yield( void ); #endif...
fmines: no source code
Used "setup adv" after rebooting after partitioning. Ignored HTMLHELP package. Installation finished. Installation worked after reboot.
Tried again, before installation, mem show largest exe size is 601kb, after (fail), 599kb. Would it loose 1.5kb memory each time it install a package?
Tried again, before installation, mem show largest exe size is 601kb, after (fail), 599kb.
I have tried: a: call freedos\setup\fdsetup.bat after it failed... it seems to complete, but: after that each line of the screen have "Out of memory error." ... and booting from hard disk after that hang.