[bug #38420] $(realpath ...) doesn't recover from signals

Update of bug #38420 (project make): Item Group:None => Bug Status:None => Fixed Assigned to:None => psmith Open/Closed:

Re: [bug #38433] Example for "eval" in documentation contains error with "define"

On Wed, 2013-02-27 at 19:04 -0800, David Boyce wrote: > I think you and the others in the "nay" camp may be being a bit > unfair. As far as I can see, nobody has proposed (in this thread) that > the entire manual be reworked to note the version in which each > feature appeared. You're absolutely

[bug #38437] cannot find the include file

Update of bug #38437 (project make): Status:None => Not A Bug Open/Closed:Open => Closed ___ Follow-up Comment #1: This is how GNU make h

Re: [bug #38437] cannot find the include file

On Wed, Feb 27, 2013 at 8:55 PM, Jian wrote: ... > Supposing 2 makefiles in dir A: 1.mak, 2.mak, and 1.mak include 2.mak. > Now in dir B, 3.mak includes 'A/1.mak' (will auto include 2.mak). But error > shows that 2.mak cannot be found. > > The make option "-I" can be the workaround like: > cd B >

[bug #38437] cannot find the include file

URL: Summary: cannot find the include file Project: make Submitted by: skyshore Submitted on: Thu 28 Feb 2013 04:55:23 AM GMT Severity: 3 - Normal Item Group: Bug

[bug #38432] Optional parameter to tag all output lines with unique text to improve logging capabilities

Follow-up Comment #1, bug #38432 (project make): WIthout discussing the merits of this particular proposal I will simply point out that this is a frequently-solved problem, though nothing has yet entered the GNU Make code base. I believe there have been multiple patches offered and numerous email

Re: [bug #38433] Example for "eval" in documentation contains error with "define"

On Wed, Feb 27, 2013 at 5:02 PM, Philip Guenther wrote: > Side note: I should make clear that I am not committer to GNU make and > do not speak for the project. I'm just a contributer to the lists, > answering questions where I can. > Likewise. > IMO, the suggestion that was proposed would re

Re: [bug #38433] Example for "eval" in documentation contains error with "define"

On Wed, Feb 27, 2013 at 2:42 PM, Sebastian Pipping wrote: > Paul and Philipp, Side note: I should make clear that I am not committer to GNU make and do not speak for the project. I'm just a contributer to the lists, answering questions where I can. > Daniel has a valid point here. You could b

[bug #38433] Example for "eval" in documentation contains error with "define"

Follow-up Comment #2, bug #38433 (project make): Paul and Philipp, Daniel has a valid point here. You could be a lot more welcoming on this case, why so hard on him? I hit the very same thing myself some time ago, just forgot to speak up myself. That documentation "bug" is the reason meta pro

Re: [bug #38433] Example for "eval" in documentation contains error with "define"

On Wed, 2013-02-27 at 13:56 -0800, Daniel Wagenaar wrote: > I appreciate your correction, but I still feel that the documentation > on the website would be more helpful if it at least mentioned that > older versions of make fail quietly when there is a "=" at the end of > the line. GNU make has be

Re: [bug #38433] Example for "eval" in documentation contains error with "define"

On 02/27/2013 02:07 PM, Philip Guenther wrote: On Wed, Feb 27, 2013 at 1:56 PM, Daniel Wagenaar wrote: I appreciate your correction, but I still feel that the documentation on the website would be more helpful if it at least mentioned that older versions of make fail quietly when there is a "="

Re: [bug #38433] Example for "eval" in documentation contains error with "define"

On Wed, Feb 27, 2013 at 1:56 PM, Daniel Wagenaar wrote: > I appreciate your correction, but I still feel that the documentation on the > website would be more helpful if it at least mentioned that older versions > of make fail quietly when there is a "=" at the end of the line. The reason > is tha

Re: [bug #38433] Example for "eval" in documentation contains error with "define"

On 02/27/2013 11:30 AM, Philip Guenther wrote: On Wed, Feb 27, 2013 at 11:25 AM, Daniel Wagenaar wrote: The example for the "eval" function in the documentation at http://www.gnu.org/software/make/manual/html_node/Eval-Function.html contains a syntax error that causes the example to fail quiet

Re: [bug #38420] $(realpath ...) doesn't recover from signals

On Wed, 2013-02-27 at 12:47 -0700, Brian Vandenberg wrote: > What it doesn't make clear is, if it's configured with 'nointr' will > that just cause the system function to block? That seems the most > plausible. Correct. With nointr, you won't be able to (for example) ^C a program that is hung wa

Re: [bug #38420] $(realpath ...) doesn't recover from signals

On Wed, Feb 27, 2013 at 11:36 AM, Philip Guenther wrote: > On Wed, Feb 27, 2013 at 9:44 AM, Brian Vandenberg > wrote: >> Follow-up Comment #3, bug #38420 (project make): >> You're spot on. It is Solaris / NFS 3. >> >> In the interim I'm using a build with the fix I suggested. >> >> Do you

[bug #38433] Example for "eval" in documentation contains error with "define"

Update of bug #38433 (project make): Status:None => Not A Bug Open/Closed:Open => Closed ___ Follow-up Comment #1: That's a valid stateme

Re: [bug #38433] Example for "eval" in documentation contains error with "define"

On Wed, Feb 27, 2013 at 11:25 AM, Daniel Wagenaar wrote: > The example for the "eval" function in the documentation at > http://www.gnu.org/software/make/manual/html_node/Eval-Function.html contains > a syntax error that causes the example to fail quietly. The problem is in the > line > > def

[bug #38420] $(realpath ...) doesn't recover from signals

Follow-up Comment #5, bug #38420 (project make): Paul, I'm using `realpath` for defensive coding purposes. I'm using a pattern rule of the form: %.so : $(if $(realpath $(filter %.o,${^})),,$(warning No dependencies specified for ${@})@false) recipe goes here ... where the dependencies ar

[bug #38433] Example for "eval" in documentation contains error with "define"

URL: Summary: Example for "eval" in documentation contains error with "define" Project: make Submitted by: wagenaar Submitted on: Wed 27 Feb 2013 07:25:20 PM GMT Severity: 3 - Normal

[bug #38432] Optional parameter to tag all output lines with unique text to improve logging capabilities

URL: Summary: Optional parameter to tag all output lines with unique text to improve logging capabilities Project: make Submitted by: phantal Submitted on: Wed 27 Feb 2013 07:13:05 PM GMT

Re: [bug #38420] $(realpath ...) doesn't recover from signals

On Wed, Feb 27, 2013 at 9:44 AM, Brian Vandenberg wrote: > Follow-up Comment #3, bug #38420 (project make): > You're spot on. It is Solaris / NFS 3. > > In the interim I'm using a build with the fix I suggested. > > Do you know of a workaround for this that wouldn't require deploying a > mo

[bug #38420] $(realpath ...) doesn't recover from signals

Follow-up Comment #4, bug #38420 (project make): The only option I can think of is using $(shell ...) to determine the real path rather than the built-in realpath function. This will be slower, but more reliable (as far as I'm aware all the EINTR issues with shell have long since been solved). M

[bug #38420] $(realpath ...) doesn't recover from signals

Follow-up Comment #3, bug #38420 (project make): Paul, You're spot on. It is Solaris / NFS 3. In the interim I'm using a build with the fix I suggested. Do you know of a workaround for this that wouldn't require deploying a modified version of make? _