Re: GNU make 4.3.91 on CentOS 8 Stream

On Wed, 2022-10-19 at 04:44 +0200, Bruno Haible wrote: > > I saw a similar test timeout. > > If the test hit a timeout, the timeout is definitely too small. It's strange. The timeout on this is 4 seconds, but it's just waiting for a file to be created by a different target. It's hard to imagine

Re: GNU make 4.3.91 on Debian 9.1

On Wed, 2022-10-19 at 15:59 +0200, Bruno Haible wrote: > > Maybe just augmenting the check target to do more? > > Yes. Instead of printing >   See .diff* files in work dir for details it could >   - generate a summary file with details (like test-suite.log, described >     above), and/or >   - gen

Re: [bug #62936] Confusing description of chained rules in the manual

On Wed, 2022-10-19 at 07:28 +0100, Tim Murphy wrote: > Outside of make "update" implies existence - we use CRUD as a term > for example not RUD.  Why redefine the language? Actually for > databases the word "upsert" has been invented to explain a roughly > analagous situation is going on - perhaps

A complete example of quoting an arbitrary value as a word in a shell script

Hi, Maybe this has been done before, but I couldn't find it on the nets. The example Makefile below illustrates how to quote an arbitrary value as a word in a shell script. One use case for this is to evaluate a value as a complete shell script, similar to .ONESHELL but allowing all shell fe

Re: [bug #62936] Confusing description of chained rules in the manual

On Sat, 22 Oct 2022, 20:33 Paul Smith, wrote: > On Wed, 2022-10-19 at 07:28 +0100, Tim Murphy wrote: > > Outside of make "update" implies existence - we use CRUD as a term > > for example not RUD. Why redefine the language? Actually for > > databases the word "upsert" has been invented to explai

Re: GNU make 4.3.91 on CentOS 8 Stream

On Sun, 2022-10-23 at 16:17 +0200, Bruno Haible wrote: > Paul Smith wrote: > > I bumped the timeout to 10 seconds because, why not?  I'll be > > interested to see if we still get these timeouts... > > Yes, with tmout changed from 4 to 10 in tests/thelp.pl, I still > see these failures among the ou

Re: GNU make 4.3.91 release candidate available

On Sat, 2022-10-22 at 10:16 -0400, Paul Smith wrote: > > This warning doesn't seem to be given for indirect targets as e.g. > > would be the case with bison and cc: %.y -> %.[ch] -> %.o which was > > the case that caused me problems with 4.3.90. I've since fixed my > > Makefile, so no actual proble

Re: [bug #62936] Confusing description of chained rules in the manual

On Sat, 2022-10-22 at 21:13 +0100, Tim Murphy wrote: > On Sat, 22 Oct 2022, 20:33 Paul Smith, wrote: > > "Updating a target" has a well-defined meaning that's used > > everywhere in the documentation and the mailing lists etc., and > > it's also the term used everywhere in the POSIX spec for the >

Re: GNU make 4.3.91 on Manjaro 17 — bi-arch problem

On Wed, 2022-10-19 at 02:20 +0200, Bruno Haible wrote: > The cause: > libguile-2.2.so happens to be installed only as 64-bit binaries, in > /usr/lib. > Not as 32-bit binaries, in /usr/lib32. Yet, /usr/include/guile/2.2/ > exists. I added extra configure checking to try to link with Guile, not just

[bug #63260] Avoid infinite recursion.

Follow-up Comment #2, bug #63260 (project make): I am not adding a test. Existing tests in features/output-sync fail. ___ Reply to this item at: ___ Mes

Re: GNU make 4.3.91 on CentOS 8 Stream

Paul Smith wrote: > I bumped the timeout to 10 seconds because, why not? I'll be > interested to see if we still get these timeouts... Yes, with tmout changed from 4 to 10 in tests/thelp.pl, I still see these failures among the output-sync tests. On a machine with minimal load. Bruno

Re: GNU make 4.3.91 release candidate available

When replying to the release messages we should try to trim the "CC" list to avoid spamming the translators and testers. In future releases I will send separate announce emails to the lists, translators, and testers. On Wed, 2022-10-19 at 06:31 +0200, Frank Heckenbach wrote: > > * WARNING: Futur

[bug #63260] Avoid infinite recursion.

Follow-up Comment #3, bug #63260 (project make): The same effect can be seen on a filesystem which supports O_TMPFILE, if TMPDIR is set to a non existing directory. ___ Reply to this item at:

Re: GNU make 4.3.91 on GNU/Hurd

On Wed, 2022-10-19 at 03:14 +0200, Bruno Haible wrote: > PATH_MAX does not exist on GNU/Hurd (intentionally, because file > names are of arbitrary length). Thanks, I've fixed this by setting a large value (4096) as PATH_MAX if it's not set anywhere. Ideally GNU make would also allow arbitrarily-

[bug #63260] Avoid infinite recursion.

URL: Summary: Avoid infinite recursion. Project: make Submitter: dgoncharov Submitted: Sun 23 Oct 2022 03:10:12 PM UTC Severity: 3 - Normal Item Group: Bug

[bug #63260] Avoid infinite recursion.

Additional Item Attachment, bug #63260 (project make): File name: sv63260.fixSize:2 KB ___ Reply to this item at:

Re: GNU make 4.3.91 on Debian 9.1

Paul Smith wrote: > *** Testing failed! Details saved in: makeerror-x86_64-pc-linux-gnu.tar.gz > *** Please report to > > make[3]: *** [Makefile:1537: check-regression] Error 1 > make[2]: *** [Makefile:1271: check-am] Error 2 > make[1]: *** [Makefile:973: check-recursive] Error 1 > m

[bug #63260] Avoid infinite recursion.

Update of bug #63260 (project make): Status:None => Fixed Assigned to:None => psmith Open/Closed:Open => Closed Fixed Release:

[bug #63260] Avoid infinite recursion.

Follow-up Comment #1, bug #63260 (project make): The current make enters infinite recursion on a filesystem that does not support O_TMPFILE. $ cat makefile all:; $(info hello, world) $ # current make from master $ ~/src/gmake/make/m64/make -Orecurse Segmentation fault (core dumped) Th

[bug #63243] Fix a race between sigterm and make writing its error message.

Update of bug #63243 (project make): Status:None => Fixed Open/Closed:Open => Closed Fixed Release:None => SCM Triage Status:

[bug #63248] Ignore sigpipe.

Update of bug #63248 (project make): Status:None => Fixed Open/Closed:Open => Closed Fixed Release:None => SCM Triage Status: