From: "Andy Neebel" Newsgroups: comp.os.msdos.djgpp Subject: Re: compiling dgjpp for dos Date: Tue, 29 Apr 2003 21:13:48 -0500 Lines: 41 Message-ID: References: <3eaa5e7f$0$79348$cc7c7865 AT news DOT luth DOT se> NNTP-Posting-Host: 192.152.29.111 X-Trace: fu-berlin.de 1051668829 12514189 192.152.29.111 (16 [191991]) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com This is the end of this I guess. Sorry to have wasted your time, but I gave up with DJGPP and just put linux on the computer instead. Andy "Martin Str|mberg" wrote in message news:3eaa5e7f$0$79348$cc7c7865 AT news DOT luth DOT se... > Andy Neebel wrote: > : that error went away. My source came off of CVS, so I can't really get > : anything newer. What do you mean by an older compilier? To me it makes > > It sounds from you description that your gcc is using sections not > defined in the linker script. Older gcc's didn't. Hence it might help > to use an older one. > > If you use the latest in CVS that shouldn't happen. > > If you have extracted some older version, you might have a problem. > > 1. Have you upgraded your DJGPP installation without removing the old > packages? If so, remove the whole DJGPP tree and reinstall. > > 2. Does "make clean" before make help? > > 3. Post the command line that fails (the link command line, not > "make") and the linker script. > > : sense to use the newer one because it is more likely to support everything. > > And you get more bugs. At least different ones. > > > Right, > > MartinS