Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.c > #60737

Re: Fist steps in compiling, gcc commands confusion

From James Kuyper <jameskuyper@verizon.net>
Newsgroups comp.lang.c
Subject Re: Fist steps in compiling, gcc commands confusion
Date 2015-04-22 11:15 -0400
Organization Self
Message-ID <5537BB13.4000909@verizon.net> (permalink)
References <9f1b89ff-cf47-4e01-b137-ba263e9e75f1@googlegroups.com> <be2ee571-ec9b-494e-abf9-93f6f2e94e9e@googlegroups.com> <mh5s03$dgg$1@speranza.aioe.org> <mh7iu8$mcg$1@dont-email.me>

Show all headers | View raw


On 04/22/2015 03:35 AM, David Brown wrote:
> On 21/04/15 17:56, Morris Dovey wrote:
>> On 4/21/15 10:25 AM, Alla _ wrote:
>>> Just to add: I don't understand why the option with renaming the file
>>> has worked while the option gcc sample.c has not.
>>
>> In a terminal window, you can use the 'man' utility to view manual
>> pages. I suggest reading the page for man itself by typing
>>
>> man man
>>
>> It's helpful to remember that you can exit from man by typing 'q' for quit.
>>
>> Having done that, try
>>
>> man gcc
>>
>> and should see the answer to your question - and much, much more.
>>
> 
> The "man" page for gcc has little useful information - the real


On this particular issue, "man gcc" gives:
>        -o file
>            Place output in file file.  This applies regardless to whatever
>            sort of output is being produced, whether it be an executable file,
>            an object file, an assembler file or preprocessed C code.
> 
>            If -o is not specified, the default is to put an executable file in
>            a.out, the object file for source.suffix in source.o, its assembler
>            file in source.s, a precompiled header file in source.suffix.gch,
>            and all preprocessed C source on standard output.



> reference manual is easily found online:
> 
> <https://gcc.gnu.org/onlinedocs/>

When I got to that source and retrieve the manual for the same version
of gcc (4.4.7), it says:

> -o file
> Place output in file file. This applies regardless to whatever sort
> of output is being produced, whether it be an executable file, an object
> file, an assembler file or preprocessed C code.
> 
> If -o is not specified, the default is to put an executable file in
> a.out, the object file for source.suffix in source.o, its assembler file
> in source.s, a precompiled header file in source.suffix.gch, and all
> preprocessed C source on standard output.


Those descriptions appear to be word-for-word identical, though I might
have missed something. On what basis are you claiming that "the 'man'
page for gcc has little useful information"?

Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Fist steps in compiling, gcc commands confusion Alla _ <modelling.data@gmail.com> - 2015-04-21 08:18 -0700
  Re: Fist steps in compiling, gcc commands confusion Alla _ <modelling.data@gmail.com> - 2015-04-21 08:25 -0700
    Re: Fist steps in compiling, gcc commands confusion Morris Dovey <mrdovey@iedu.com> - 2015-04-21 10:56 -0500
      Re: Fist steps in compiling, gcc commands confusion David Brown <david.brown@hesbynett.no> - 2015-04-22 09:35 +0200
        Re: Fist steps in compiling, gcc commands confusion James Kuyper <jameskuyper@verizon.net> - 2015-04-22 11:15 -0400
          Re: Fist steps in compiling, gcc commands confusion David Brown <david.brown@hesbynett.no> - 2015-04-23 01:31 +0200
        Re: Fist steps in compiling, gcc commands confusion Keith Thompson <kst-u@mib.org> - 2015-04-22 08:43 -0700
          Re: Fist steps in compiling, gcc commands confusion Bartc <bc@freeuk.com> - 2015-04-22 18:57 +0100
            Re: Fist steps in compiling, gcc commands confusion Keith Thompson <kst-u@mib.org> - 2015-04-22 11:35 -0700
  Re: Fist steps in compiling, gcc commands confusion James Kuyper <jameskuyper@verizon.net> - 2015-04-21 12:01 -0400
  Re: Fist steps in compiling, gcc commands confusion John Gordon <gordon@panix.com> - 2015-04-21 16:01 +0000
    Re: Fist steps in compiling, gcc commands confusion Tim Prince <tprince@computer.org> - 2015-04-21 13:11 -0400
    Re: Fist steps in compiling, gcc commands confusion Keith Thompson <kst-u@mib.org> - 2015-04-21 12:09 -0700
  Re: Fist steps in compiling, gcc commands confusion Bartc <bc@freeuk.com> - 2015-04-21 18:25 +0100
    Re: Fist steps in compiling, gcc commands confusion Keith Thompson <kst-u@mib.org> - 2015-04-21 12:11 -0700
  Re: Fist steps in compiling, gcc commands confusion Keith Thompson <kst-u@mib.org> - 2015-04-21 11:16 -0700

csiph-web