🚀 go-pugleaf

In article <2083@ultb.isc.rit.edu> rxg3321@ultb.isc.rit.edu (R.X. Getter ) writes:
>I'm using the Sozobon C compiler, which is supposed to be Alcyon
>compatible, and it compiles RTXBIND.S to RTXBIND.O fine, and then
>I put it in my libraries directory and #include <RTXBIND.H>, but
>I can't get my programs to link with it. Can anyone tell me how
>to fix this problem?
Are you passing the rtxbind.o to the linker explicitly, or have you
put it in your dlibs.a ? just putting it in the lib directory won't work.

>for Fforce? or does micrortx patch Fforce? micrortx seems like a 
>fantastic package, and I will register for it if I can use it
>effectively.

I really think it's worth the price. If you are using dlibs, you will
have to change initargs.c in the last part, where it tries to get
the program name from the parent memory (I guess). the line containing
something like p= *(p + 0x36) (I think) must be checked if p != NULL,
and argv[0] set to something reasonable, else the program will crash.

That means you have to recompile all programs that were compiled with
dLibs (of course, even the compiler, linker etc.) if you want to
use them under RTX.

I've build a small root program, a "backgrounder" (i.e., a program that
can be accessed from other programs and starts background jobs), and a
cron utility last weekend. I am starting gulam as the main shell from
the root program and am very happy with RTX doing all the background work
(hopefully also running uucp etc.)

If there is enough interest, I might post the sources after some cosmetic
cleanups, so others may avoid doing the same mistakes that I made 8-) .

Michael
-- 
_____________________________________________________________________________
Michael Vishchers                                     (michaelv@watzman.UUCP)
"Wer fuer alles offen ist, kann nicht ganz dicht sein." (unbekannt)
_____________________________________________________________________________