Message-ID: <003a01be1d76$07ceeaa0$603ef482@banan> From: "Bengt AT Playboj DOT com" To: Subject: Re: gcc 2.8.1 + RSXNT Date: Tue, 1 Dec 1998 22:59:32 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Reply-To: djgpp AT delorie DOT com Thanks a lot, it works now... I have no idea why it worked with the earlier version of gcc though... I did use the same specs file... anyway it works now so I'm happy:) -----Original Message----- From: bowman To: djgpp AT delorie DOT com Date: den 1 december 1998 19:31 Subject: Re: gcc 2.8.1 + RSXNT > > >"Bengt AT Playboj DOT com" wrote: >> >> c:/djgpp/bin/ld.exe: cannot open -lc_app: No such file or directory (ENOENT) >> the specs code you typed, is that a fix for this? If so where in the specs >> file should I put it, (and what happends to the specs file in >> djggp\lib\gcc-lib\2.81? shall I replace it?, right now it uses the >> rsxnt\lib\specs file...? > >I didn't use the suggested fix, since I prefer to just use the single >thread >library, but the idea is the same. > >-------------------------- rsxnt\lib\specs >-------------------------------- >..... > >*link: >%{Zwin32: -Lc:/rsxntdj/lib/all -Lc:/rsxntdj/lib/st} > >..... > > >If you look at /rsxntdj/lib/ you'll see three subdirectories, /All, /Mt, >and /St. >The single thread (St) and multithread (Mt), contain several libraries, >including the libc_app.a the linker can't find. By adding the above line >to the specs file in the /rsxntdj/lib/, the linker will look in the >single threaded, /St, and use those libraries. The other fix would let >you select Mt or St with a command line option. > >For whatever reason, the specs file provided with rsxntdj will include >neither directory, and will fail on linking. > > >On the ld.exe question: I am using the ld.exe provided with binutils. It >seems to work fine. The ld.exe from rsxntdj will silently ignore >whatever it cannot find during linking, allowing the application to >crash the first time it tries to call the missing function. This is >extremely poor behavior, especially since the linker, as it is set up, >doesn't look too hard. libcomct.a, for instance, is not searched by >default.