🚀 go-pugleaf

>      Where can I find documentation on the format of archive libraries?
> (Other than the developer's kit, which I can't afford just yet :-)
> Marty

Even the developers kit doesn't document the format of ar68 files.

I would very much like to get this information myself.  Since ar68 doesn't
work (half the time it gives: error reading file ... messages, always gives
this for any file with file static objects) I am hoping to right my own.

Some other questions:

Is there any way to give the kit's linker a file list longer than 128 chars.
I tried the [com[tail.lnk]] option but it seems to truncate that to 128 chars
also.  ar68 heaved it's guts on almost every module for this project.
Has anyone figured out what ar68 is doing wrong?

This was my solution:

link68 [u] h.68k=gs,a,b,c,d,e,f,g,h,i,j,k,l,m,n,o,p,q,r,s,t,u,v,w,x,y,z,0,1,2,3,4,5,6,7,8,9,gl,lf

where a-z and 0-9 are files renamed to a.o b.o etc.
and gs is gemstart.o renamed and gl is gemlib renamed and lf is libf renamed

Does anyone know how to pass an environment to a program?  Without the
aes/vdi kludge package if possible.

Note: I was promised an update for my developers kit around april.  I still have
not seen hide nor hair of it? Listening Neil@ ?
--j.a.tainter