server then provides the info to the user about how much % of make job
is done.
Please let me know. This is really an urgent requirement for me. Let me
know about the functions or variables where I can find like how many
targets have to executed.
Thanks a lot,
Nikhil Jain
ou so much.
On Fri, May 31, 2019 at 10:45 PM Paul Smith wrote:
> I'm adding back the mailing list. Please always keep it on the CC list
> at least (or just reply to the list directly: I am subscribed).
>
> On Fri, 2019-05-31 at 21:16 +0530, nikhil jain wrote:
> > Y
Hi again,
Does GMAKE has a retry option. If a command in a rule is failed, is there
an option to retry it or I have to implement it ?
Waiting for response.
Thanks
Nikhil
On Fri, May 31, 2019 at 10:59 PM nikhil jain wrote:
> OK, Thanks for your valuable suggestion.
> Also, will you co
Ok, thanks.
On Sat, 31 Aug 2019, 19:44 Paul Smith, wrote:
> On Fri, 2019-08-30 at 16:37 +0530, nikhil jain wrote:
> > Does GMAKE has a retry option. If a command in a rule is failed, is
> > there an option to retry it or I have to implement it ?
>
> GNU make has no built
ow if you guys thing to
make it part of some future releases.
Thanks
Nikhil Jain
On Mon, Sep 2, 2019 at 10:01 AM Kaz Kylheku (gmake) <
729-670-0...@kylheku.com> wrote:
> Hi nihkil,
>
> Try using a "macro":
>
> # $(1) is retry count: integer constant in shell test
same host if the build fails, then what to do ? ?? Run the
build from scratch ? That is a waste of time and resource.
On Mon, Sep 2, 2019 at 11:53 AM Kaz Kylheku (gmake) <
729-670-0...@kylheku.com> wrote:
> On 2019-09-01 23:04, nikhil jain wrote:
> > Hi,
> >
> > Thanks fo
Something sounds interesting from your message.
What is this .ONESHELL ?
If I have -
All:
mkdir dir
cd dir
So currently in my remote execution design these 2 commands execute on
different host.
So, does ONESHELL will make these 2 commands on the same host ?
Please reply as soon as y
Remote exec design is quite easy. I just filled in remote-stub.c with
enough code to execute the commands remotely and getting the status back.
On Mon, 2 Sep 2019, 21:06 Paul Smith, wrote:
> On Mon, 2019-09-02 at 20:48 +0530, nikhil jain wrote:
> > So currently in my remote executi
Thanks for detailed information.
I will see if I can use shell wrapper program as mentioned by you.
I had used LSF a lot like for 5 years. I still use it. bsub, bjobs. bkill,
lim, sbatchd, mbatchd etc. it is easy to understand and use
lsmake - I do not want to use IBM's proprietary stuff.
Than
haha OK.
If I were you, I would have built lsmake functionality in GMAKE and not pay
IBM lol.
Anyways, have a good day. :)
On Mon, Sep 2, 2019 at 11:45 PM David Boyce wrote:
> I did not suggest using lsmake, I simply mentioned that we use it.
>
> On Mon, Sep 2, 2019 at 11:04 AM ni
that we use it.
>>
>> On Mon, Sep 2, 2019 at 11:04 AM nikhil jain
>> wrote:
>>
>>> Thanks for detailed information.
>>>
>>> I will see if I can use shell wrapper program as mentioned by you.
>>>
>>> I had used LSF a lot like for
-09-18 at 08:20 +0530, nikhil jain wrote:
> > Can you please let me know when I do a SIGINT to the running make or
> > do a ctrl+c, which function is called at the last ? I want to add
> > some logic in there.
>
> Please start a new thread for a different question. Also, for
Hi,
I am seeing very different behaviors in my build between make version 3.81
and 4.2
My build compiles correctly but fails with segmentation fault on 4.2
version.
My build compiles correctly and executes also correctly on 3.81 version.
The build failed with error message related to THREADS.
I
?
Thanks
Nikhil
Need help.
On Sat, 28 Sep 2019, 03:58 Kaz Kylheku (gmake), <729-670-0...@kylheku.com>
wrote:
> On 2019-09-27 13:23, nikhil jain wrote:
> > Please reply. It is urgent for me to provide a Correct compiled product
> > to
> > my users.
> > I do not want to sw
Thanks
Nikhil
On Sun, Sep 29, 2019 at 6:20 AM Tony Theodore wrote:
>
>
> > On 28 Sep 2019, at 16:21, nikhil jain wrote:
> >
> > Do you mean to not use -j ?
> >
> > That means a single rule execution at a time. It takes 2 hours to build.
> > With -j4 it takes
n, 2019-09-30 at 13:51 +0530, nikhil jain wrote:
> > There are 2 parts to this problem -
> >
> > 1) Build the code using v3.81 and v4.2 -> In both cases, builds is
> > happening correctly.
> > 2) Segmentation fault -> While running the binary generated from the
&g
Also we prefer inline responses
> rather than top-quoting.
>
> On Mon, 2019-09-30 at 19:48 +0530, nikhil jain wrote:
> > For example, maybe you're using $(wildcard ...) to gather filenames
> > and the difference in the order returned is causing your code to be
> >
:
> Hello Nikhil,
>
> On Sat, Sep 28, 2019 at 1:54 AM nikhil jain
> wrote:
>
>> I am seeing very different behaviors in my build between make version 3.81
>> and 4.2
>>
>> My build compiles correctly but fails with segmentation fault on 4.2
>> version.
>
running. Is there some change after 3.81 with respect to the commands/rules
being displayed while running the Makefile ?
Please respond.
Thanks
Nikhil
On Tue, Oct 1, 2019 at 10:09 AM nikhil jain wrote:
> Hi,
>
> Thanks for the answers.
>
> You know what!
>
> It worked wit
go back to 3.81 and implement the remote execution again.
Help.
Thanks
Nikhil
On Fri, 4 Oct 2019, 02:59 Paul Smith, wrote:
> On Tue, 2019-10-01 at 10:09 +0530, nikhil jain wrote:
> > It is the test version sent to me in the mail thread by a GMAKE
> > expert. I would probably
sion testing on the binaries
generated by the build.
If I share a makefile then can you debug that ?
On Sat, 5 Oct 2019, 19:35 Paul Smith, wrote:
> On Fri, 2019-10-04 at 07:36 +0530, nikhil jain wrote:
> > So it looks like the wild card issue as you mention.
>
> If that is indeed
for
your help. I will keep you posted for any issues I come across.
thanks
Nikhil
On Sat, Oct 5, 2019 at 8:09 PM Paul Smith wrote:
> On Sat, 2019-10-05 at 19:55 +0530, nikhil jain wrote:
> > Can you tell when the make 4.3 will be official ?
>
> Should be within a few weeks.
>
Alright, so I don't know much of the makefile stuff. But can it happen
like a makefile is more optimized for a specific make version ?
Can that happen at all?
On Mon, 21 Oct 2019, 09:05 Paul Smith, wrote:
> On Sun, 2019-10-20 at 23:59 +0530, nikhil jain wrote:
> > Is this expect
.
Also I want to catch the signal in make code as I am doing some processing
there like deleting temp files etc..
What is the sequence of catching signal?
Please help.
On Mon, 21 Oct 2019, 10:47 Paul Smith, wrote:
> On Mon, 2019-10-21 at 10:11 +0530, nikhil jain wrote:
>
> Alright, s
I handle SIGINT (ctrl+c) like this in the makefile -
trap 'USER_INT=1; /bin/echo "terminating, please wait"' INT;
This traps SIGINT.
Thanks
Nikhil
On Mon, Oct 21, 2019 at 6:09 PM Paul Smith wrote:
> On Mon, 2019-10-21 at 13:00 +0530, nikhil jain wrote:
> >
On Mon, Oct 21, 2019 at 9:32 PM Paul Smith wrote:
> On Mon, 2019-10-21 at 21:26 +0530, nikhil jain wrote:
> > I handle SIGINT (ctrl+c) like this in the makefile -
> >
> > trap 'USER_INT=1; /bin/echo "terminating, please wait"' INT;
>
> That i
the build, I don't see issue as
some file would be updated and seen over NFS on the submission host.
Let me know any pointers to how I can overcome this behaviour.
Thanks
Nikhil
On Tue, 22 Oct 2019, 00:04 Paul Smith, wrote:
> On Mon, 2019-10-21 at 22:47 +0530, nikhil jain wrote:
&
Just for information.
Issue is not reproduced when replacing stat with safe_stat() which double
checks the file for stale handle.
thanks
Nikhil
On Wed, Dec 4, 2019 at 12:51 PM nikhil jain wrote:
> Thanks for all the help. There was another script which was causing issue
> with the sig
Any comments?
On Wed, 4 Dec 2019, 18:14 nikhil jain, wrote:
> Just for information.
>
> Issue is not reproduced when replacing stat with safe_stat() which double
> checks the file for stale handle.
>
> thanks
> Nikhil
>
> On Wed, Dec 4, 2019 at 12:51 PM nikhil jain
&
19 AM Paul Smith wrote:
> On Wed, 2019-12-04 at 18:14 +0530, nikhil jain wrote:
> > Just for information.
> >
> > Issue is not reproduced when replacing stat with safe_stat() which
> > double checks the file for stale handle.
> >
> > On Wed, Dec 4, 2019 at 1
file which results in
resolving pathname.
On Tue, Dec 17, 2019 at 1:17 PM nikhil jain wrote:
> I will reply on this sooner with code snippets.
>
> Just to again confirm that this actually solved a very critical issue in
> my project,
>
> A rule was processed and then as soon as
issue with NFS stale mounts which seems to be resolved if we
open the file again according to NFS specs (mentioned in another email).
Anyways, I will check if I need some more of your help. Thanks anyways.
On Tue, Dec 17, 2019 at 8:12 PM Paul Smith wrote:
> On Tue, 2019-12-17 at 13:17 +0530
Thank you Paul for the suggestions. Will think over them. Thanks for the
help.
On Tue, Dec 17, 2019 at 9:03 PM Paul Smith wrote:
> On Tue, 2019-12-17 at 20:44 +0530, nikhil jain wrote:
> > No, I do not want to delete the object file before sending the target
> > out. That's
might print the "Waiting for unfinished jobs" message above
when not necessary. */
is this related ?
Please reply. It is really urgent.
On Tue, Dec 17, 2019 at 9:04 PM nikhil jain wrote:
> Thank you Paul for the suggestions. Will think over them. Thanks for the
> help.
reaped.
Please help if you know about this problem
Thanks
Nikhil
On Wed, Jan 15, 2020 at 7:34 PM Paul Smith wrote:
> On Tue, 2020-01-14 at 15:25 +0530, nikhil jain wrote:
> > Hi Paul,
> >
> > I am coming across a strange issue in gmake.
> > in Job.c there is a condition
Any idea Paul and Team ?
On Thu, Jan 23, 2020 at 7:12 AM nikhil jain wrote:
> Ok thanks for the explanation.
>
> The issue here is the child has been reaped but when i print the Live
> child in job.c -
>
> DB (DB_JOBS, (_("Live child 0x
Hi,
There are few like you said SGE's qmake. There is one from IBM called
lsmake but it needs LSF to run.
You can actually develop your own non-standard gmake build by filling out
the stubs in the remote-stub.c file. That will be much easier.
Thanks
Nikhil
On Sat, Jan 23, 2021 at 2:13 AM Cook, M
make in main function ? How to know if
the build passed or failed ?
This is extremely urgent. Please help.
On Sun, Jan 24, 2021 at 10:59 AM nikhil jain wrote:
> Hi,
>
> There are few like you said SGE's qmake. There is one from IBM called
> lsmake but it needs LSF to run.
&
value of calling
> make. If it encountered no errors it should return 0.
>
> On Thu, May 5, 2022 at 2:11 PM nikhil jain wrote:
>
>> Hi Guys,
>>
>> I have been using gmake from a long time.
>> I wanted to know 2 things -
>>
>> 1) How do I know if th
Correct, but how do i know its a incremental or full ? any ENV is set which
says it is incremental or full ?
On Thu, May 5, 2022 at 9:38 PM Kaz Kylheku wrote:
> On 2022-05-05 06:42, nikhil jain wrote:
> > Hi Pablo,
> >
> > Thanks for your reply.
> > I actually do not
"cache" tools (ccache?) that may give you at least
> SOME idea.
>
> -Original Message-
> From: Help-make On Behalf
> Of Paul Smith
> Sent: Thursday, May 5, 2022 12:54 PM
> To: nikhil jain
> Cc: help-make
> Subject: [EXTERNAL] Re: GMAKE 3.81 vs GMAKE 4.2
Hi Brian,
I am not using -k.
My question is how do I print the exit status in the make itself
before exiting make. May be at the last of main.c (main function) ? but how
? Which variable stores the exit code just before make exits ?
Thanks
Nikhil
On Thu, May 5, 2022 at 11:48 PM Brian Cowan wro
guys for quick input. You dont know how much it will help me.
On Fri, May 6, 2022 at 1:08 AM Kaz Kylheku wrote:
> On 2022-05-05 11:07, nikhil jain wrote:
> > Thanks Paul and Brian.
> > I understand Now it's not possible to find out if it was an incremental
>
command in gnumakefile.
Please help guys.
Thanks in advance
Nikhil
On Fri, 6 May 2022 at 8:59 AM, nikhil jain wrote:
> Thanks Paul, I will utilize the die() function! I already changed make to
> be distributed. Thanks to the remote-stub.c (stub). I filled it in with my
> logic of distrib
give ctrl C . Which place in the code is best to do so?
Thanks
Nikhil
On Sun, 22 May 2022 at 4:57 AM, Paul Smith wrote:
> On Sat, 2022-05-21 at 08:37 +0530, nikhil jain wrote:
> > Also, fatal error handler in commands.C gets called multiple times. I
> > believe it is getting
ked process).
2) use -i parameter of "tee" command which means to ignore interrupts.
Both the above confirmed that the fatal_error_signal is called for main
parent process.
Thanks
Nikhil
On Sun, May 22, 2022 at 7:27 AM nikhil jain wrote:
> Thanks Paul, I know we can’t use standa
and do some stuff based on it.
On Sun, 22 May 2022 at 6:52 PM, Paul Smith 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 mem
47 matches
Mail list logo
