49

I am trying to compile a Pro*C file on gcc and I am getting this error :

make: *** [MedLib_x.o] Error 1

This is the command printed by make:

   /usr/bin/gcc -g -fPIC -m64 -DSS_64BIT_SERVER  -I/home/med/src/common -
I/u01/app/oradb11r2/product/11.2.0/dbhome_3/rdbms/demo 
-I/u01/app/oradb11r2/product/11.2.0/dbhome_3/rdbms/public 
-I/u01/app/oradb11r2/product/11.2.0/dbhome_3/precomp/public 
-I/u01/app/oradb11r2/product/11.2.0/dbhome_3/xdk/include INCLUDE=/u01/app/oradb11r2/product/11.2.0/dbhome_3/precomp/public -lnapi -ltabs -c MedLib_x.c

Please help me why this make error is coming? Although object file is also created.

QMG
  • 719
  • 2
  • 7
  • 16

4 Answers4

28

From GNU Make error appendix, as you see this is not a Make error but an error coming from gcc.

‘[foo] Error NN’ ‘[foo] signal description’ These errors are not really make errors at all. They mean that a program that make invoked as part of a recipe returned a non-0 error code (‘Error NN’), which make interprets as failure, or it exited in some other abnormal fashion (with a signal of some type). See Errors in Recipes. If no *** is attached to the message, then the subprocess failed but the rule in the makefile was prefixed with the - special character, so make ignored the error.

So in order to attack the problem, the error message from gcc is required. Paste the command in the Makefile directly to the command line and see what gcc says. For more details on Make errors click here.

fnokke
  • 1,121
  • 8
  • 18
  • Thank you for your reply. I am unable to link down the error and things written on page regarding Make errors. – QMG Apr 04 '11 at 08:55
  • My problem was make was trying to run a cmd I didn't have (`numactl` [in my particular case](https://github.com/f18m/malloc-benchmarks)). So, I ran `sudo apt install numactl`, and now the `make` cmd works fine! – Gabriel Staples Jun 26 '21 at 23:56
22

I got the same thing. Running "make" and it fails with just this message.

% make
make: *** [all] Error 1

This was caused by a command in a rule terminates with non-zero exit status. E.g. imagine the following (stupid) Makefile:

all:
       @false
       echo "hello"

This would fail (without printing "hello") with the above message since false terminates with exit status 1.

In my case, I was trying to be clever and make a backup of a file before processing it (so that I could compare the newly generated file with my previous one). I did this by having a in my Make rule that looked like this:

@[ -e $@ ] && mv $@ $@.bak

...not realizing that if the target file does not exist, then the above construction will exit (without running the mv command) with exit status 1, and thus any subsequent commands in that rule failed to run. Rewriting my faulty line to:

@if [ -e $@ ]; then mv $@ $@.bak; fi

Solved my problem.

zrajm
  • 1,361
  • 1
  • 12
  • 21
  • Another option would be `@[ ! -e $@] || mv $@ $@.bak` – T0xicCode Feb 09 '14 at 04:40
  • 1
    Absolutely! `@[ ! -e $@] || mv $@ $@.bak` would also work! But it hurts my brain just to try to read beyond the double negations, so out of consideration for my fellow programmers (i.e. most likely myself, a year into the future) I prefer to use the slightly longer `if` statement instead. – zrajm Apr 19 '15 at 16:31
3

Sometimes you will get lots of compiler outputs with many warnings and no line of output that says "error: you did something wrong here" but there was still an error. An example of this is a missing header file - the compiler says something like "no such file" but not "error: no such file", then it exits with non-zero exit code some time later (perhaps after many more warnings). Make will bomb out with an error message in these cases!

John Lupien
  • 31
  • 1
0

In my case there was a static variable which was not initialized. When I initialized it, the error was removed. I don't know the logic behind it but worked for me. I know its a little late but other people with similar problem might get some help.

Waqas Ahmed
  • 88
  • 1
  • 1
  • 5