I received a WARN when was configuring GNU make,


 
Thread Tools Search this Thread
Top Forums UNIX for Advanced & Expert Users I received a WARN when was configuring GNU make,
Prev   Next
# 1  
Old 02-01-2018
I received a WARN when was configuring GNU make,

When I tried to configure GNU make, I received:
Code:
...
WARNING: Your system has neither waitpid() nor wait3().
Without one of these, signal handling is unreliable
You should be aware that running GNU make with -j
could result in erratic behavior.
...

What is that supposed to mean ? my spec:

MinGW and MSYS on Windows 10 (64 bit all)

shell has system mingw64 - environment variable MSYSTEM="MINGW64" - and path to its bin first, before msys/usr/bin, when work's being done

Any sincere useful help is really thanked and appreciated

Last edited by rbatte1; 02-01-2018 at 07:25 AM.. Reason: Wrapped output in CODE tags for clarity
 
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

GNU make doesn't pick up changes

It's been a while since I had to write a Makefile, but I've managed to clobber this together: SRC=module1.c module2.c OBJS=$(SRC:%.c=%.o) HDR=include1.h include2.h CC=gcc CFLAGS=-Wall -ggdb -D_XOPEN_SOURCE -I. -ansi all: program program: $(OBJS) $(CC) $(CFLAGS) -o $@ $(OBJS) ... (3 Replies)
Discussion started by: pludi
3 Replies

2. AIX

Not picking up the GNU version of make

Hi team, I am new to unix,and need your advice on the below. I am using aix5.3 and have installed make-3.82 on the server. I need to use gmake for configuring and installing a package ,but it is giving error at the below root@sapsrp:/usr/tmp/xymon-4.3.2 # ./configure.server ... (7 Replies)
Discussion started by: sonal kumar
7 Replies

3. UNIX for Advanced & Expert Users

Make giving error after configuring a package

Hi, I have installed gmake 3.82 in my aix 5.3 system. but while installing a package,after doing./configure ,i give gmake and its throwing below error. # gmake "build/Makefile.rules", line 13: make: 1254-055 Dependency line needs colon or double colon operator. also the command is not... (1 Reply)
Discussion started by: sonal kumar
1 Replies

4. AIX

gnu make fir AIX 5.3 and gcc 3.3.2

Hi all i had installed gcc version 3.3.2 on my AIX 5.3 machine. which make utility i have to instal so it will fit the gcc version tnx skfn (2 Replies)
Discussion started by: skfn1203
2 Replies

5. Programming

A question about Makefile run by GNU make

Hello everybody, Currently I'm learning how to build projects (C programming) with GNU make. I have a problem with one Makefile and I would appreciate if you could kindly give me a hand. Here is the environment: OS: Redhat linux 5 compiler: gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-44)... (2 Replies)
Discussion started by: dariyoosh
2 Replies

6. SCO

GNU cpp and make on SCO

Installed GNU make and the GNU C/C++ compiler on SCO Openserver 5.0.7 recently. Only a normal user is able to run make and compile programs - root is not able to. Under root, make do run, but root can't access the compiler at all, even tho I set root's path to point to the compiler.... (0 Replies)
Discussion started by: The_Librarian
0 Replies

7. Programming

Detecting host OS in Gnu make

Is this possible? Right now I'm developing some code for Linux, Windows and OS X. To build on each of the systems I've currently got separate build targets for each platform. Ideally I'd like to set up a single make rule that can detect the appropriate target and build it. I know this is... (2 Replies)
Discussion started by: G_Morgan
2 Replies

8. UNIX for Dummies Questions & Answers

What's the difference between PMake and GNU Make?

My system is ubuntu, can I use PMake ? (0 Replies)
Discussion started by: meili100
0 Replies

9. UNIX for Advanced & Expert Users

GNU's make error codes - list

Hi, I often encounter make errors. Many a times, a corresponding error code is also shown, like make: Error 56 (ignored) make: Error 91 (ignored) make: Error 96 (ignored) et al. I tried google'ing as well as searching this forum for what these error codes mean. I know, make... (1 Reply)
Discussion started by: vino
1 Replies

10. UNIX for Advanced & Expert Users

Problems with gnu make

I am running a make file through the gnu make tool and i am getting the following error jsh1035c:/users/egate453/admegate/kapil/samples $ make -f GNUmakefile queue_c make -f ./GNUmakefile queue_c in_objdir=1 build_root=/users/egate453/admegate/kapil/samples make: Entering directory... (2 Replies)
Discussion started by: handak9
2 Replies
Login or Register to Ask a Question
WAIT(2) 						      BSD System Calls Manual							   WAIT(2)

NAME
wait, wait3, wait4, waitpid -- wait for process termination SYNOPSIS
#include <sys/wait.h> pid_t wait(int *stat_loc); pid_t wait3(int *stat_loc, int options, struct rusage *rusage); pid_t wait4(pid_t pid, int *stat_loc, int options, struct rusage *rusage); pid_t waitpid(pid_t pid, int *stat_loc, int options); DESCRIPTION
The wait() function suspends execution of its calling process until stat_loc information is available for a terminated child process, or a signal is received. On return from a successful wait() call, the stat_loc area contains termination information about the process that exited as defined below. The wait4() call provides a more general interface for programs that need to wait for certain child processes, that need resource utilization statistics accumulated by child processes, or that require options. The other wait functions are implemented using wait4(). The pid parameter specifies the set of child processes for which to wait. If pid is -1, the call waits for any child process. If pid is 0, the call waits for any child process in the process group of the caller. If pid is greater than zero, the call waits for the process with process id pid. If pid is less than -1, the call waits for any process whose process group id equals the absolute value of pid. The stat_loc parameter is defined below. The options parameter contains the bitwise OR of any of the following options. The WNOHANG option is used to indicate that the call should not block if there are no processes that wish to report status. If the WUNTRACED option is set, children of the current process that are stopped due to a SIGTTIN, SIGTTOU, SIGTSTP, or SIGSTOP signal also have their status reported. If rusage is non-zero, a summary of the resources used by the terminated process and all its children is returned (this information is cur- rently not available for stopped processes). When the WNOHANG option is specified and no processes wish to report status, wait4() returns a process id of 0. The waitpid() call is identical to wait4() with an rusage value of zero. The older wait3() call is the same as wait4() with a pid value of -1. The following macros may be used to test the manner of exit of the process. One of the first three macros will evaluate to a non-zero (true) value: WIFEXITED(status) True if the process terminated normally by a call to _exit(2) or exit(3). WIFSIGNALED(status) True if the process terminated due to receipt of a signal. WIFSTOPPED(status) True if the process has not terminated, but has stopped and can be restarted. This macro can be true only if the wait call specified the WUNTRACED option or if the child process is being traced (see ptrace(2)). Depending on the values of those macros, the following macros produce the remaining status information about the child process: WEXITSTATUS(status) If WIFEXITED(status) is true, evaluates to the low-order 8 bits of the argument passed to _exit(2) or exit(3) by the child. WTERMSIG(status) If WIFSIGNALED(status) is true, evaluates to the number of the signal that caused the termination of the process. WCOREDUMP(status) If WIFSIGNALED(status) is true, evaluates as true if the termination of the process was accompanied by the creation of a core file containing an image of the process when the signal was received. WSTOPSIG(status) If WIFSTOPPED(status) is true, evaluates to the number of the signal that caused the process to stop. NOTES
See sigaction(2) for a list of termination signals. A status of 0 indicates normal termination. If a parent process terminates without waiting for all of its child processes to terminate, the remaining child processes are assigned the parent process 1 ID (the init process ID). If a signal is caught while any of the wait() calls is pending, the call may be interrupted or restarted when the signal-catching routine returns, depending on the options in effect for the signal; see intro(2), System call restart. RETURN VALUES
If wait() returns due to a stopped or terminated child process, the process ID of the child is returned to the calling process. Otherwise, a value of -1 is returned and errno is set to indicate the error. If wait3(), wait4(), or waitpid() returns due to a stopped or terminated child process, the process ID of the child is returned to the call- ing process. If there are no children not previously awaited, -1 is returned with errno set to [ECHILD]. Otherwise, if WNOHANG is specified and there are no stopped or exited children, 0 is returned. If an error is detected or a caught signal aborts the call, a value of -1 is returned and errno is set to indicate the error. ERRORS
The wait() system call will fail and return immediately if: [ECHILD] The calling process has no existing unwaited-for child processes. [EFAULT] The status or rusage argument points to an illegal address (may not be detected before the exit of a child process). [EINVAL] Invalid or undefined flags are passed in the options argument. The wait3() and waitpid() calls will fail and return immediately if: [ECHILD] The process specified by pid does not exist or is not a child of the calling process, or the process group specified by pid does not exist or does not have any member process that is a child of the calling process. The waitpid() call will fail and return immediately if: [EINVAL] The options argument is not valid. Any of these calls will fail and return immediately if: [EINTR] The call is interrupted by a caught signal or the signal does not have the SA_RESTART flag set. STANDARDS
The wait() and waitpid() functions are defined by POSIX; wait3() and wait4() are not specified by POSIX. The WCOREDUMP() macro and the abil- ity to restart a pending wait() call are extensions to the POSIX interface. LEGACY SYNOPSIS
#include <sys/types.h> #include <sys/wait.h> The include file <sys/types.h> is necessary. SEE ALSO
sigaction(2), exit(3), compat(5) HISTORY
A wait() function call appeared in Version 6 AT&T UNIX. 4th Berkeley Distribution April 19, 1994 4th Berkeley Distribution