[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GMAKE 3.81 vs GMAKE 4.2
From: |
nikhil jain |
Subject: |
Re: GMAKE 3.81 vs GMAKE 4.2 |
Date: |
Sun, 22 May 2022 20:16:23 +0530 |
When I say memory , I mean when make starts then in the main function I
have the getpid to give me the parent pid which I save in the env and that
is available to all the child processes so that I can find out when the
parent make has come into child handler by checking getpid == make pid from
env and do some stuff based on it.
On Sun, 22 May 2022 at 6:52 PM, Paul Smith <psmith@gnu.org> wrote:
> On Sun, 2022-05-22 at 10:53 +0530, nikhil jain wrote:
> > 1) write some content in a file only if the forked process ID is same
> > as the main make process ID (stored main process ID in the memory as
> > make starts so that it will be available to all the forked process).
>
> I don't understand this. Yes, make will fork a new process but then it
> immediately does an exec, including when invoking a sub-make, so no
> memory is shared between make processes.
>
- RE: GMAKE 3.81 vs GMAKE 4.2, (continued)
- Re: GMAKE 3.81 vs GMAKE 4.2, Kaz Kylheku, 2022/05/05
- Re: GMAKE 3.81 vs GMAKE 4.2, nikhil jain, 2022/05/05
- Re: GMAKE 3.81 vs GMAKE 4.2, nikhil jain, 2022/05/20
- Re: GMAKE 3.81 vs GMAKE 4.2, Paul Smith, 2022/05/21
- Re: GMAKE 3.81 vs GMAKE 4.2, nikhil jain, 2022/05/21
- Re: GMAKE 3.81 vs GMAKE 4.2, nikhil jain, 2022/05/22
- Re: GMAKE 3.81 vs GMAKE 4.2, Paul Smith, 2022/05/22
- Re: GMAKE 3.81 vs GMAKE 4.2,
nikhil jain <=