On Sat, Nov 18, 2017 at 04:48:12PM -0500, Paul Smith wrote:
> One way to fix this would be to change the second #if line above to be:
>
> # if _GNU_GLOB_INTERFACE_VERSION >= GLOB_INTERFACE_VERSION
>
> and see if that works.
Yes! This solves the issue and it also solves the __stat issues as
well.
>
> Is there anywhere documented what the difference is between version 1
> and version 2? Is it just this symlink change? I'm not sure if the
> above change is absolutely correct since it means we'll always accept
> the latest libc glob interface, which seems to defeat the purpose of
> having a version in the first place.
It seems to be a relatively recent change according to `git blame'.
https://sourceware.org/git/?p=glibc.git;a=commit;h=ccf970c7a77e86f4f5ef8ecc5e6
Apparently this patch committed in September 2017 to solve this bug
report:
https://sourceware.org/bugzilla/show_bug.cgi?id=22183
Within it someone mentions this beautiful gem:
* Bump _GNU_GLOB_INTERFACE_VERSION to 2 and forcing new GNUmake build to use
its internal glob implementation.
Well, that sure backfired quite nicely, haha
_______________________________________________
Bug-make mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-make
