oleg@jvd.msk.su (Oleg Pavlyuchenko) (06/27/91)
Is it normal that BC++ linker make .EXE file more than 2 minutes for windows program on 80386 ( 33 MHz ) mashine? (oleg@jvd.msk.su) -- Oleg Pavlyuchenko (oleg@jvd.msk.su)
gary@neptune.uucp (Gary Bisaga x4219) (06/27/91)
In article <1991Jun26.174511.2449@jvd.msk.su> oleg@jvd.msk.su (Oleg Pavlyuchenko) writes: > Is it normal that BC++ linker make .EXE file more than 2 minutes > for windows program on 80386 ( 33 MHz ) mashine? I have the exact same problem but ONLY when compiling/linking under the integrated environment. When I link from the command line, it works fine. Details of the problem in my case (probably Oleg's as well): Compiling takes the amount of time you'd expect. Linking proceeds more or less normally, taking about 10 seconds to get through the source and most libraries (short program). Then, it sits linking LIBCS (I think the name is, pretty sure it's the standard library in any case) for about 3 minutes, 20 seconds (I have a 386/25). As I recall, it's not accessing disk for most of that time. I thought the machine had crashed the first time. Then, it finishes the library and completes in a few seconds. The same thing happens whether the linker is run under Windows or straight from DOS without Windows running. It's not that big of a deal for me, since I normally use the command line compilers anyway, but it is a curious problem ... Gary Bisaga (gary@ctc.contel.com, soon gbisaga@mitre.org)
hugh@slee01.srl.ford.com (Hugh Fader) (06/28/91)
oleg@jvd.msk.su (Oleg Pavlyuchenko) writes: > > Is it normal that BC++ linker make .EXE file more than 2 minutes > for windows program on 80386 ( 33 MHz ) mashine? The speed of the compiler increases dramatically under windows if you run windows in standard mode with win/s. Also, using bcx rather than bc makes a big difference. -- Hugh Fader hugh@slee01.srl.ford.com