Path: utzoo!utgpu!water!watmath!clyde!att!mtunx!rutgers!gatech!bloom-beacon!tut.cis.ohio-state.edu!mailrus!ames!oliveb!pyramid!infmx!greggy From: greggy@infmx.UUCP (greg yachuk) Newsgroups: comp.lang.c Subject: Re: C Compiler bugs Summary: How does a compiler know what something WILL BE linked with? Message-ID: <230@infmx.UUCP> Date: 8 Jun 88 18:28:51 GMT References: <15085@tut.cis.ohio-state.edu> <4421@haddock.ISC.COM> <15275@tut.cis.ohio-state.edu> Organization: Informix Software Inc., Menlo Park, CA. Lines: 21 In article <15275@tut.cis.ohio-state.edu>, lvc@tut.cis.ohio-state.edu (Lawrence V. Cipriani) writes: > In article <8030@brl-smoke.ARPA> gwyn@brl.arpa (Doug Gwyn (VLD/VMB)) writes: [general discussion about main returning something other than an int, whether it should be considered an "error" by the compiler...] > >I seem to recall you said that this so-called bug had been "fixed". > >Was it fixed by building in knowledge that main() returns an int > >(in which case how do you disable that "knowledge" for compiling > >freestanding applications?), > I think it was done this way, and the way it is disabled for free- > standing applications is to not use the supplied /lib/*crt0.o files. How can you disable a part of the compiler by determining which /lib/*crt0.o file will be used when the whole muck is finally linked together? Do you have a code emitting linker, or am I missing something very basic? Greg Yachuk Informix Software Inc., Menlo Park, CA (415) 322-4100 {uunet,pyramid}!infmx!greggy !yes, I chose that login myself, wazit tooya? And they offered us a roof above our heads And like fools we beleive every last word they said. -- The Christians