[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: fnmatch-gnu fails to compile on OSX with clang
From: |
Bruno Haible |
Subject: |
Re: fnmatch-gnu fails to compile on OSX with clang |
Date: |
Sat, 11 Aug 2018 02:19:04 +0200 |
User-agent: |
KMail/5.1.3 (Linux/4.4.0-130-generic; KDE/5.18.0; x86_64; ; ) |
Hi,
Jeroen Meijer wrote:
> It seems that the recent changes related to fnmatch breaks builds on OSX.
>
> I tested on Travis CI, with Xcode 9.4 (clang-902).
>
> The compiler error I get is the following:
>
> /bin/sh ../libtool --tag=CC --mode=compile clang -DHAVE_CONFIG_H -I.
> -I../src/hre -g -O2 -W -Wall -pipe -c -o fnmatch.lo fnmatch.c
> libtool: compile: clang -DHAVE_CONFIG_H -I. -I../src/hre -g -O2 -W
> -Wall -pipe -c fnmatch.c -o fnmatch.o
> In file included from fnmatch.c:176:
> ./fnmatch_loop.c:49:41: error: use of undeclared identifier 'FNM_EXTMATCH'
> if (__builtin_expect (flags & FNM_EXTMATCH, 0) && *p == '(')
> ^
Strange. On this system I would have expected that configure finds
HAVE_FNMATCH_H = 1
HAVE_FNMATCH = 1
REPLACE_FNMATCH = 1
but it seems that it found
HAVE_FNMATCH_H = 1
HAVE_FNMATCH = 0
REPLACE_FNMATCH = 0
Can you confirm this hypothesis? The config.status contains the
values of these variables.
Can you find out why? The config.log contains the execution log of
the autoconf test. Look for "checking for fnmatch...".
Also, did you "make distclean" before reconfiguring with the files
from the updated gnulib?
Bruno