[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GNU make 3.81beta4 released

From: Eli Zaretskii
Subject: Re: GNU make 3.81beta4 released
Date: Fri, 20 Jan 2006 22:01:33 +0200

> Date: Fri, 20 Jan 2006 14:36:15 -0500
> Cc: address@hidden, address@hidden
> From: "Paul D. Smith" <address@hidden>
> %% Eli Zaretskii <address@hidden> writes:
>   ez> It doesn't die; vfork returns -1 with errno set to EAGAIN, and the
>   ez> rule's commands are not run.
> But, is the rule marked as failed?
> If not, that's obviously a bug.  If so, that might be good enough for
> this unusual case.

Here's the transcript (you can try it yourself, it's a makefile from
parallelism test):

    address@hidden:~$ cat mkf4
    recurse: ; @$(MAKE) --no-print-directory -f mkf4 INC=yes all
    all: 0 1 2; @echo success

    0: ; @echo $(MAKEFLAGS)

    INC = no
    ifeq ($(INC),yes)
    endif ; @echo; sleep 2; echo; echo '1: ; @echo ONE; sleep 
2; echo TWO' > $@ ; @sleep 1; echo; echo '2: ; @sleep 1; echo THREE' > $@
    address@hidden:~$ ulimit -S 7
    address@hidden:~$ make -j -f mkf4
    --no-print-directory -j -- INC=yes
    address@hidden:~$ ulimit -S -u 9
    address@hidden:~$ make -j -f mkf4
    make[1]: vfork: Resource temporarily unavailable
    --no-print-directory -j -- INC=yes

As you see, after limiting the number of jobs, the commands for
are not run because vfork fails, but Make doesn't say anything about
failing to remake the target.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]