Re: Baffled by cc -o in Make manual

2017-08-01 Thread Sven C. Dack
Hello, this is completely normal. The compiler calls the assembler and linker automatically when needed and depending on the input files. One doesn't actually call the assembler and linker manually in most cases. You can do: cc -c prog.c -o prog.o This will compile the file 'prog.c' int

Re: Baffled by cc -o in Make manual

2017-08-01 Thread Mike Gran
On Tuesday, August 1, 2017, 10:31:15 AM PDT, Ray Foulkes wrote: > I am totally baffled as to what cc -o is doing there. Surely it should be > ld??> and then the -o is for "output" i.e. create "edit" as an executable. The above command is correct.  On the GNU Linux and BSD systems, usuallyone ha

Re: Baffled by cc -o in Make manual

2017-08-01 Thread Paul Smith
On Tue, 2017-08-01 at 18:32 +0200, Ray Foulkes wrote: > I am totally baffled as to what cc -o is doing there. Surely it > should be ld?? and then the -o is for "output" i.e. create "edit" as > an executable. It's generally not recommended that you ever run the linker directly unless you have speci

Baffled by cc -o in Make manual

2017-08-01 Thread Ray Foulkes
Hello, like many reports I suppose I have this totally wrong but the very first example on page 4 of the make manual at https://www.gnu.org/software/make/manual/make.pdf  reads: edit : main.o kbd.o command.o display.o \     insert.o search.o files.