GCC compilation option "-fexec-charset=utf-8" has a serious problem.

[MaxLHy0424]

Description / Steps to reproduce the issue

1. Create a C++ source code file that includes the <print> header file, for example:

#include <print>
auto main() -> int
{
    std::print( "Test\n" );
    return 0;
}

2. In the compilation options, add the option -fexec-charset=utf-8, and then compile the source code file created in the previous step.

Expected behavior

The source code file has been successfully compiled and linked.

Actual behavior

GCC will return the following link error messages:

C:/Software/MSYS2/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/14.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: C:\Users\MaxLH\AppData\Local\Temp\cchGzAWv.o:main.cpp:(.text$_ZSt14vprint_unicodeP6_iobufSt17basic_string_viewIcSt11char_traitsIcEESt17basic_format_argsISt20basic_format_contextINSt8__format10_Sink_iterIcEEcEE[_ZSt14vprint_unicodeP6_iobufSt17basic_string_viewIcSt11char_traitsIcEESt17basic_format_argsISt20basic_format_contextINSt8__format10_Sink_iterIcEEcEE]+0x24d): undefined reference to `std::__write_to_terminal(void*, std::span<char, 18446744073709551615ull>)'
collect2.exe: error: ld returned 1 exit status

Verification

• I have verified that my MSYS2 is up-to-date before submitting the report (see https://www.msys2.org/docs/updating/)

Windows Version

MSYS_NT-10.0-27768

MINGW environments affected

• MINGW64
• MINGW32
• UCRT64
• CLANG64
• CLANGARM64

Are you willing to submit a PR?

No.

[nak5124]

On Mingw, you should add -lstdc++exp.
I don't know if this is a bug or not.

[MaxLHy0424]

On Mingw, you should add -lstdc++exp. I don't know if this is a bug or not.

Oh, thanks. It has been works. I think this should have been mentioned in the document. I hope this can be added to the document.