levitte@garbo.bion.kth.se (Tommy Levitte) (05/26/90)
I have found a somewhat annoying bug (i think). Facts: - In MAKE.INI, I have the line .RESPONSE_LINK : tlink - In I:, I have all my BORLAND stuff, and all my NDMAKE stuff. I: is a write protected network disk (I am running PCSA). - I have a SUBST T: I:\ for technical reasons. - In my makefile, I have TLINK /x /d /c /v /l T:\BORLAND\LIB\C0L scrmgr ord10,ord10,,T:\BORLAND\LIB\EMU T:\BORLAND\LIB\MATHL T:\BORLAND\LIB\CL T:\BORLAND\LIB\GRAPHICS ..\UTILS\UTILS Now, MAKE first generates a file MK###### (###### is a random number) which contains: /x /d /c /v /l T:\BORLAND\LIB\C0L scrmgr ord10 ord10 T:\BORLAND\LIB\EMU T:\BORLAND\LIB\MATHL + T:\BORLAND\LIB\CL T:\BORLAND\LIB\GRAPHICS + ..\UTILS\UTILS Then NDMAKE does: TLINK @MK###### This should work OK, you say. Yes, absolutelly! And it does! The problem is, when control comes back to NDMAKE, it tries to write something on I: !!! This gives me the error message: Write protect error writing drive I Abort, Retry, Fail ? Now, how do I know NDMAKE is the problem? Well, I reproduced the MK###### file and did TLINK @MK###### manually, and IT WORKED PERFECTLY !!!! Have anybody else encountered this problem??? What is it NDMAKE is doing??? How do I get around it??? Personally, I think NDMAKE has no need or reason to do this! !+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++! ! Tommy Levitte, System manager ! tel: int+46-8-790 64 23 ! ! Royal Institute of Technology ! Internet: gizmo@ttt.kth.se ! ! Department of Teletransmition Theory ! ! ! S-100 44 Stockholm, Sweden ! ! !---------------------------------------------------------------------------! -- !+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++! ! Tommy Levitte ! tel: int+46-8-790 64 23 ! ! Box 700 32 ! Internet: levitte@bion.kth.se ! ! S-100 44 Stockholm, Sweden ! gizmo@ttt.kth.se ! !---------------------------------------------------------------------------!