You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
error: ‘template<class T, class ... Args> fmt::v11::basic_string_view<Char> spdlog::details::to_string_view’ redeclared as different kind of entity
#3302
In file included from /build/spdlog-1.15.0/include/spdlog/logger.h:17,
from /build/spdlog-1.15.0/include/spdlog/async_logger.h:17,
from /build/spdlog-1.15.0/include/spdlog/async.h:17,
from /build/spdlog-1.15.0/src/stdout_sinks.cpp:10:
/build/spdlog-1.15.0/include/spdlog/common.h:369:1: warning: inline variables are only available with '-std=c++17' or '-std=gnu++17' [-Wc++17-extensions]
369 | inline fmt::basic_string_view<T> to_string_view(fmt::basic_format_string<T, Args...> fmt) {
| ^~~~~~
/build/spdlog-1.15.0/include/spdlog/common.h:369:54: error: ‘template<class T, class ... Args> fmt::v11::basic_string_view<Char> spdlog::details::to_string_view’ redeclared as different kind of entity
369 | inline fmt::basic_string_view<T> to_string_view(fmt::basic_format_string<T, Args...> fmt) {
| ^~~~~~~~~~~~~~~~~~~
Seems some compiler selection is broken.
I'm not quite sure that it's spdlog that's causing the issue because it worked well with fmt 11.0.2.
The text was updated successfully, but these errors were encountered:
KarlStraussberger
changed the title
error: ‘template<class T, class ... Args> fmt::v11::basic_string_view<Char> spdlog::details::to_string_view’ redeclared as different kind of entity (Issue #4275)
These are spdlog, not {fmt} functions. Please report to https://github.com/gabime/spdlog.
error: ‘template<class T, class ... Args> fmt::v11::basic_string_view<Char> spdlog::details::to_string_view’ redeclared as different kind of entity
Dec 26, 2024
Occurs when building gerbera with fmt 11.1
https://github.com/gerbera/gerbera/actions/runs/12498488888
Seems some compiler selection is broken.
I'm not quite sure that it's spdlog that's causing the issue because it worked well with fmt 11.0.2.
Originally posted by @vitaut in fmtlib/fmt#4275 (comment)
The text was updated successfully, but these errors were encountered: