filesystem-ts | Library Enhancements Working Group | Chat library

It seems that the package g++-mingw-w64-x86-64 provides two executables:

• x86_64-w64-mingw32-g++-posix: which uses posix
• x86_64-w64-mingw32-g++-win32: which uses win32

Using the first executable should solve your issue.

It seems that in your specific environment the Enter key you press to confirm you input is interpreted as a raw '\n'. The original meaning of this character, in fact, is line feed, that means "change line without performing a carriage return" ('\r').

In most terminals the enter key sums the effects of \r and \n, and this doesn't happen in your case.

To work it around try inserting manually a '\r' after the input insertion:

The problem lies in thread function t_work, which is calling printf. Depending on your platform, printf is not necessarily re-entrant. On Visual Studio environment, printf is probably protected with some mutex, and everything works. But with GCC and its libc, races can happen in that I/O function.

Solution: use a mutex to protect printf. For example:

By deeper searching, it can be easily found out that the __main (with an additional underscore internally) is the actual entry point for programs.

The same problem is mentioned in the following two answers:

1. https://stackoverflow.com/a/32164910/14320958
2. https://stackoverflow.com/a/45442576/14320958

Both of which claim some form of a connection to the -lgcc option and the libgcc library.

Renaming main to __main works, but is not recommended (the entry point for kernels is apparently by convention kmain as seen in other questions and answers)

The __main function is what a OS calls when starting a program and it usually contains (for example) a call to exit() (passing the return code from main if it's return type is int) and some other underlying system calls (which are probably system specific, more research would need to be done here)

GCC expects you to include a __main function even on standalone compilations, since it's by specification (or that's what I seen people claim) the default entry point for all applications

File system is a general term in computing which can mean different things in different contexts.

The MSYS2 package you found named filesystem is just a basic package for MSYS2 that installs a bunch of files and folders inside MSYS2. Like any other MSYS2 package, you can investigate filesystem to see exactly what it installs by running pacman -Ql filesystem. But this package is irrelevant to the problem at hand.

The library you load by writing #include inside a C++ program is part of the C++ standard library, and it helps you access the file systems of your computer. This part of the standard library was added in C++17, but GCC 9.3.0 defaults to using some older version of C++ when you don't specify what version to use. To use filesystem, you should compile your program with a command like this, which specifies that you want to use C++17:

Solved. For anyone else having this issue, make sure you are using the dll that comes from the same version of mingw than the one you are compiling with.

Use wprintf() in the loop too.

Once orientation is defined, stick to it.

Each stream has an orientation. After a stream is associated with an external file, but before any operations are performed on it, the stream is without orientation. Once a wide character input/output function has been applied to a stream without orientation, the stream becomes a wide-oriented stream. Similarly, once a byte input/output function has been applied to a stream without orientation, the stream becomes a byte-oriented stream. ... C17dr § 7.21.2 4

After hours of searching I found out that there was no err.h on MSYS2, see https://github.com/cliffordwolf/icestorm/issues/85 and resolved my case by replacing all my errx() function calls following these method https://github.com/cliffordwolf/icestorm/pull/88/commits/9acaac752ac53b51b9b33290394b7811048221fa.

Your build problem is likely due to permissions inherited from C:\Users\franc that screw the execution permission needed by the build process.
Use the /home/franc or the /usr/src directories or other similar ones.
Do NOT build under the Windows Home directories.

Unfortunately you can not build the program on Cygwin for other reason, see below:

In a proper directory you will have: