[Bug 268820] index C++ variable overloading

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268820

--- Comment #2 from Mark Millard <[email protected]> ---
(In reply to Mark Millard from comment #1)

It looks like anything with __POSIX_VISIBLE==0 (such as adding
a line at the beginning to define _C11_SOURCE to avoid POSIX)
tends to get errors, such as:

In file included from string_index_use.cpp:5:
In file included from /usr/include/c++/v1/string:523:
In file included from /usr/include/c++/v1/__functional_base:23:
/usr/include/c++/v1/new:327:11: error: no member named 'posix_memalign' in the
global namespace
  (void)::posix_memalign(&__result, __alignment, __size);
        ~~^
In file included from string_index_use.cpp:5:
In file included from /usr/include/c++/v1/string:525:
In file included from /usr/include/c++/v1/algorithm:667:
In file included from /usr/include/c++/v1/functional:506:
In file included from /usr/include/c++/v1/__functional/function.h:22:
In file included from /usr/include/c++/v1/__memory/shared_ptr.h:35:
In file included from /usr/include/c++/v1/atomic:524:
In file included from /usr/include/c++/v1/__thread/timed_backoff_policy.h:16:
/usr/include/c++/v1/__threading_support:411:11: error: use of undeclared
identifier 'nanosleep'
   while (nanosleep(&__ts, &__ts) == -1 && errno == EINTR);
          ^
2 errors generated.

__BSD_VISIBLE==0 is associated with __POSIX_VISIBLE==0 by
default. So it looks like __BSD_VISIBLE==0 is not really an
alternative for avoiding the issue that you hit.

-- 
You are receiving this mail because:
You are the assignee for the bug.