Re: [PATCH] Use UTF-8 active code page for Windows host.

On Tue, 2023-04-11 at 15:29 +0300, Eli Zaretskii wrote: > I agree with the list.  As for Basic.mk, we can forget about it from > my POV.  Paul should make the call, but from my POV that file was > unmaintained and therefore unsupported. Why do we think it's unmaintained / unsupported? It worked t

Re: Build gnu cmake sources

On Mon, 2023-04-10 at 01:51 +0300, Дмитрий Мозулёв wrote: > I would like to build your GNU Make utility from source for 5 > platforms: Windows x64, Linux x64/arm64 and macOS x64/arm64. > Unfortunately, I'm having trouble. Hi; please use the bug-make@gnu.org mailing list for questions about buildin

Re: [PATCH] Use UTF-8 active code page for Windows host.

On Fri, 2023-04-07 at 08:29 -0400, Paul Smith wrote: > > Also, I'm still waiting for Paul to approve the changes to Posix > > configury part of your patch. > > Sorry I will make every effort to get to it today. The configure part looks OK to me. This change to Make

Re: [PATCH] Use UTF-8 active code page for Windows host.

On Thu, 2023-04-06 at 22:32 +0300, Eli Zaretskii wrote: > > From: Costas Argyris > > Date: Thu, 6 Apr 2023 22:04:48 +0300 > > Cc: bug-make@gnu.org, Paul Smith > > > > Hi and sorry to bother you again. > > > > I haven't received any response so >

The --warn / .WARNINGS feature

I pushed my changes to implement the --warn / .WARNINGS feature. I hope people find them useful. As of now there are only 3 possible warnings, but I will be looking through other warnings that might be useful to control. There is one major caveat to this: currently it's not possible to set .WARN

Re: `make check -j` fails when building GNU Make from source

On Mon, 2023-04-03 at 14:36 +0200, Alejandro Colomar wrote: > -  Being part of the make targets, it would enable running them in >    parallel, taking around 1/4th the time it takes now. Up until this morning this could not work because all the tests run in the same directory and they create tempo

Re: `make check -j` fails when building GNU Make from source

On Sun, 2023-04-02 at 18:14 +0200, Alejandro Colomar wrote: > I wonder if you could use the Makefile to run the tests, rather > than calling a script from a .PHONY target that runs them all the > time.  Why not run them only once?  You can touch empty files > when a test succeeds to make make(1) ha

Enhancements to the regression tests

Hi all; I reworked the behavior of the regression tests in the following way: Each test file has a separate subdirectory created for it in work/ and before the test starts the driver will make that the current working directory, then switch back again after the test completes. The idea is to prev

Re: `make check -j` fails when building GNU Make from source

On Sun, 2023-04-02 at 16:13 +0200, Alejandro Colomar wrote: > I can reproduce it by running `make check`, interrupting it > at this specific point, and then running again `make check` > (no -j needed): This is a known limitation with the test suite.

Re: `make check -j` fails when building GNU Make from source

On Sun, 2023-04-02 at 14:52 +0200, Alejandro Colomar wrote: > If I build make from source and run the checks in parallel, some > fail. Is this expected, or is it a bug in the Makefile? The test suite is invoked as a single target, so there's no way that enabling parallelism could impact it. Also

Re: Quotes Bug

On Thu, 2023-03-30 at 22:05 +0300, Eda Çelik wrote: > Hello, I'm a master student at Çanakkale Onsekiz Mart University in > Turkey. I'm trying to use rvfit code but this code written GNU data > language. I installed GDL but rvfit code is not working. Code and > error by: > GDL> > rvfit,configfile='

Re: [PATCH] Use UTF-8 active code page for Windows host.

I apologize for being incommunicado: for the last week I've been fighting the mother of all head colds. The only good thing I can say about it is that it was not COVID. I'm sort of back on my feet. On Sat, 2023-03-25 at 23:12 +, Costas Argyris wrote: > and then from README.W32 -> Building w

Re: [PATCH] Use UTF-8 active code page for Windows host.

On Tue, 2023-03-21 at 12:52 +, Costas Argyris wrote: > When trying from git, which was my first attempt, I was getting > compilation warnings which were turning themselves into errors, > so I never managed to build. > > When I used the sources extracted from the tarball though, this > simply w

Re: [PATCH] Use UTF-8 active code page for Windows host.

On Sun, 2023-03-19 at 16:47 +0200, Eli Zaretskii wrote: > If we add tests for this feature (and I agree it's desirable), we > should generate the files with non-ASCII names for those tests as > part of the test script, not having them ready in the repository and > the tarball. Agreed for sure; plu

Re: [PATCH] Use UTF-8 active code page for Windows host.

On Sat, 2023-03-18 at 16:37 +, Costas Argyris wrote: > The attached patch incorporates the UTF-8 manifest into the build > process of GNU Make when hosted on Windows, and forces the > built executable to use UTF-8 as its active code page, solving all > problems shown above because this has a gl

Re: [PATCH] Use UTF-8 active code page for Windows host.

On Sun, 2023-03-19 at 13:42 +, Costas Argyris wrote: > I cross-compiled Make for Windows using gcc (mingw-w64) and the > autoconf + automake + configure + make approach, so it clearly worked > for me, but I didn't imagine that this wasn't the standard way to > build for Windows host. There is

Re: subst: Mention how to deal with a FROM that has commas in it

On Sat, 2023-03-18 at 16:41 +0800, Dan Jacobson wrote: > Or mention that there is no way to deal with it. https://www.gnu.org/software/make/manual/html_node/Syntax-of-Functions.html Cheers!

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

On Sun, 2023-03-12 at 11:25 -0400, Ken Brown wrote: > > If I'm right, the solution would seem to be to disable the use of > > pselect on Cygwin when the jobserver is using a fifo.  I'll try > > that on a local build of make and see if I can still reproduce the > > problem. > > Never mind.  My spe

Re: make -t and directories

On Sat, 2023-03-11 at 01:54 +0100, Alejandro Colomar wrote: > Let's say I have a build tree that has directories which are created > during build.  The build system has some linters in a `lint` target, > which touches files when it succeeds.  When I want to lint only a > specific file, it's interes

Re: No progress output when make 4.4.1 builds Linux 4.19 and earlier

On Wed, 2023-03-08 at 15:53 +, David Laight wrote: > Adding a $(filter-out --%,...) should help with old makes: Yes that's what is there. See the link to the commit I posted. I just couldn't remember why it was necessary to treat things differently between different versions. Dmitry reminde

Re: No progress output when make 4.4.1 builds Linux 4.19 and earlier

On Wed, 2023-03-08 at 09:39 -0500, Dmitry Goncharov wrote: > On Wed, Mar 8, 2023 at 8:58 AM Paul Smith wrote: > > Does anyone know why this commit is using a make version > > comparison? > > Kernel build system is expected to work with gnu make-3.82. > make-3.82 puts l

Re: No progress output when make 4.4.1 builds Linux 4.19 and earlier

On Wed, 2023-03-08 at 15:31 +0100, Greg KH wrote: > > Does anyone know why this commit is using a make version > > comparison? That seems totally unnecessary to me; am I forgetting > > something?  As far as I remember, > > > > silence := $(findstring s,$(firstword -$(MAKEFLAGS))) > > > > ha

Re: Segmentation fault with make-4.3+ on MacOS with 'wildcard'

On Tue, 2023-03-07 at 20:18 -0600, Satish Balay wrote: > Ok - try a build without guile: > > balay@ypro make-4.4.1 % ./configure --without-guile && make -j8 > > Now it works! : > > balay@ypro ~ % ./make-4.4.1/make > CONFIGDIR: /Users/balay/testdir/share/config > balay@ypro ~ % > > > So there

Re: No progress output when make 4.4.1 builds Linux 4.19 and earlier

On Wed, 2023-03-08 at 08:12 -0500, Dmitry Goncharov wrote: > > > Is this an intentional breakage from the 'make' side? > No it is not an intentional breakage. > This is a fix for https://savannah.gnu.org/bugs/?63347. Just to note, it was possible to run into this problem with earlier versions of G

Re: Segmentation fault with make-4.3+ on MacOS with 'wildcard'

On Wed, 2023-03-08 at 00:13 +, Martin Dorey wrote: > ... and it's sliced off half the gl_pathv pointer through calling an > implementation of glob that wasn't compatible with the declaration of > the structure that Make is using? Well, since this is a MacOS system we SHOULD be using our own im

Re: Segmentation fault with make-4.3+ on MacOS with 'wildcard'

On Tue, 2023-03-07 at 17:54 -0600, Satish Balay wrote: > (lldb) p nlist[i] > error: Couldn't apply expression side effects : Couldn't > dematerialize a result variable: couldn't read its memory Boy I really really dislike lldb as a tool. Does it work to install gdb with brew instead? Not sure if

Re: Segmentation fault with make-4.3+ on MacOS with 'wildcard'

On Tue, 2023-03-07 at 17:38 -0600, Satish Balay via Bug reports and discussion for GNU make wrote: > -> 3535   NEWELT (concat (2, prefix, nlist[i])); >    3536  >    3537   if (globme) >    3538 globfree (&gl); > Target 0: (make) stopped. > (lldb) bt > * thread #1, queue = 'com.

Re: whitespaces preceding backslash sometimes removed in POSIX mode

On Sun, 2023-03-05 at 23:09 +0100, Arkadiusz Drabczyk wrote: > "If the @code{.POSIX} special target is defined then > backslash/newline handling is modified slightly to conform to > POSIX.2: first, whitespace preceding a backslash is not removed and > second, consecutive backslash/newlines are not

Re: 4.4.1 breaks recursive invocation with --print-directory [when adding to MAKEFLAGS]

On Tue, 2023-02-28 at 19:02 -0600, Satish Balay via Bug reports and discussion for GNU make wrote: > This usage works with make-4.4 [and older versions] - but not 4.4.1 > > balay@p1 /home/balay/tmp > $ cat makefile > all: > @MAKEFLAGS="-j1 ${MAKEFLAGS}" ${MAKE} -f makefile hello > hello: >

Re: 4.4.1 breaks recursive invocation with --print-directory [when adding to MAKEFLAGS]

On Wed, 2023-03-01 at 13:05 -0600, Satish Balay wrote: > Perhaps my minimal test code is not an exact representation. However > this usage does work in our code-base. > > > > > > [balay@pj01 petsc]$ make --version |head -1 > GNU Make 4.3 > [balay@pj01 petsc]$ grep ^MAKE_NP configure.log > MAKE_N

Re: 4.4.1 breaks recursive invocation with --print-directory [when adding to MAKEFLAGS]

On Tue, 2023-02-28 at 22:34 -0600, Satish Balay via Bug reports and discussion for GNU make wrote: > And the reason we use the order '-j8 ${MAKEFLAGS}' is so that we have > the following behavior': > > - invoking 'make' defaults to using a default of '-j8' > - invoking 'make -j4' gives: '-j8 -j4'

GNU Make 4.4.1 released!

GNU make is a tool which controls the generation of executables and other non-source files of a program from the program's source files. You can learn more at: https://www.gnu.org/software/make/ --

Re: meaning of # in the variable used as a list of targets

On Sun, 2023-02-26 at 19:19 +0100, Arkadiusz Drabczyk wrote: > In the manual it says: > > "Within a @code{define} directive, comments are not ignored during > the definition of the variable, but rather kept intact in the value > of the variable.  When the variable is expanded they will either be >

Re: $(wildcard ...*/) and symlinks

On Fri, 2023-02-24 at 10:05 -0500, Dmitry Goncharov wrote: > On Fri, Feb 24, 2023 at 6:55 AM Frank Heckenbach > wrote: > ... > > So "*/" ignores the symlink to a file as expected, but "l*/" does > > return it, likewise "*/*/" which doesn't make much sense to me. > > There is a known bug in glibc

Re: VPATH question

On Fri, 2023-02-24 at 17:40 +0100, Gisle Vanem wrote: > Paul Smith wrote: > > If you use "-d" you'll get the info you want: > > > > No implicit rule found for 'default'. > > Considering target file 'lib'. > > Fin

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

On Thu, 2023-02-23 at 16:17 -0500, Ken Brown wrote: > Sorry, I spoke too soon.  I just went back to my original use case, > in which I used the TeX Live "Build" script instead of directly > invoking make, and I again got the jobserver warning. Thanks for the info. TL;DR: this is not an error in m

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

On Thu, 2023-02-23 at 16:17 -0500, Ken Brown wrote: > I'm attaching that script so you can see exactly how "make" is > invoked in a subshell.  I'm also attaching my build log up to the > point of the warning and the Makefile in the ft-build directory in > which the warning occurred.  I've previousl

Re: VPATH question

On Fri, 2023-02-24 at 08:44 +0100, Gisle Vanem wrote: > So I want to create a './lib' directory in > 'Current Directory', but gnumake won't do it > since there is a 'lib' under 'apps'. Output: >    gnumake: Nothing to be done for 'default'. > > Why doesn't it understand the meaning of '.'? It doe

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

On Tue, 2023-02-21 at 13:11 -0500, Ken Brown wrote: > I think you're on the right track.  I got through 'make -j13 check' > without the jobserver warning. w00t! Thanks for the help. A full fix should be in 4.4.1 which I hope to release this week or weekend.

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

On Tue, 2023-02-21 at 10:36 -0500, Paul Smith wrote: > But, I think I might have found the bug.  If I'm right, it's a doozy! > But, as you mentioned it's not widespread because it only affects > pipe jobservers.  I'm glad 4.4.1 is almost ready to go.  I'll try to

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

On Tue, 2023-02-21 at 10:12 -0500, Ken Brown wrote: > > There will likely be a lot of output. > > Here it is. Oops I got the rule wrong for the set -x. But, I think I might have found the bug. If I'm right, it's a doozy! But, as you mentioned it's not widespread because it only affects pipe jo

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

On Tue, 2023-02-21 at 08:35 -0500, Ken Brown wrote: > make  check-TESTS > make[4]: Entering directory > '/home/kbrown/src/texlive/test.x86_64/Work/texk/kpathsea' > make[5]: Entering directory > '/home/kbrown/src/texlive/test.x86_64/Work/texk/kpathsea' OK, I see the rule that generates the [5] re

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

On Tue, 2023-02-21 at 08:35 -0500, Ken Brown wrote: > On 2/21/2023 3:54 AM, Ken Brown wrote: > > On 2/21/2023 12:27 AM, Paul Smith wrote: > > > Just to note, I do run the regression test suite with the > > > equivalent of "jobserver-style=pipe" (basically I

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

On Mon, 2023-02-20 at 20:21 -0500, Ken Brown wrote: > Parallel make is still not working reliably.  I've just discovered > that my TeX Live build logs have several occurrences of the following > warning: > >    jobserver unavailable: using -j1.  Add '+' to parent make rule. > > This has been goin

Re: Handling references to invalid variables

On Mon, 2023-02-20 at 14:20 -0500, rsbec...@nexbridge.com wrote: > I think you need to be able to return to a compatible mode for some > users. Having an option like --undefined-variables=warn or -- > undefined-variables=error (the default) or --undefined- > variables=ignore would be prudent. Hm.

Handling references to invalid variables

In the next major release (not the upcoming 4.4.1 release but the one after that) I plan to implement notifying users of invalid variable references; for example variable names containing whitespace. So, a makefile like this for example: all: ; echo $(cat foo) will notify the user about the il

Re: GNU Make 4.4.0.91 on Cygwin

On Mon, 2023-02-20 at 14:47 +0200, Eli Zaretskii wrote: > How do you conclude that this "works on Windows"? Before I make a release I test on various systems and the regression test suite must pass with no failures. One of the systems I test on is Windows, so if a release comes out and a test is

Re: GNU Make 4.4.0.91 on Cygwin

On Sun, 2023-02-19 at 17:20 -0500, Ken Brown wrote: > > Hm.  This is a test of this: > > https://savannah.gnu.org/bugs/index.php?57674 > > > > which explicitly removes PATH from the environment completely.  It > > should use a default PATH, which should mean "echo" works even so.  > > I'm not real

Re: GNU Make 4.4.0.91 on openSUSE Leap 15.2

On Sun, 2023-02-19 at 22:15 +0100, Bruno Haible wrote: > gnulib/m4/glob.m4 contains a test for this bug: Thanks! I adapted this for GNU make and hopefully it will correctly detect this issue. # Check the system to see if it provides GNU glob. If not, use our # local version. Also avoid versio

Re: GNU Make 4.4.0.91 on openSUSE Leap 15.2

On Sun, 2023-02-19 at 21:23 +0100, Bruno Haible wrote: > - The wildcard.9 failure (well-known), 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". Howe

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

On Sun, 2023-02-19 at 21:53 +0100, Bruno Haible wrote: > Somehow your fix for archives.12 and archives.13 does not work > in this environment. I'm attaching the config.status. That test was accidentally running with 4.4.0.90 still: # /export/home/bruno/make-4.4.0.90/build-32/tests/scripts/feat

Re: GNU Make 4.4.0.91 on GNU/Hurd

On Sun, 2023-02-19 at 21:46 +0100, Bruno Haible wrote: > > You'll likely see this same issue with the 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 The patch below shoul

Re: GNU Make 4.4.0.91 on AIX 7.2

On Sun, 2023-02-19 at 21:20 +0100, Bruno Haible wrote: > 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. Hm. Maybe the AIX filesystem has issues with subsecond

Re: GNU Make 4.4.0.91 on AIX 7.2

On Sun, 2023-02-19 at 20:55 +0100, Bruno Haible wrote: >   - 1 from category 'features/include'. Hm. I don't know what the problem is here; clearly we shouldn't be printing this line twice: *** work/features/include.base.37 Sun Feb 19 19:38:21 2023 --- work/features/include.log.37S

Re: GNU Make 4.4.0.91 on Cygwin

On Sun, 2023-02-19 at 20:32 +0100, Bruno Haible wrote: > All "Device or resource busy" failures are gone. Only the 1 failure > in category 'misc/general4' is still present. Hm. This is a test of this: https://savannah.gnu.org/bugs/index.php?57674 which explicitly removes PATH from the environmen

Re: GNU Make 4.4.0.91 on GNU/Hurd

On Sun, 2023-02-19 at 20:25 +0100, Bruno Haible wrote: > 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". Argh, I forgot to change th

GNU Make 4.4.0.91 release candidate available

GNU make is a tool which controls the generation of executables and other non-source files of a program from the program's source files. You can learn more at: https://www.gnu.org/software/make/ --

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

On Sun, 2023-02-19 at 09:17 -0500, Ken Brown wrote: > > So I'm not sure where to go from here on Cygwin.  Should I force > > Cygwin builds to use the "pipe" jobserver, as I've done for > > GNU/Hurd? > > My preference would be for you to provide a configure option, which > defaults to "pipe" on Cy

Re: pattern rules with multiple targets producing intermediate files

On Tue, 2023-02-07 at 14:51 +0100, Jan Beulich wrote: > while something has changed from 4.3 to 4.4 in the dealing with > intermediate files, the example Makefile below still doesn't work > as expected. There are two pairs of *.[ch] files generated, each by > their respective rule. Each of the *.o

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

On Wed, 2023-02-15 at 13:57 -0500, Ken Brown wrote: > One thing to keep in mind here is that your tests on Cygwin were done > on Cygwin 2.9.0, in which FIFOs were very poorly supported.  For > example, a FIFO couldn't have multiple readers or writers.  If > GNU/Hurd has similar limitations, that co

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

On Sun, 2023-02-19 at 12:44 +0100, Bruno Haible wrote: >   - 4 failures in category 'features/jobserver' >   - 2 failure in category 'functions/shell' I looked at the error logging you sent, and I think these are just a result of an incomplete/incorrect setting of the default value to "pipe". Hop

Re: GNU Make 4.4.0.90 on GNU/Hurd

On Sun, 2023-02-19 at 12:34 +0100, Bruno Haible wrote: > In other words, on GNU/Hurd, one should use 'glob' and 'globfree', > not 'glob64' and 'globfree64'. Even though the libc is glibc and > support for large files (> 2 GiB) is enabled. > > The culprit seems to be the glob.in.h file. As far as

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

On Wed, 2023-02-15 at 13:57 -0500, Ken Brown wrote: > If I simply run 'make -j13 world' without using the Build script, it > doesn't hang.  I don't know if this provides any clue as to where the > problem is. Speaking for myself, it doesn't give me any clues. I don't see why it should matter. Bu

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

On Wed, 2023-02-15 at 19:34 +0100, Bruno Haible wrote: > > I may be misremembering but I thought that you had tried forcing > > the pipe jobserver option on GNU/Hurd and it didn't help. > > This must be a misunderstanding. I never said that. I don't even know > how to do this, within the framework

Re: CentOS Stream installation

On Sat, 2023-02-18 at 16:55 -0500, Paul Smith wrote: > On Sun, 2023-02-05 at 23:46 +0100, Bruno Haible wrote: > > Paul Smith wrote: > > > How many CPUs did you give to the VM?  It shouldn't matter since > > > we're doing multiprocessing here but... maybe...?  I

Re: CentOS Stream installation

On Sun, 2023-02-05 at 23:46 +0100, Bruno Haible wrote: > Paul Smith wrote: > > How many CPUs did you give to the VM?  It shouldn't matter since > > we're doing multiprocessing here but... maybe...?  I was using 4G > > RAM and 4 CPUs in my guest. > > I

Re: is this a typo on your manual?

Please reply to the list, not privately, then everyone can help and/or see the answer. On Wed, 2023-02-15 at 18:19 +, Shailan Patel wrote: > Hello im referring to this > chapter https://www.gnu.org/software/make/manual/make.html#Secondary- > Expansion  > > and im referring to this example he

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

On Tue, 2023-02-14 at 01:04 +0100, Bruno Haible wrote: > And possibly also on GNU/Hurd. Cf. > https://lists.gnu.org/archive/html/bug-make/2023-01/msg00107.html I may be misremembering but I thought that you had tried forcing the pipe jobserver option on GNU/Hurd and it didn't help.

Re: is this a typo on your manual?

On Wed, 2023-02-15 at 05:10 +, Shailan Patel wrote: > do you know whether the third prerequisite list here > https://prnt.sc/_l1Jg2gkV4v_  expands to "foo.1 bar.1 foo.2 bar.2 > foo.1 foo.1 bar.1 foo.1 bar.1" https://pastebin.com/DFr9Athi ? Hi; Please choose just one mailing list to ask on sin

Re: bug

On Tue, 2023-02-14 at 23:22 +0100, Viktor Cada wrote: > I am new to Debian and when installing apache2 i got these error > codes: > > collect2: error: ld returned 1 exit status I suppose when you say "installing" apache2 you really mean "building" apache2. This error means the link command that

Re: OpenIndiana installation

On Sun, 2023-02-05 at 18:04 +0100, Bruno Haible wrote: > Paul Smith wrote: > > I tried to install Solaris 11 OpenIndiana from an OVA file in > > VirtualBox and I was able to get it to install but couldn't figure > > out how to install a C compiler on it. > > Y

Re: CentOS Stream installation

On Sun, 2023-02-05 at 17:54 +0100, Bruno Haible wrote: > I am testing CentOS 8 stream. Find my personal installation notes > below. That's more or less what I did except I did manage to install guest additions. However, the problem did not reproduce for me on CentOS 8. How many CPUs did you give

Re: GNU Make 4.4.0.90 on CentOS Stream

On Sun, 2023-01-15 at 11:47 +0100, Bruno Haible wrote: > On CentOS stream, 3 tests fail, in the output-sync category. I have been struggling to reproduce these output-sync failures for a few weeks now and I'm about to give up in frustration. I can't even get past the first step. It would be good

Re: A spell error in pdf manual

On Fri, 2023-02-03 at 21:51 +0800, 毛欣宇 wrote: > The second paragraph begins "If an expression matches multiple files > than the results will be sorted",it should be "then" rather than > "than"? Fixed; thank you!

Re: GNU/Hurd installation

On Mon, 2023-01-16 at 00:01 -0500, Paul Smith wrote: > I just got a new GNU/Linux laptop for working at home: it has the > very latest Intel i9 CPU, NVMe disk, and all the trimmings.  It's > running Ubuntu 22.04.  Perhaps this is leading to issues. > > I have a GNU/Linux lapto

Re: Misleading "--debug=w" output for phony target

On Wed, 2023-01-18 at 15:22 +0100, Frank Heckenbach wrote: > > > Of course, make should remake a, but not due to b but because > > > it's phony. > > > > Please provide info about what version of GNU make you're using. > > This was 4.4. I now see it's fixed in the latest RC, so forget about > it.

Re: Misleading "--debug=w" output for phony target

On Wed, 2023-01-18 at 14:45 +0100, Frank Heckenbach wrote: > % cat Makefile > .PHONY: a > a: b; : > % touch b; touch a; make --debug=w > Makefile:2: update target 'a' due to: b > : > > Of course, make should remake a, but not due to b but because it's > phony. Please provide info about what versi

Re: [PATCH] Check .exe as well when a target does not exist on OS/2

On Tue, 2023-01-17 at 01:38 +0900, KO Myung-Hun wrote: > What I meant is checking the existence of a rule for a target not a > real file built for a target. But how do you check for a "rule for a target"? What if the pattern rule is "%e" not "%.exe"? That will still match of course. Or "%xe" or

Re: [PATCH] Check .exe as well when a target does not exist on OS/2

On Mon, 2023-01-16 at 22:14 +0900, KO Myung-Hun wrote: > > But this does not seem like an easy thing to accomplish, at all.  > > What if there is a "%.exe" pattern rule, not an explicit rule for > > "foo.exe"? > > I think, it's possible to do so by finding a target as GNU Make finds > dependencies

Re: GNU/Hurd installation

On Sun, 2023-01-15 at 22:47 +0100, Bruno Haible wrote: > Unfortunately, this magic pixie dust depends on your CPU model, > UEFI/BIOS settings, Linux host kernel version, and VirtualBox > version. I just got a new GNU/Linux laptop for working at home: it has the very latest Intel i9 CPU, NVMe disk,

Re: GNU/Hurd installation

On Sun, 2023-01-15 at 21:31 +0100, Bruno Haible wrote: > In my instructions for GNU/Hurd in 2020 I had noted >   Disable 'Nested paging', otherwise it DOES NOT BOOT! > > So, maybe it's worth looking at the main parameters of the VirtualBox VM: >   - General: Operating System: Other/Unknown >   - S

Re: GNU/Hurd installation

On Sun, 2023-01-15 at 15:06 -0500, Paul Smith wrote: > I did get the "current" version, which was created on 2022-10-30. > Maybe that one is broken?  I'll try downloading the 2022-08-24 > version you reference above and see if that makes a difference. It did not mat

Re: GNU/Hurd installation

On Sun, 2023-01-15 at 19:24 +0100, Bruno Haible wrote: > Download > https://cdimage.debian.org/cdimage/ports/latest/hurd-i386/20220824/debian-sid-hurd-i386-DVD-1.iso I did get the "current" version, which was created on 2022-10-30. Maybe that one is broken? I'll try downloading the 2022-08-24 ve

Re: GNU/Hurd installation

On Sun, 2023-01-15 at 19:24 +0100, Bruno Haible wrote: > Pseudo-graphical install. I've tried a couple of times, using different instructions (VirtualBox and vanilla KVM) and every time when it starts to boot the first time (after selecting this install) it prints: ... module 0: initrd $(ramd

Re: GNU Make 4.4.0.90 on GNU/Hurd

On Sun, 2023-01-15 at 15:49 +0100, Bruno Haible wrote: >   - 5 failures in category 'features/jobserver' >   - 2 failures in category 'features/parallelism' >   - 1 failure in category 'features/recursion' >   - 1 failure in category 'functions/shell' It seems these are the same errors from the pr

Re: GNU Make 4.4.0.90 on Debian 11.1

On Sun, 2023-01-15 at 09:44 -0500, Paul Smith wrote: > We'll have to override these settings in that test. OK I made a change that will hopefully address this.

Re: [PATCH] Check .exe as well when a target does not exist on OS/2

On Mon, 2023-01-16 at 00:15 +0900, KO Myung-Hun wrote: > Then, this patch is acceptable? Or MSYS is a special case ? I don't think this patch is a good idea. I said in my initial email: > I don't think I like this change. I understand its usefulness but in > general make never tries to manipula

Re: GNU Make 4.4.0.90 on macOS 12

On Sun, 2023-01-15 at 15:53 +0100, Bruno Haible wrote: > On macOS 12.5 / arm64 I see two test failures: >   - output-sync >   - temp_stdin Thanks, I fixed this one.

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

On Sun, 2023-01-15 at 14:58 +0100, Bruno Haible wrote: > 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 attache

Re: GNU Make 4.4.0.90 on Debian 11.1

On Sun, 2023-01-15 at 09:35 -0500, Paul Smith wrote: > On Sun, 2023-01-15 at 15:33 +0100, Bruno Haible wrote: > > In this test you have the lines > > > >   # Fallback if configure did not find AR > >   my $ar = get_config('AR') || 'ar'; > &g

Re: GNU Make 4.4.0.90 on Debian 11.1

On Sun, 2023-01-15 at 15:33 +0100, Bruno Haible wrote: > In this test you have the lines > >   # Fallback if configure did not find AR >   my $ar = get_config('AR') || 'ar'; > > Why not do the same for CC? > >   my $cc = get_config('CC') || 'cc'; Yes, that's how it's done in other tests. I'll

Re: GNU Make 4.4.0.90 on Debian 9.1

On Sun, 2023-01-15 at 14:52 +0100, Bruno Haible wrote: > - 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. This is due to bugs in

Re: GNU Make 4.4.0.90 on Debian 11.1

On Sun, 2023-01-15 at 14:36 +0100, Bruno Haible wrote: > But instead I see 4 test failures in the 'features/archives' > category. These are because: ! /bin/sh: 1: cc: not found Why is there no C compiler on this system? Or is the problem that it's not on the PATH for some reason?

Re: GNU Make 4.4.0.90 release candidate available

On Sat, 2023-01-14 at 17:10 -0500, Paul Smith wrote:    > >     GNU make is a tool which controls the generation of executables and >     other non-source files of a program from the program's source files. > &g

GNU Make 4.4.0.90 release candidate available

GNU make is a tool which controls the generation of executables and other non-source files of a program from the program's source files. You can learn more at: https://www.gnu.org/software/make/ --

Re: [PATCH] Check .exe as well when a target does not exist on OS/2

On Fri, 2023-01-13 at 22:27 +0900, KO Myung-Hun wrote: > This pattern is usually used on UNIX. However, on OS/2, gcc creates > foo.exe not foo when an extension is not present, and Make check foo > only. Therefore Make tries to build foo whenever called. I don't think I like this change. I unders

Re: [PATCH 0/8] Fix compilation on OS/2

On Sun, 2022-11-20 at 23:42 +0900, KO Myung-Hun wrote: > These patches fix compilation on OS/2. I have applied some of these patches as-is, and modified others, but I believe all the changes needed have been pushed to Git.

Re: GNUmake v4.4 port on Solaris with gcc 9.5.0

On Thu, 2022-11-03 at 06:57 +0100, Christian Jullien wrote: > Here is the correct one for make v4.4 on Solaris 10 with gcc 9.5.0: > > gcc -c -o libgnu_a-concat-filename.o concat-filename.c > concat-filename.c: In function 'concatenated_filename': > concat-filename.c:69:7: warning: implicit declara

Re: [bug #61763] [PATCH] glob: Do not use realloc wrapper on FreeBSD

On Mon, 2023-01-02 at 10:47 -0500, Dmitry Goncharov wrote: > On Mon, Jan 2, 2023 at 9:50 AM Paul D. Smith > wrote: > > I decided to own this glob implementation > > Paul, do you mean that you decided to maintain glob impl in make? > If yes, do you still want to link against glibc impl, when avail

Re: Documentation Typo

On Sun, 2023-01-01 at 18:39 -0800, Vafilor wrote: > so just changing the second `of` to be `if`.  I made this fix, thanks for reporting!

<    1   2   3   4   5   6   7   8   9   10   >