Re: MAKEFLAGS=-r

Dmitry Goncharov wrote: > On Mon, Jul 17, 2023 at 5:45 AM Bruno Haible wrote: > > And finally, MAKEFLAGS is not even mentioned in the main index of the GNU > > Make > > documentation [5], and only regarding "recursion" in the Variables index > > [6]. &g

Re: MAKEFLAGS=-r

ile at a time. Together with the other arguments by Paul [1], this means the .SUFFIXES approach is much much preferable. Bruno [1] https://lists.gnu.org/archive/html/bug-make/2023-07/msg00063.html

Re: disabling the built-in rules

Paul Smith wrote: > POSIX > reserves all targets prefixed with "." (that are not already specified > in the standard) to the implementation. So it's fine with POSIX to add > a pseudo target like .NOBUILTINS; no conforming makefile can use that > target for anything else. Thanks for explaining!

Re: disabling the built-in rules

of the built-in database, say, .NO_GNU_BUILTINS. And users would have to write: .SUFFIXES: .NO_GNU_BUILTINS: Bruno

Re: disabling the built-in rules

because it does not work portably: On FreeBSD and NetBSD, 'make' gives an error: make: don't know how to make %,v. Stop Similarly on OpenBSD: make: don't know how to make %,v (prerequisite of: %) Can we get a syntax to clear all built-in rules that works portably? For example, such as: .SUFFIXES: .GNUSUFFIXES: Bruno

Re: MAKEFLAGS=-r

t. I confused it with the := assignment operator. Bruno

Re: MAKEFLAGS=-r

of implicit rules because Automake provides the rules already, it's either MAKEFLAGS=-r or nothing at all. Bruno

Re: GNU make troubleshooting

;when experimenting, change only one variable at a time". Because if they change two variables at once and get and improvement, they won't know which variable change is responsible for it. > Another approach for the case when you cannot modify the makefile is this > > $ cat makefile > all: hello > $ make -nd |wc >13347530 63382 > $ make -E $'.DEFAULT_GOAL:=all\nmakefile::;' -nd |wc > 7324117 32947 This is better for text under the topic "Understanding a Makefile's action". Thanks. Bruno

Re: MAKEFLAGS=-r

a subdirectory needs built-in rules, will the MAKEFLAGS=-r setting propagate to the subdirectory? In other words, is it a good idea to use MAKEFLAGS=-r in Makefiles that recurse to other Makefiles (and that are maintained independently)? Bruno [1] https://www.gnu.org/savannah-checkouts/gnu/autoc

Re: GNU make troubleshooting

You can grep away most of the matching lines with 'grep -v makefile'. Then it's useful to present this as a filter in the troubleshooting section. Bruno

Re: GNU make troubleshooting

refer to get told to add an option: $ make -n -d -r |tail +7 |wc because that allows me to continue with an unmodified Makefile. Can the addition of 'makefile::;' be replaced by a make option or by some (sed-based?) postprocessing? So that we arrive at the same 37 lines with a common of the form $ make -n -d SOME_MORE_OPTIONS | tail +7 | SOME_MORE_FILTER ? Bruno

Re: GNU make troubleshooting

ous troubleshooting tricks in a chapter "Troubleshooting" in the doc. Bruno

Re: GNU make troubleshooting

does not exist With 4.4.1, I see this too. A nice improvement! Bruno

Re: GNU make troubleshooting

Paul Smith wrote: > Maybe a version difference. I'm using 4.4. I get the same output with GNU make 4.4 as with 4.3. Bruno

Re: GNU make troubleshooting

someone else wants to do it but my suspicion > is that the code changes needed would be massively disruptive. That sounds like a discussion among GNU make contributors could maybe bring up alternative implementation ideas, that are not so disruptive? Bruno [1] https://www.gnu.org/software/make/m

Re: GNU make troubleshooting

need them" and another person saying "If the output is 100 lines long or longer, you lost me". How about introducing _options_ whose goal is not to produce maximal information, but small-sized and still useful information? Bruno

Re: GNU make troubleshooting

only the file with the newest timestamp. Files with older timestamps are redundant.) The important fact is that the file mbrtoc32.o does not exist; the output should mention this. Bruno

GNU make troubleshooting

s 9 and 13 explain operational aspects, but none goes into troubleshooting details. For a complex program like GNU make, probably at least 10 or 20 pages on this topic are needed. Best regards, Bruno [1] https://www.airs.com/blog/archives/95 [2] https://www.gnu.org/software/make/manual/html_node/Functions.html

Re: GNU Make 4.4.0.91 on openSUSE Leap 15.2

Paul Smith wrote: > In the abstract it would be nice to have configure detect the bug in > glibc and use our local version of glob on those systems, but writing a > runtime test for the actual bug would be "interesting". gnulib/m4/glob.m4 contains a test for this bug: AC_CACHE_CHECK([whethe

GNU Make 4.4.0.91 on other platforms

/bug-make/2023-01/msg00101.html is fixed. - macOS 12.5 I.e. the 2 test failures reported in https://lists.gnu.org/archive/html/bug-make/2023-01/msg00108.html are gone. - FreeBSD 11, NetBSD 9, OpenBSD 6.5 - Solaris 10 Bruno

Re: GNU Make 4.4.0.91 on Solaris 11.4 (32-bit)

features/archives patch. Results: - 64 bit: All tests pass. - 32 bit: All tests pass. Yeah! Bruno

Re: GNU Make 4.4.0.91 on GNU/Hurd

e systems. I've retested one of the systems: Solaris 11.4 (64-bit). Your patch fixes the two remaining test failures. Now, all tests pass. Bruno

GNU Make 4.4.0.91 on Solaris 11.4 (32-bit)

On Solaris 11.4 (32-bit mode): All 4 test failures in category 'features/archives', reported in , are still present. Somehow your fix for archives.12 and archives.13 does not work in this environment. I'm attaching the config.statu

Re: GNU Make 4.4.0.91 on GNU/Hurd

he other systems that don't > provide a "cc". Yes, I see these also on: - Debian 11.1 - Solaris 11.4 (64-bit) - Solaris 11 OmniOS - Solaris 11 OpenIndiana Bruno

GNU Make 4.4.0.91 on openSUSE Leap 15.2

On openSUSE Leap 15.2, the results are better than with 4.4.0.90 : - The wildcard.9 failure (well-known), - 2 failures in the 'features/archives' category, due to "cc: command not found". makeerror-4.4.0.91-x86_64-pc-linux-gnu

Re: GNU Make 4.4.0.91 on AIX 7.2

Paul Smith wrote: > Does touch on AIX support the "-a" option? Yes. "-a" is a documented option of /usr/bin/touch, and it works fine. Bruno

GNU Make 4.4.0.91 on AIX 7.2

On AIX 7.2 as well, the results are much better than for 4.4.0.90 : Only 3 test failures: - 2 from category 'features/archives', due to "cc: not found" - 1 from category 'features/include'. makeerror-4.4.0.91-powerpc-ibm-ai

GNU Make 4.4.0.91 on Cygwin

On Cygwin (running in Windows 10), the results are much better than those of 4.4.0.90 : All "Device or resource busy" failures are gone. Only the 1 failure in category 'misc/general4' is still present. makeerror-4.4.0.91-x86_64-

GNU Make 4.4.0.91 on GNU/Hurd

On GNU/Hurd, much fewer test failures than with 4.4.0.90 : Only 2 test failures, in category 'features/archives', due to "cc: not found". makeerror-4.4.0.91-i686-unknown-gnu0.9-0wnh.tar.gz Description: application/compressed-tar

Re: GNU Make 4.4.0.90 on GNU/Hurd

ystem's > glob implementation, somehow. Yes. Reported as a glibc bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30146 Bruno

Re: Regression on Cygwin: Problems with parallel make in 4.4

es in category 'features/archives', due to "cc: not found". - 4 failures in category 'features/jobserver' - 2 failure in category 'functions/shell' Bruno makeerror-4.4.0.90-i686-unknown-gnu0.9-aonj.tar.gz Description: application/compressed-tar

Re: GNU Make 4.4.0.90 on GNU/Hurd

gt; - 5 failures in category 'features/jobserver' > - 2 failures in category 'features/parallelism' > - 1 failure in category 'features/recursion' > - 1 failure in category 'functions/shell' Note that on this platform, the build log has a

Re: Regression on Cygwin: Problems with parallel make in 4.4

files" in GNU/Hurd, we see "Device or resource busy" in Cygwin." Bruno [1] https://lists.gnu.org/archive/html/bug-make/2023-01/msg00134.html

Re: Regression on Cygwin: Problems with parallel make in 4.4

Ken Brown wrote: > I suggest > that you provide a configure option to set the jobserver style at the > time make is built, and set it to 'pipe' by default on Cygwin. And possibly also on GNU/Hurd. Cf. https://lists.gnu.org/archive/html/bug-make/2023-01/msg00107.html Bruno

Re: OpenIndiana installation

tee log2 \ && gmake check 2>&1 | tee log3 ===== Sometimes I also do "gmake check" without the redirection; there's normally no difference between with and without redirection. Bruno

Re: CentOS Stream installation

ort 22 -j ACCEPT For CentOS 8 probably something like sudo nft add rule inet firewalld filter_IN_public_allow tcp dport 22 accept > And normally I don't have an SSH server running on my host machine, > since I don't need to log into it from anywhere and it's more secure > that way Yeah, everyone has different preferences. Leading to different network topologies in each case. Bruno

Re: CentOS Stream installation

27;scp' each time), and that the mouse handling is a bit more annoying. Bruno = CentOS 8 in VirtualBox == Use CentOS 8 stream 2022-10-05 from https://ftp.gwdg.de/pub/linux/centos/8-stream/isos/x86_64/ Disk size: 15 GB. The installation menu is

Re: OpenIndiana installation

out the actual package names that one needs to install. I hope my writeup (below) helps. Bruno === Solaris 11 OpenIndiana in VirtualBox OpenIndiana, a distro based on Illumos - roughly Solaris 11 compatible. Download: http://dlc.openindiana.org/isos/hipster/20221

Re: GNU Make 4.4.0.90 on AIX 7.2

ld process > in some situations. (I had seen this many years ago, in AIX 4 or AIX 5.) config.h contains: /* #undef USE_POSIX_SPAWN */ Replacing 'vfork ()' with 'fork ()' in src/job.c does not help. Bruno

Re: GNU Make 4.4.0.90 on Cygwin

On Cygwin 2.9.0 (running in Windows 10), I see these test failures: * Same failures as seen in GNU/Hurd: - 5 failures in category 'features/jobserver' - 2 failures in category 'features/parallelism' - 1 failure in category 'features/recursion' - 1 failure in category 'functions/shell'

Re: GNU Make 4.4.0.90 on AIX 7.2

On AIX 7.2, in 64-bit mode, with the environment variables settings CC="xlc -q64 -qthreaded -qtls"; CXX="xlC -q64 -qthreaded -qtls"; AR="ar -X 64"; NM="nm -X 64 -B"; export CC CXX AR NM (with which I build many GNU packages successfully), I get 20 test failures: * 16 failures in catego

Re: GNU Make 4.4.0.90 on Solaris 11 OpenIndiana

On Solaris 11 OpenIndiana (from 2022), aside from the 4 well-known test failures in 'features/archives', in 64-bit mode I also see a test failure in category 'features/output-sync', with an error message "timeout after 10 seconds". I don't know why only this 1 out of 3 output-sync tests (compared

Re: GNU Make 4.4.0.90 on Solaris 11 OmniOS

On Solaris 11 OmniOS, aside from the well-known 4 features/archives failures, I see 3 test failures in the 'features/output-sync' category. They come with an error message "timeout after 10 seconds". Here the logs: - 32-bit build: makeerror-4.4.0.90-x86_64-pc-solaris2.11-thix.tar.gz - 64-bit b

Re: GNU Make 4.4.0.90 on Solaris 11.4

The same 4 failures in features/archives ("cc: not found") also occur on Solaris 11.4. On this platform, 'cc' does not exist in $PATH, but 'gcc' does. Find attached the logs. makeerror-4.4.0.90-x86_64-pc-solaris2.11-q6is.tar.gz Description: application/compressed-tar

Re: GNU/Hurd installation

mount of background knowledge, which is then the basis for finding the right setting that makes things work. Sorry, I had expected that it would be as smooth for you as it was for me. Bruno [1] https://www.virtualbox.org/manual/UserManual.html

Re: GNU/Hurd installation

Disable* all extended features (PAE/NX, Nested VT-x) [The latter is what I meant above.] - System: Paravirtualization Interface: You can try different values than 'Default'. Do you have other VirtualBox VMs that work? If not, i.e. if you get problems also with other OSes as guests, I would verify that VT-x/AMD-V is enabled in the UEFI/BIOS. Bruno

Re: GNU/Hurd installation

Paul Smith wrote: > I will download a GNU/Hurd KVM image, as suggested here: > > https://www.debian.org/ports/hurd/hurd-cd > > is that appropriate for testing? Yes. The GNU/Hurd installation instructions vary a bit over time, but these are my notes from 5 months ago. Fill in the ** fields.

Re: GNU Make 4.4.0.90 on macOS 12

On macOS 12.5 / arm64 I see two test failures: - output-sync - temp_stdin Find attached the log files. The machine is gcc104.fsffrance.org. makeerror-4.4.0.90-aarch64-apple-darwin21.6.0-050w.tar.gz Description: application/compressed-tar

Re: GNU Make 4.4.0.90 on GNU/Hurd

On GNU/Hurd (from 2022), I get 13 test failures: New: - 4 failures in category 'features/archives', due to "cc: not found". Already reported in https://lists.gnu.org/archive/html/bug-make/2022-10/msg00218.html : - 5 failures in category 'features/jobserver' - 2 failures in category 'featu

Re: GNU Make 4.4.0.90 on Debian 11.1

s [1], a GNU package should use $CC, not 'cc' — so that users have the freedom to use a compiler of their choice (clang, TinyCC, whatever...). In this test you have the lines # Fallback if configure did not find AR my $ar = get_config('AR') || 'ar'; Why

Re: GNU Make 4.4.0.90 on Manjaro 17 — bi-arch problem

On Manjaro Linux 17, installed from manjaro-kde-17.1.12-stable-x86_64.iso, in 32-bit mode, the build failure reported in https://lists.gnu.org/archive/html/bug-make/2022-10/msg00212.html still occurs. Find the build details attached. makeerror-manjaro17-32bit.tar.gz Description: application/co

Re: GNU Make 4.4.0.90 on openSUSE Leap 15.2

On OpenSUSE Leap 15.2 / x86_64 (a glibc 2.26 system): - The wilcard.9 failure reported in https://lists.gnu.org/archive/html/bug-make/2022-10/msg00128.html and discussed in https://lists.gnu.org/archive/html/bug-make/2022-10/msg00158.html is still present. - The output-sync and temp_stdin

Re: GNU Make 4.4.0.90 on Debian 9.1

On Debian 9.1.0 / x86 (a machine with glibc 2.24): - The wilcard.9 failure reported in https://lists.gnu.org/archive/html/bug-make/2022-10/msg00123.html and discussed in https://lists.gnu.org/archive/html/bug-make/2022-10/msg00158.html is still present. - The output-sync and temp_stdin fa

Re: GNU Make 4.4.0.90 on Debian 11.1

On Debian 11.1 / x86_64 (a glibc 2.31 system) I don't see the older test failures from https://lists.gnu.org/archive/html/bug-make/2022-10/msg00124.html any more. But instead I see 4 test failures in the 'features/archives' category. Find the logs attached. makeerror-4.4.0.90-x86_64-pc-linux

Re: GNU Make 4.4.0.90 on CentOS Stream

On CentOS stream, 3 tests fail, in the output-sync category. Find attached the logs: - with gcc: makeerror-4.4.0.90-x86_64-pc-linux-gnu-itaa.tar.gz - with clang: makeerror-4.4.0.90-x86_64-pc-linux-gnu-dzg1.tar.gz It looks similar to what I reported in https://lists.gnu.org/archive/html/bug-ma

GNU make 4.4 on Solaris OpenIndiana

tached the log files tarball. Bruno makeerror-4.4-x86_64-pc-solaris2.11-qha4.tar.gz Description: application/compressed-tar

Re: GNU make 4.3.92 on Solaris 11

URL Deselect AppStream. Select AppStream. Software selection: Base Environment: Workstation Add-ons: Development Tools, Graphical Administration Tools Root password: login: root password: ** Press "Done" twice. User settings: login: bruno password: ** Select

Re: GNU Make 4.3.92 on OpenBSD 6.5

On OpenBSD 6.5, I see 6 test failures. makeerror-x86_64-unknown-openbsd6.5.tar.gz Description: application/compressed-tar

Re: GNU make 4.3.92 on Cygwin

I wrote: > On Cygwin 2.9.0 (64-bit), compilation works fine, but there are 11 test > failures. With GNU make 4.3.92, we're down to 10 test failures. makeerror-x86_64-pc-cygwin2.9.0.tar.gz Description: application/compressed-tar

Re: GNU make 4.3.92 on mingw

I wrote: > On mingw (on Windows 10 in a Cygwin dev environment), compilation works > fine, but there are 91 test failures. With GNU make 4.3.92, this is down to 75 test failures. makeerror-x86_64-w64-mingw.tar.gz Description: application/compressed-tar

Re: GNU make 4.3.92 on GNU/Hurd

Paul Smith wrote: > 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 n

Re: GNU make 4.3.92 on Solaris 11

I wrote: > On Solaris 11.4 / x86_64, in 64-bit mode, the compilation works fine, but > there > are 20 test failures. Likewise in 32-bit mode. > > On Solaris 11 OmniOS, in 64-bit mode, the compilation works fine, but there > are 22 test failures. In 32-bit mode, even 26 test failures. > > On Sola

Re: GNU make 4.3.92 on FreeBSD

I wrote: > On FreeBSD 11 / x86, the compilation works fine but 1 test fails. On the same machine, with GNU make 4.3.92, all tests pass.

Re: GNU make 4.3.92 on openSUSE Leap 15.2

I wrote: > On OpenSUSE Leap 15.2 / x86_64 (a glibc 2.26 system), the compilation works > fine > but 3 tests fail. On the same system, with GNU make 4.3.92, I see only 1 test failure: the wildcard tests. Due to the older glibc. makeerror-x86_64-pc-linux-gnu-opensuse15.2.tar.gz Description: appl

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

Paul Smith 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 > assume that if we ca

Re: GNU make 4.3.92 on Manjaro 17

I wrote: > On Manjaro Linux 17 (a glibc 2.28 system) in 64-bit mode, the compilation > works fine, but there are 2 test failures. With GNU make 4.3.92, all tests pass.

Re: GNU make 4.3.92 on CentOS 8 Stream

I wrote: > On CentOS 8 Stream / x86_64 (a glibc 2.28 system), the compilation works fine, > but the test suite has failures in the 'output-sync' category: > - 3 failures in a build with gcc The same 3 failures still occur with GNU make 4.3.92. makeerror-x86_64-pc-linux-gnu-centos-8-stream.tar.

Re: GNU make 4.3.92 on Debian 11.1

I wrote: > On Debian 11.1 / x86_64 (a glibc 2.31 system) compilation succeeds > but there are 2 test failures. With GNU make 4.3.92, I see all tests pass.

Re: GNU make 4.3.92 on Debian 9.1

Martin Dorey wrote: > I looked into it further and concluded that failure is indeed expected on > Debian 9, where it's a harmless documentation of the legacy $(wildcard) > behavior with dangling symlinks there. GNU make 4.3.92, on the same machine, shows only this one failure: functions/wildcard

Re: GNU make 4.3.91 on Debian 9.1

recursive] Error 1 > make: *** [Makefile:1192: distcheck] Error 1 > > The tar file is named with the host triplet, and all the things I might > want (hopefully!!) are there. It exists in the working directory. Thank you! That should make the next reports by Nelson and me much more useful to you. Bruno

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 on Cygwin

GW shutils from my PATH and get the suite working without them but I > don't want to undertake that for this release. For the Cygwin port, this wouldn't help. For the mingw port, it sounds like Eli already has some patches (or at least he knows which places need to be patched) [1].

[bug #52018] suggestion: test case for glob with dangling symlink

Follow-up Comment #7, bug #52018 (project make): > So Debian Stretch aka 9, with glibc 2.24, fails, where Debian Buster aka 10, with glibc 2.28, passes, meaning that it exhibits the new behavior, where $(wildcard) matches even dangling symlinks. It would be possible for 'make' to not have this te

Re: GNU make 4.3.91 on Debian 9.1

. Assuming what you want is a tarball with config.status `find tests/work -name '*.diff*'` `find tests/work -name '*.diff*' | sed -e 's/\.diff/.log/'` that's what I'm sending now. Bruno [1] https://lists.gnu.org/archive/html/platform-testers/2022-10/msg5.html debian91-failures.tar.gz Description: application/compressed-tar

Re: GNU make 4.3.91 on CentOS 8 Stream

, and so on. In the 'make-4.3.91' directory: time ./configure 7.4 sec time make 5.6 sec Bruno

GNU make 4.3.91 on other platforms

On some platforms, the compilation works fine and all tests pass: - Ubuntu / x86_64 22.04 - macOS 10.13 - NetBSD 9 Bruno

GNU make 4.3.91 on GNU/Hurd

On GNU/Hurd (from 2022), there is one compilation error: depbase=`echo src/arscan.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\ gcc-12 -DHAVE_CONFIG_H -Isrc -I../src -Ilib -I../lib -DLIBDIR=\"/home/bruno/lib\" -DLOCALEDIR=\"/home/bruno/share/locale\" -DINCLUDEDI

GNU make 4.3.91 on mingw

On mingw (on Windows 10 in a Cygwin dev environment), compilation works fine, but there are 91 test failures. mingw-failures.tar.gz Description: application/compressed-tar

GNU make 4.3.91 on Cygwin

On Cygwin 2.9.0 (64-bit), compilation works fine, but there are 11 test failures. cygwin-failures.tar.gz Description: application/compressed-tar

GNU make 4.3.91 on Solaris 11

On Solaris 11.4 / x86_64, in 64-bit mode, the compilation works fine, but there are 20 test failures. Likewise in 32-bit mode. On Solaris 11 OmniOS, in 64-bit mode, the compilation works fine, but there are 22 test failures. In 32-bit mode, even 26 test failures. On Solaris 11 OpenIndiana, in 64-

GNU make 4.3.91 on FreeBSD

On FreeBSD 11 / x86, the compilation works fine but 1 test fails. freebsd11-failures.tar.gz Description: application/compressed-tar

GNU make 4.3.91 on openSUSE Leap 15.2

On OpenSUSE Leap 15.2 / x86_64 (a glibc 2.26 system), the compilation works fine but 3 tests fail. opensuse152-failures.tar.gz Description: application/compressed-tar

GNU make 4.3.91 on Manjaro 17 — bi-arch problem

d -g -O2 -Wl,--export-dynamic -L/home/bruno/prefix32/lib -o make src/ar.o src/arscan.o src/commands.o src/default.o src/dir.o src/expand.o src/file.o src/function.o src/getopt.o src/getopt1.o src/guile.o src/hash.o src/implicit.o src/job.o src/load.o src/loadapi.o src/main.o src/misc.o src/ou

GNU make 4.3.91 on Manjaro 17

On Manjaro Linux 17 (a glibc 2.28 system) in 64-bit mode, the compilation works fine, but there are 2 test failures. manjaro17-failures.tar.gz Description: application/compressed-tar

GNU make 4.3.91 on CentOS 8 Stream

On CentOS 8 Stream / x86_64 (a glibc 2.28 system), the compilation works fine, but the test suite has failures in the 'output-sync' category: - 3 failures in a build with gcc, - 4 failures in a build with clang-15.0.2. centos8s-gcc-failures.tar.gz Description: application/compressed-tar centos

GNU make 4.3.91 on Debian 11.1

On Debian 11.1 / x86_64 (a glibc 2.31 system) compilation succeeds but there are 2 test failures. debian111-failures.tar.gz Description: application/compressed-tar

GNU make 4.3.91 on Debian 9.1

On Debian 9.1.0 / x86 (a machine with glibc 2.24), the compilation succeeds but 3 tests fail. debian91-failures.tar.gz Description: application/compressed-tar

Re: Missing [/usr/local]/var/lib and [/usr/local]/tmp

root wheel 11 Feb 10 2015 /etc -> private/etc > lrwxr-xr-x@ 1 root wheel 11 Feb 10 2015 /tmp -> private/tmp /tmp is world-writable, of course: $ ls -lLd /etc /tmp drwxr-xr-x@ 124 root wheel 3968 27 Jun 01:25 /etc drwxrwxrwt@ 8 root wheel 256 18 Jul 14:38 /tmp Bruno

Re: Missing [/usr/local]/var/lib and [/usr/local]/tmp

y has not enough room. 2) It creates one more directory that requires either regular attention (so that it does not fill up over time) or a fascist policy of the kind "let's remove the contents of this directory regularly". Suggestion: Use ${TMPDIR-/tmp} instead. See also

Re: "make -jN" requires mechanical changes to a Makefile [SOLVED]

e copy3 > install -c -m 644 Makefile copy4 > === Fails (D) and (E). => Not a solution to the problem. Bruno

Re: "make -jN" requires mechanical changes to a Makefile [SOLVED]

to be adjusted to include this stamp file. I'll use the rule with a phony target and 'test ... -ot ...', unless you find a problem with it (other than the potential portability problem redarding 'test'). Bruno

Re: "make -jN" requires mechanical changes to a Makefile [SOLVED]

> === > all : copy1 copy2 copy3 copy4 > > copy1: Makefile > { test -f copy1 && test ! copy1 -ot Makefile; } || { rm -f copy4; > $(MAKE) copies; } > copy2: copy1 > { test -f copy2 && test ! copy2 -ot copy1; } || { rm -f copy4; $(MAKE) > copies;

Re: "make -jN" requires mechanical changes to a Makefile [SOLVED]

ils all the requirements. Can we use 'test FILE1 -ot FILE2'? - POSIX 'test' does not support this option. See <https://pubs.opengroup.org/onlinepubs/9699919799/utilities/test.html> - But all test programs in all current operating systems (Linux, macOS, FreeBSD, NetBSD, OpenBSD, AIX, Solaris, Haiku, Minix, Cygwin, even Busybox) support it. Except for /bin/sh on Solaris 10 — but in packages that use the GNU Build System, Autoconf sets SHELL = @CONFIG_SHELL@ = /bin/bash on such systems. Bruno

Re: make-4.3: wildcard test #9 fails

GNU make ships a copy of glob.c from 1999 :-( Bruno [1] https://www.gnu.org/software/gnulib/manual/html_node/glob.html

make-4.3: wildcard test #9 fails

global_setlist 00637080 b global_variable_set U globfree@@GLIBC_2.2.5 U glob@@GLIBC_2.2.5 00424760 T init_hash_global_variable_set Bruno

Re: "make -jN" requires mechanical changes to a Makefile

rely on it in > parallel make. The sequence of lines of the recipe of a rule gets executed in order, even in parallel make, no? Bruno ___ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make

Re: "make -jN" requires mechanical changes to a Makefile

'make' invocation will fail somewhere when it references copy2...copy4. Bruno ___ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make

Re: "make -jN" requires mechanical changes to a Makefile

for multiple targets on the same rule. You mentioned splitting the rule into one rule per file. But bison does not work this way; it really produces two files at once. And for other rules I mentioned Automake limitations. Parallel make is of growing importance, because Debian now uses parallel b

Re: "make -jN" requires mechanical changes to a Makefile

akefile copy3 install -c -m 644 Makefile copy4 copy2 copy3 copy4: copy1 === Bruno ___ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make

Re: "make -jN" requires mechanical changes to a Makefile

s might be a better compromise, when only few Makefiles have problems with parallel make. Whereas the snippet I showed turns it off for an entire package (when placed in the top-level Makefile). Thanks for the suggestion. Bruno ___ Bug-make mailing li

  1   2   >