steve@thelake (Steve Yelvington) (09/01/89)
ddavis@APG-EMH5.APG.ARMY.MIL (Dave Davis, HSHB-MLOP) writes... > > I have what is probably a rather simple question; how do you > link the vdifast.a and aesfast.a libraries to a program? I've tried: > cc -vf <program.c> vdifast.a aesfast.a > and > lnk <program.o> vdifast.a aesfast.a > with no success. I've gotten various results, from three bombs to a > message "pdstart.o" missing (I do not have the 'pdstart.o' file > available). > Any suggestion? I've also had trouble trying to link in the > floating point library as well. Thanks! I find this rather puzzling, especially the line about "lnk," because the Sozobon linker isn't named lnk at all, nor should there be a pdstart.o. Assuming you have the genuine Sozobon cc driver program, as well as hcc.ttp, top.ttp, jas.ttp and ld.ttp, all you need to do is put the GEM libraries in the library directory and include them on the command line, as in: cc -o myprog.prg myprog.c aesfast.a vdifast.a The library directory should be designated in the environment. Mine says: PATH=.,\bin,c:\bin INCLUDE=c:\sozobon\include LIB=c:\sozobon\lib In c:\sozobon\lib\ I have: 1030 DSTART.O /* dLibs standard startup module */ 250 DASTART.O /* my desk accessory startup module */ 21670 LIBM.A /* David Brooks' replacement math library */ 12112 AESFAST.A /* Ian Lepore's AES library */ 9508 VDIFAST.A /* Ian Lepore's VDI library */ 68980 DLIBS.A /* Dale Schumacher's dLibs main library */ (your file sizes may vary due to slightly altered versions) To link in the floating point library, just include -f on the command line as per your example. If your setup matches this and you get bombs, I would suspect that either your shell program is doing something ugly or you have a corrupted copy of CC. If that happens, send me e-mail and I'll arrange to get you a copy that I know is OK. Steve Yelvington, up at the lake in Minnesota ... pwcs.StPaul.GOV!stag!thelake!steve (Usenet) ... {playgrnd,moundst,class68}!thelake!steve (Citadel)