Re: Parallel Jobs Bug

[Christopher Faylor]

On Sun, Jan 28, 2007 at 05:06:50PM -0500, Paul Smith wrote:
>On Sun, 2007-01-28 at 13:27 -0800, Bill Harding wrote:
>> In regards to Paul's earlier questions about the version and
>> distribution of my make, it is a Cygwin version of make running on
>> Windows XP.  Specifically, if I access my make's help it says "Program
>> built for i686-pc-cygwin".  The version of make is GNU Make 3.80.  
>
>The Cygwin version of GNU make 3.80 (and below) have some special
>customizations that aren't part of vanilla GNU make 3.80.  I suggest you
>continue to work with the folks on the Cygwin mailing list to try to
>resolve this issue.  I do find it odd that the errors seemed to suggest
>you were running cmd.exe, if you're using a Cygwin environment.
>However, the folks on the Cygwin lists will be better able to advise
>you.

We don't generally support older versions of released programs so moving to
3.81 is advised.

cgf


___
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make

[bug #18872] problem colon after drive letter in prerequisite

[Paul D. Smith]

Update of bug #18872 (project make):

  Status:None => Fixed  
 Open/Closed:Open => Closed 
   Component Version:None => 3.81   
   Fixed Release:None => CVS

___

Follow-up Comment #2:

Only project admins can change the state of a bug (so you can't re-open it). 
If GCC is generated drive-lettered pathnames in a cygwin environment that is
arguably a bug in GCC on Cygwin; you should report it to either or both GCC
or Cygwin.

However, as Eli points out there has already been a change incorporated to
allow GNU make on Cygwin to handle drive letters properly (for some
definition of properly).  This change will be available in the next release
of GNU make.

___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/



___
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make

RE: Parallel Jobs Bug

[Paul Smith]

On Sun, 2007-01-28 at 13:27 -0800, Bill Harding wrote:
> In regards to Paul's earlier questions about the version and
> distribution of my make, it is a Cygwin version of make running on
> Windows XP.  Specifically, if I access my make's help it says "Program
> built for i686-pc-cygwin".  The version of make is GNU Make 3.80.  

The Cygwin version of GNU make 3.80 (and below) have some special
customizations that aren't part of vanilla GNU make 3.80.  I suggest you
continue to work with the folks on the Cygwin mailing list to try to
resolve this issue.  I do find it odd that the errors seemed to suggest
you were running cmd.exe, if you're using a Cygwin environment.
However, the folks on the Cygwin lists will be better able to advise
you.

Starting with GNU make 3.81, the cygwin port is supported natively and
doesn't involve any extra code modifications (as far as I know).  If you
still have problems with that version then we may be able to help.

-- 
---
 Paul D. Smith <[EMAIL PROTECTED]>  Find some GNU make tips at:
 http://www.gnu.org  http://make.paulandlesley.org
 "Please remain calm...I may be mad, but I am a professional." --Mad Scientist


___
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make

RE: Parallel Jobs Bug

[Bill Harding]

In regards to Paul's earlier questions about the version and
distribution of my make, it is a Cygwin version of make running on
Windows XP.  Specifically, if I access my make's help it says "Program
built for i686-pc-cygwin".  The version of make is GNU Make 3.80.  

--Bill

-Original Message-
From: Eli Zaretskii [mailto:[EMAIL PROTECTED] 
Sent: Sunday, January 28, 2007 12:23 PM
To: [EMAIL PROTECTED]
Cc: Bill Harding; bug-make@gnu.org
Subject: Re: Parallel Jobs Bug

> From: Paul Smith <[EMAIL PROTECTED]>
> Date: Sun, 28 Jan 2007 09:42:25 -0500
> Cc: bug-make@gnu.org
> 
> 
>   * the code that generates that output is conditionally compiled
> only if MAKE_JOBSERVERS is set, and that macro is set only if
> the configure script detects a number of POSIX-like features
in
> your OS.  If you build using the default config.h.W32 etc. and
> don't run configure, that macro is not set and that code does
> not even exist in the program anywhere!

It probably just means that the OP is using the Cygwin port of Make.
Which, of course, doesn't explain this:

>   * If the code is compiled in, it's only invoked if there is a
> jobserver pipe, and there is only a jobserver pipe if one of
two
> things is true: a -jN was passed where N>1 was passed to make
on
> the compile line, or the option --jobserver-fds (which is an
> internal option passed by make to its submakes and should
never
> be given to make externally) was passed to make.


___
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make

Re: Parallel Jobs Bug

[Christopher Faylor]

On Sun, Jan 28, 2007 at 10:22:52PM +0200, Eli Zaretskii wrote:
>> From: Paul Smith
>> Date: Sun, 28 Jan 2007 09:42:25 -0500
>> 
>> 
>>   * the code that generates that output is conditionally compiled
>> only if MAKE_JOBSERVERS is set, and that macro is set only if
>> the configure script detects a number of POSIX-like features in
>> your OS.  If you build using the default config.h.W32 etc. and
>> don't run configure, that macro is not set and that code does
>> not even exist in the program anywhere!
>
>It probably just means that the OP is using the Cygwin port of Make.

Yes, the problem was reported to the cygwin list as well.

cgf


___
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make

Re: Parallel Jobs Bug

[Eli Zaretskii]

> From: Paul Smith <[EMAIL PROTECTED]>
> Date: Sun, 28 Jan 2007 09:42:25 -0500
> Cc: bug-make@gnu.org
> 
> 
>   * the code that generates that output is conditionally compiled
> only if MAKE_JOBSERVERS is set, and that macro is set only if
> the configure script detects a number of POSIX-like features in
> your OS.  If you build using the default config.h.W32 etc. and
> don't run configure, that macro is not set and that code does
> not even exist in the program anywhere!

It probably just means that the OP is using the Cygwin port of Make.
Which, of course, doesn't explain this:

>   * If the code is compiled in, it's only invoked if there is a
> jobserver pipe, and there is only a jobserver pipe if one of two
> things is true: a -jN was passed where N>1 was passed to make on
> the compile line, or the option --jobserver-fds (which is an
> internal option passed by make to its submakes and should never
> be given to make externally) was passed to make.


___
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make

Re: Parallel Jobs Bug

[Paul Smith]

On Sun, 2007-01-28 at 00:24 -0800, Bill Harding wrote:

> make -C Anims --no-print-directory -r -f Anims.mk all &&  make -C BGs
> --no-print-directory -r -f BGs.mk all 
> 
> However, at seemingly random intervals throughout the build process
> (usually about 4-5 times per build), I get the following error:
>  
> make[1]: *** read jobs pipe: No such file or directory.  Stop.
> make[1]: *** Waiting for unfinished jobs
> ShIdleA.ica
> make[1]: *** Waiting for unfinished jobs
> make: *** [build] Error 2
> Error executing c:\windows\system32\cmd.exe.

This is extremely strange.  First, when asking for help please ALWAYS
provide the version of GNU make you're using, as well as the type and
version of the system you're using it on.  Here it looks like you're
running on some kind of Windows system; in that case please provide
information about how make was built (cygwin?  MINGW?  DOS?  Etc.)  You
might also try asking on the make-w32@gnu.org mailing list, since the
folks most knowledgeable about the idiosyncrasies of make on Windows
platforms tend to hang out there.

Anyway, a few facts:
  * the code that generates that output is conditionally compiled
only if MAKE_JOBSERVERS is set, and that macro is set only if
the configure script detects a number of POSIX-like features in
your OS.  If you build using the default config.h.W32 etc. and
don't run configure, that macro is not set and that code does
not even exist in the program anywhere!
  * If the code is compiled in, it's only invoked if there is a
jobserver pipe, and there is only a jobserver pipe if one of two
things is true: a -jN was passed where N>1 was passed to make on
the compile line, or the option --jobserver-fds (which is an
internal option passed by make to its submakes and should never
be given to make externally) was passed to make.

Altogether I can't see how the behavior you're seeing is possible with
the standard version of make.

Please provide the information mentioned above.  Also you should run
make with -d and see if it gives any clues.

-- 
---
 Paul D. Smith <[EMAIL PROTECTED]>  Find some GNU make tips at:
 http://www.gnu.org  http://make.paulandlesley.org
 "Please remain calm...I may be mad, but I am a professional." --Mad Scientist


___
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make

Parallel Jobs Bug

[Bill Harding]

Hi Bug Team,
 
I have been combatting a make bug for several months, and after many,
many hours of web searching, I am finally breaking down to see if you
might possibly have some idea about what I can do about this bug.  The
issue is that I am building assets for a video game using the following
command:
 
make -C Anims --no-print-directory -r -f Anims.mk all &&  make -C BGs
--no-print-directory -r -f BGs.mk all 

However, at seemingly random intervals throughout the build process
(usually about 4-5 times per build), I get the following error:
 
make[1]: *** read jobs pipe: No such file or directory.  Stop.
make[1]: *** Waiting for unfinished jobs
ShIdleA.ica
make[1]: *** Waiting for unfinished jobs
make: *** [build] Error 2
Error executing c:\windows\system32\cmd.exe.
 
After I get this error, I can invoke the build again and it will start
building files again where it had left off, indicating that there was no
problem with the asset itself.  The most perplexing part of this "jobs
pipe error" is that I am not using jobs.  Even if I explicitly pass make
a -j1 flag, it still gives me this error maddeningly often, and
cumulatively this ends up being an enormous time cost.  Do you have any
idea why I would be getting this error when I am not using jobs, and
more importantly, if there is anything that could be done to fix it?
 
Thanks!
Bill Harding
Lead Developer
Amaze Entertainment
___
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make

GNU MAKE

[suresh babu]

hI Paul Smith,
   
  I am interested to do development required for GNU make.  Can you give me the 
details what should I do?
   
  regards,
  sureshbk.
   


-
Everyone is raving about the all-new Yahoo! Mail beta.___
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make