On Thu, 2022-09-22 at 20:34 +0100, John Graham-Cumming wrote: > Simply did ./configure. It’s an Intel Mac. Compiler seems to be > clang. > > Doing a clean build shows a few warnings when compiling.
Those are not a problem. In addition to answers to the questions I asked below, can you send the output of "ls -al" in the directory where you're running make? Maybe there's some other file in that directory which is causing the glob to return something weird. > > > 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
