Simply did ./configure. It’s an Intel Mac. Compiler seems to be clang. Doing a clean build shows a few warnings when compiling.
On Thu, 22 Sep 2022 at 20:21, Paul Smith <psm...@gnu.org> wrote: > On Thu, 2022-09-22 at 14:13 +0100, John Graham-Cumming wrote: > > $ sw_vers > > ProductName: macOS > > ProductVersion: 12.6 > > BuildVersion: 21G115 > > > > $ ./make -v > > GNU Make 4.3.90 > > > > $ cat Makefile > > $(info $(wildcard foo)) > > > > $ rm -f foo > > $ ./make > > zsh: segmentation fault ./make > > Hm, I cannot reproduce this. Can you think of anything else "non- > standard" about this system? Did you use any special arguments to > configure? Is this an Intel-based mac or an M1 or an M2? > > My attempt: > > % sw_vers > ProductName: macOS > ProductVersion: 12.4 > BuildVersion: 21F79 > > % ../make -v | head -n1 > GNU Make 4.3.90 > > % rm -f foo > % ../make > > make: *** No targets. Stop. > > > Thread 2 received signal SIGSEGV, Segmentation fault. > > 0x000000010001e7fe in parse_file_seq (stringp=<optimized out>, > > stringp@entry=0x7ff7bfefe868, size=size@entry=16, > > stopmap=stopmap@entry=1, prefix=prefix@entry=0x0, > > flags=flags@entry=25) at src/read.c:3529 > > 3529 NEWELT (concat (2, prefix, nlist[i])); > > Thanks. Can you check the value of "i" and the contents of the "nlist" > array here? > > I'm also curious whether the configure step decides to use the system > glob and fnmatch. It should not, because GNU make expects the GNU > version of glob, so it should build its own. You can see if these > files exist in the build tree after make is built: > > ./lib/libgnu_a-glob.o > ./lib/libgnu_a-fnmatch.o > >
