Re: bizarre build behaviour from PoolingAllocator on OpenBSD/clang
Alex Rousskov <[email protected]> Mon, 16 Aug 2021 10:44:11 -0400
| Newsgroups | gmane.comp.web.squid.devel |
|---|---|
| Message-ID | <[email protected]> |
On 8/16/21 7:29 AM, Stuart Henderson wrote: > -c .../src/log/access_log.cc -fPIC -DPIC -o .libs/access_log.o > In file included from .../src/log/access_log.cc:12: > In file included from .../src/AccessLogEntry.h:19: > In file included from .../src/HttpHeader.h:13: > In file included from .../src/base/LookupTable.h:15: > /usr/include/c++/v1/unordered_map:857:5: error: static_assert failed > due to requirement 'is_same<std::__1::pair<const SBuf, unsigned long > long>, std::__1::pair<uf, unsigned long long>>::value' "Invalid > allocator::value_type" > static_assert((is_same<value_type, typename allocator_type::value_type>::value), > ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Yes, that could be the smoking gun missing from the earlier error log, thank you, Stuart! Francesco, can you reproduce the same false is_same<> result using a toy example? You might not even need Squid-specific types. If you can reproduce it, is the result valid/expected or is that a clang bug? Alex.