Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: How to find the problem in the object file Date: Thu, 26 Jan 2017 08:52:42 -0800 Organization: None to speak of Lines: 24 Message-ID: References: <23ab01a2-5220-42cb-80b2-20a2b4a35d5c@googlegroups.com> <2beebc58-3f8f-46c6-bd10-e2ec3cf87906@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: mx02.eternal-september.org; posting-host="c4bbf5deaa7fb5ee9d54a2c91785016f"; logging-data="29903"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+P+EVMvqk9RTPnfCMGTTCy" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:r9WuY7C2nC/E1Femq37T2rc1Jbc= sha1:URL552byCcsqOpAxXEDEPpYNV9k= Xref: csiph.com comp.lang.c:102473 Alla _ writes: > On Thursday, January 26, 2017 at 5:51:41 PM UTC+3, David Brown wrote: [...] >> It looks like you are using clang as your compiler. [snip] > > Not me - Apple has changed gcc for clang. But I still use gcc command, > clang knows how to interpret that. Yes, you *are* using clang -- because Apple has made it inconvient not to. You're typing the command "gcc", and it's invoking the Clang compiler. (It's set up by the OS as a symlink or something similar.) gcc and clang pretty much work alike, so it shouldn't be an issue. (Apple set up the misleading name "gcc" to allow for scripts and Makefile that assume the C compiler is named "gcc".) [...] -- Keith Thompson (The_Other_Keith) kst-u@mib.org Working, but not speaking, for JetHead Development, Inc. "We must do something. This is something. Therefore, we must do this." -- Antony Jay and Jonathan Lynn, "Yes Minister"