Hello. I just want to ask atip from the experts and experienced linux users.
When we compiling a package on linux, if there is an error occured during the ./configure or make process of the software that we intended to install, what are the parts that we should check from the details that we get the error?
Is there any specific tips on how to handle such situation (having error while compiling a package)?
Thanks for any help on this.

Below are the example of error occured and what should I look for first to make a solution.

In file included from ../locking.h:68,
from sender.c:43:
../lock_alloc.h: In function `lock_set_alloc':
../lock_alloc.h:68: warning: passing arg 3 of `_shm_malloc' discards qualifiers from pointer target type
sender.c:193:1: unterminated argument list invoking macro "LOG"
sender.c: In function `AAASendMessage':
sender.c:102: error: `LOG' undeclared (first use in this function)
sender.c:102: error: (Each undeclared identifier is reported only once
sender.c:102: error: for each function it appears in.)
sender.c:102: error: syntax error at end of input
sender.c:77: warning: unused variable `event'
sender.c:78: warning: unused variable `ret'
sender.c:85: error: label `error' used but not defined
../transport/../list.h:82: warning: 'list_add' defined but not used
../transport/../list.h:95: warning: 'list_add_tail' defined but not used
../transport/../list.h:119: warning: 'list_del' defined but not used
../transport/../list.h:128: warning: 'list_del_init' defined but not used
../transport/../list.h:145: warning: 'list_empty' defined but not used
../transport/../list.h:155: warning: 'list_splice' defined but not used
sender.c:56: warning: 'ses_trans_timeout_f' defined but not used
make[2]: *** [sender.lo] Error 1
make[2]: Leaving directory `/usr/local/disc-0.2.0/src/diameter_api'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/local/disc-0.2.0/src'
make: *** [all-recursive] Error 1

moving to programming

well, what i like to do is run make from with in vi. the vi command

:make

will run make, and jump to the errors in the file they occure. you can then edit the file if you can see what it is that is calling the problem, and run :make again to see if it is fixed.

emacs allows you to do this too i believe, but I'm not sure how.

as far as problems with ./configure, from my experience it just comes down to looking in the ./configure file, finding where the error occured, figure out what caused it,and then research why its a problem.

unfortunatly, this just comes from experience, and tinkering.