cvs.gedasymbols.org/archives/browse.cgi | search |
From: | "Tony O'Bryan" <aho450s AT nic DOT smsu DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: Compiling .C files |
Date: | Mon, 29 Dec 1997 13:44:58 -0600 |
Organization: | Southwest Missouri State University |
Lines: | 10 |
Message-ID: | <34A7FDBA.3E83@nic.smsu.edu> |
References: | <MPG DOT f119de9997d7343989681 AT news> |
Reply-To: | aho450s AT nic DOT smsu DOT edu |
NNTP-Posting-Host: | marie.a02.smsu.edu |
Mime-Version: | 1.0 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Matt Riker wrote: > > Usually when I compile .C files, DJGPP makes an executable. But today I > tried to compile, and DJGPP only made an .O file. Does anyone know why? You probably used the -c switch. If this .o file was part of a larger project build, then a source file probably contained an error which caused the build to stop after the file was compiled to an object file (which is what the .o extension means), thereby preventing gcc from putting all the .o files together to form the executable.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |