[bug #60774] make hangs on fcntl lock when using -O and stdout is /dev/null

Follow-up Comment #1, bug #60774 (project make): i thought i had included it originally, but i think it might be a change in the kernel version. i'm testing against linux-5.10 & glibc-2.31. ___ Reply to this item at:

[bug #60774] make hangs on fcntl lock when using -O and stdout is /dev/null

URL: Summary: make hangs on fcntl lock when using -O and stdout is /dev/null Project: make Submitted by: vapier Submitted on: Fri 11 Jun 2021 06:24:02 PM EDT Severity: 3 - Normal

[PATCH] manual: relocate $? example

The $? example shows up after all the automatic variables are discussed. This is weird as it's only relevant to the $? section, and the content that follows it is relevant to all the automatic variables. Move it up to the $? specific section. --- doc/make.texi | 24 1 fil

[bug #49773] release/archive older make manuals

URL: Summary: release/archive older make manuals Project: make Submitted by: vapier Submitted on: Mon 05 Dec 2016 06:15:27 PM GMT Severity: 3 - Normal Item Group: None

[PATCH] manual: relocate $? example

The $? example shows up after all the automatic variables are discussed. This is weird as it's only relevant to the $? section, and the content that follows it is relevant to all the automatic variables. Move it up to the $? specific section. --- doc/make.texi | 24 1 fil

[bug #30897] simple archive rules broken under make 3.82

URL: Summary: simple archive rules broken under make 3.82 Project: make Submitted by: vapier Submitted on: Sat 28 Aug 2010 10:23:19 PM GMT Severity: 3 - Normal Item Grou

[bug #30723] implicit re-executing of subdirs breaks $(origin) with make-3.82

Follow-up Comment #4, bug #30723 (project make): yes, that patch fixes things for me. now i get the "expected": Makefile:240: *** mixed implicit and normal rules. Stop. but that is something to take up with glibc maintainers ___ Reply t

[bug #30723] implicit re-executing of subdirs breaks $(origin) with make-3.82

Additional Item Attachment, bug #30723 (project make): File name: origin-breakage.tar.bz2Size:0 KB ___ Reply to this item at: ___ Message sent

[bug #30723] implicit re-executing of subdirs breaks $(origin) with make-3.82

Follow-up Comment #2, bug #30723 (project make): i tried to recreate a reduced test case but failed, but then i realized i was testing on a diff machine that had make-3.81 here is a simple reduced test case ... forget about glibc ;) $ tar xf origin-breakage.tar.bz2 $ cd origin-breakage $ make-3

[bug #30723] implicit re-executing of subdirs breaks $(origin) with make-3.82

URL: Summary: implicit re-executing of subdirs breaks $(origin) with make-3.82 Project: make Submitted by: vapier Submitted on: Tue 10 Aug 2010 05:22:11 AM GMT Severity: 3 - Normal

[bug #27714] expansion of $(shell) in target forces serialization of targets

Follow-up Comment #6, bug #27714 (project make): i dont really know how GNU make is architected, but i dont see why make cant fork the process to handle the target and then the subprocess does both deferred expansion and running the commands listed for that target. i'd also point out that other

[bug #27714] expansion of $(shell) in target forces serialization of targets

Follow-up Comment #4, bug #27714 (project make): i understand what you're saying, but i think the behavior you describe as "expected" is actually a bug. deferred variable expansion for a target shouldnt affect make's ability to run other targets.

[bug #27714] expansion of $(shell) in target forces serialization of targets

Follow-up Comment #2, bug #27714 (project make): i didnt think it a race condition because the original test case had a fairly lengthy $(shell) code and the targets always ran in the same order (and obviously only one cpu at a time -- the other cpus stayed idle) using sleep shows that it is inde

[bug #27714] expansion of $(shell) in target forces serialization of targets

URL: Summary: expansion of $(shell) in target forces serialization of targets Project: make Submitted by: vapier Submitted on: Fri 16 Oct 2009 07:50:48 AM GMT Severity: 3 - Normal

[bug #16652] typo in make(1) manpage in cvs / 3.81

URL: Summary: typo in make(1) manpage in cvs / 3.81 Project: make Submitted by: vapier Submitted on: Montag 22.05.2006 um 04:55 Severity: 3 - Normal

Re: change in SHELL behavior: feature, right ?

On Wednesday 19 April 2006 08:18, Paul D. Smith wrote: > %% Mike Frysinger <[EMAIL PROTECTED]> writes: > mf> so the question is, should gcc be making sure that the shell > mf> scripts that use SHELL pull the value from configure ? or is make > mf> broken ? &

change in SHELL behavior: feature, right ?

with the new handling of SHELL, gcc fails to build under non posix compatible shells (like tcsh) or if the env SHELL is set to a non-existant shell (think zsh on the host system and chrooting into a local filesystem and using bash ... bash by design doesnt reset the SHELL=/bin/zsh value) the bi

update man-page

attached is a patch to update the manpage with the latest features that cvs make has to offer -mike 2005-11-22 Mike Frysinger <[EMAIL PROTECTED]> * make.1: Fix some display errors and document all existing options. --- make/make.1 +++ make/make.1 @@ -1,4 +1,4 @@ -.TH MAKE 1L &quo