X-Authentication-Warning: mail.bio.uva.nl: Host biomacI-138.bio.uva.nl [145.18.167.138] claimed to be [145.18.167.138] Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 19 May 1999 11:02:32 +0200 To: djgpp AT delorie DOT com From: dlanor AT dds DOT nl (Ronald Landheer) Subject: Re: FPU emulation Reply-To: djgpp AT delorie DOT com >> gcc -g -mcpu=i386 -march=i386 -lemu -o xyplan.exe p:/djgpp/obj/xyplan.o >This is wrong. -lemu should come *last* in the link command line, >since the link order is important. See FAQ section 8.9. I've taken a look at it: it seems that when I put it in the linker options in RHIDE, it should work, because the -Xlinker option is also added. I can't change the order in which RHIDE adds the command-line options (at least: not that I know), and as I'm still using RHIDE for my C/C++ work, I'd guess putting it in the linker options would be the best way.. It's still strange, though, that I don't get those "unresolved externals" anymore. The program has finished it's test (one an FPU-less machine) and it did work (even though that it shouldn't in theory): it took very long (which was to be expected) but it didn't crash (which it does when I don't put in the -lemu option).. If you know of a way to change the order in which RHIDE puts in the command-line options, please tell me about it. I can only get it to put them between gcc -g and the object file, and can thus only change the sequence in which I put in the -mcpu=i386, the -march=i386 and the -lemu. Greetz! Dlanor If you think big brother is watching you, don't turn off cookies: turn off your computer!