From: "Johan Venter" Newsgroups: comp.os.msdos.djgpp References: <7tuuqf$dqs$1 AT nnrp1 DOT deja DOT com> <7u1gh6$a07$1 AT nnrp1 DOT deja DOT com> <7u28es$rar$1 AT nnrp1 DOT deja DOT com> Subject: Re: RSXNTDJ project building difficulties Lines: 25 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Message-ID: Date: Thu, 14 Oct 1999 13:30:12 +1000 NNTP-Posting-Host: 139.134.162.96 X-Trace: newsfeeds.bigpond.com 939899227 139.134.162.96 (Thu, 14 Oct 1999 21:07:07 EST) NNTP-Posting-Date: Thu, 14 Oct 1999 21:07:07 EST Organization: Telstra BigPond Internet Services (http://www.bigpond.com) To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com > So is there anyone here who has successfully configured---what is it? > the specs file?--on their system such that they can use the one 'ld' > from the standard distribution to get unresolved externals while using > the 'ld' that comes with RSXNTDJ to make the exe? I also use rhide to > build the 32-bit MSDOS programs for testing: is the C standard library > being referenced different from the one in /djgpp/lib, and if so, how > do I know I am not getting a buggy (earlier version) of a system call > than the one used if I weren't using RSXNTDJ?? You said you had read my RSXNTDJ HOWTO and that you are using RSXNTDJ 1.5. I'm inclined not to believe you as my HOWTO mentions nothing of a second copy of ld named ldrsx. There is no hassle with specs files and linker scripts with 1.5. RSXNTDJ 1.5 uses gccw32 to compile RSXNTDJ 1.5 programs, not gcc. One more thing, why is your cpp version so old? You shouldn't mix versions like that. -- Johan Venter ICQ 3643877 - jventer AT writeme DOT com The TPU DJGPP Interest Group - http://surf.to/djgppig The RSXNTDJ 1.5 HOWTO - http://surf.to/rsxntdj