X-Apparently-From: Message-ID: <001601bf36ed$f74e0de0$30f838ca@home-computer> From: "Prashant TR" To: "DJGPP Mailing list" Subject: Re: Running Borland compiler from GNU Make Date: Thu, 25 Nov 1999 08:05:18 +0530 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Reply-To: djgpp AT delorie DOT com >They both use their own DOS-extender which are not mixing well. >OTOH, Borland's rtm.exe is locking hardware interrupt handlers in a >non-standard way. Same problem applies to Pharlap tools and >Borland extended tools. Is this really true??? >"Stephen Roderick" wrote in message >news:383C2C21 DOT 4586642A AT ssl DOT umd DOT edu... >> Using gnu make to run bcc.exe (Borland's 16-bit compiler) under >> DOS (Winddoze 95 DOS) provides a nice descriptive error of >> >> "Loader error (0025): cannot initialize" >>8 >> And before you ask, yes I'd love to use GCC but that just isn't an >> acceptable option here. Sigh ... Yes. I had this problem too. For some of my programs, I require both 16-bit and 32-bit code and I also need to run bcc. But fighting this isn't really as hard as you thought. And I doubt if this has anything to do with hardware interrupt handlersl. If you have 32rtm (I'm using BC 5), run this before you run the GNU Make. The culprit here seems to be CWSDPMI. With 32rtm, everything works fine. Prashant __________________________________________________ Do You Yahoo!? Thousands of Stores. Millions of Products. All in one place. Yahoo! Shopping: http://shopping.yahoo.com