GCC and makefile: Only show errors and warnings

Question

I have a makefile that compiles every .c file in my project. For each file, I get the whole compile command printed out to the shell, with all the options and flags. This is the example output for one file:

arm-none-eabi-gcc -c -mcpu=cortex-m3 -O0 -dM -g -gdwarf-2 -mthumb -fomit-frame-pointer -fverbose-asm -Wa,-ahlms=src/sim/sim_configuration.lst -include ./lib/stm32core/stm32f2xx_conf.h -I . -I./lib/ARMStandardLibrary -I./lib/LwIP -I./lib/LwIP/src/include -I./lib/LwIP/src/include -I./lib/LwIP/src/include/ipv4 -I./lib/LwIP/src/include/ipv6 -I./lib/FatFS -I./lib/stm32core -I./src -I./src/sim -I./src/sd -I./src/tftp src/sim/sim_configuration.c -o src/sim/sim_configuration.o

The problem is that various warnings get lost inside this whole mess of command outputs. Is there a way to only print the warnings and errors that appear (not the original command)?

jxh · Accepted Answer · 2012-08-14 16:18:03Z

24

Execute make with the -s option. From the man page.

-s, --silent, --quiet
    Silent operation; do not print the commands as they are executed.

answered Aug 14, 2012 at 16:18

jxh

70.9k8 gold badges116 silver badges204 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

mrucci · Accepted Answer · 2012-08-14 23:33:38Z

6

Just prepend the command with the @ symbol.

If you rely on built-in implicit rules, you will have to make them explicit or, in your specific case, you could use:

.SILENT: *.o

for silencing all commands used for building to the %.o targets.

edited Aug 14, 2012 at 23:33

answered Aug 14, 2012 at 16:15

mrucci

4,4703 gold badges37 silver badges38 bronze badges

4 Comments

Idelic Over a year ago

Instead of (or in addition to) using @, you can do MAKEFLAGS += --quiet. That will work for built-in rules as well.

mrucci Over a year ago

Yes, but then every command in every rule will not be echoed.

Idelic Over a year ago

As always, it's a trade off, but it handles built-in rules. In general, making built-in rules explicit is a very bad idea, so setting MAKEFLAGS may be a better method. Or not, of course.

mrucci Over a year ago

Maybe the .SILENT solution is better?

DaoWen · Accepted Answer · 2012-08-14 16:20:22Z

5

You could always filter all the output from stdout, which should leave you with all the errors on stderr:

make 1>/dev/null

answered Aug 14, 2012 at 16:20

DaoWen

33.1k6 gold badges77 silver badges102 bronze badges

Comments

perreal · Accepted Answer · 2012-08-14 16:16:12Z

4

Use @ before a command to hide the it:

rule1:
  @gcc someting

answered Aug 14, 2012 at 16:16

perreal

98.7k23 gold badges159 silver badges187 bronze badges

Collectives™ on Stack Overflow

GCC and makefile: Only show errors and warnings

4 Answers 4

Comments

4 Comments

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

Comments

4 Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related