haapanen@watdcsu.UUCP (Tom Haapanen [DCS]) (01/02/85)
I have the DeSmet C Compiler, version 2.4, and I have found that using the -l option in bind causes problems. Specifically, assume all my source and object code is on the a disk (sorry, no har disk :-( ), and my compiler, linker and library are on the b disk. Then, I will do: c88 foo -db bind foo -lb The c88 works fine, but using bind with the -lb option causes unradable files 90% of the time; when I try running foo, DOS gives me 'Data error reading drive A:'. I'm using a Hyperion (256K, 2 DSDD drives) with PC-DOS 2.10. My programs work fine if I move the library onto the A drive; alas, this uses up about 40K of disk space... Has anybody else had this problem? I'd like to report this to CWare, but I'm thinking that maybe it's just a fluke... Please reply by mail. Thanks! \tom haapanen watmath!watdcsu!haapanen
jrv@Mitre-Bedford (01/13/85)
[haapanen@watdcsu.uucp writes:] >I have the DeSmet C Compiler, version 2.4, and I have found that using >the -l option in bind causes problems. > >Specifically, assume all my source and object code is on the a disk >(sorry, no har disk :-( ), and my compiler, linker and library are on >the b disk. Then, I will do: > c88 foo -db > bind foo -lb >The c88 works fine, but using bind with the -lb option causes >unreadable files 90% of the time; That series of commands works fine with my compiler (version 2.3 on MS-DOS version 2.11 on a Z-100), but then again my program may be among your 10% that work. You might try setting your PATH, since both c88 and bind will search the PATH for files they need. You could try something like path=a:;a:\bin;b:;b:\bin which also worked for me. - Jim Van Zandt
jrv@Mitre-Bedford (01/14/85)
>...You could try something like > path=a:;a:\bin;b:;b:\bin >which also worked for me. - Jim Van Zandt but of course it works better with two more backslashes: path=a:\;a:\bin;b:\;b:\bin Sorry 'bout that. - Jim Van Zandt