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
Is your feature request related to a problem? Please describe.
The fmt library sets namespaces according to its major versions (e.g., version 10.2.1 uses namespace v10), resulting in different symbols for different versions.
However, fmt version 11.0.0 uses the same namespace as major version 10.
In other words, fmt version 10.0.0 ~ 10.2.1 use namespace v10 and fmt version 11.0.0 also uses namespace v10 (this is mistake of fmt contributors).
As a result, it leads to an ODR (One Definition Rule) violation.
A segmentation fault can occur when incorrect symbols are linked in external projects that use different versions of fmt.
Describe the solution you'd like
If the version of fmt in tt-umd is updated to 11.0.1, it will use the correct namespace (v11) as described in fmtlib issue #4047.
This update will resolve the potential segmentation fault by ensuring the correct symbols linkage.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The
fmt
library sets namespaces according to its major versions (e.g., version 10.2.1 uses namespace v10), resulting in different symbols for different versions.However, fmt version 11.0.0 uses the same namespace as major version 10.
In other words, fmt version 10.0.0 ~ 10.2.1 use namespace v10 and fmt version 11.0.0 also uses namespace v10 (this is mistake of fmt contributors).
As a result, it leads to an ODR (One Definition Rule) violation.
A segmentation fault can occur when incorrect symbols are linked in external projects that use different versions of fmt.
Describe the solution you'd like
If the version of fmt in tt-umd is updated to 11.0.1, it will use the correct namespace (v11) as described in fmtlib issue #4047.
This update will resolve the potential segmentation fault by ensuring the correct symbols linkage.
The text was updated successfully, but these errors were encountered: